Sync Confluence page titles into shared Team Hub Topics so documentation is easy to find. This guide is for the people who own team-wide content: Account Admins, Team Admins, and Experts.
ℹ️ Before you start: An Account Admin must connect Confluence before anyone can sync pages. Syncing into Team Hub Topics requires Account Admin, Team Admin, or Expert access. To connect, see Connect Confluence. Confluence syncs into Team Hub only, not Deal Rooms.
1. How to sync pages
Choose the specific pages to bring into Spekit. Only what you select is synced.
- Open the Spekit Hub (Web App) or the Sidekick (Chrome Extension).
- Click the Team Hub button, then click + Add New.
- Click File Sync. Your connected Confluence workspace appears here.
- Browse or use the search bar to find pages. Select all the pages you want to import.
- Click Next once your selections are final.
- Assign the pages to the relevant Spekit Topic(s) so they are organized and easy to find.
- Click Sync to finish.
2. How synced content appears in Spekit
Confluence syncs differently from Google Drive and SharePoint. This is the most important thing to understand, because it shapes what reps see.
| Feature | Behavior |
|---|---|
| Content in Spekit | Only the page title comes into Spekit. The page body is not imported. |
| Click behavior | The synced page opens in Spekit with a View in Confluence button that opens the live page in Confluence. |
| Permissions | Only users with Confluence access can open the full page. |
| AI Sidekick | Can reference synced titles, but cannot view or summarize the page body. |
Because only the title syncs, Confluence is best thought of as a smart, permission-aware pointer to your documentation, not a full copy of it inside Spekit.
3. How to test your integration
After your first sync, confirm everything is routing correctly.
- Go to Content and filter by Content source: Confluence to see your synced pages (Click here to use the filter).
- Open a page and confirm the View in Confluence button opens the right page.
- Ask the AI Sidekick to reference a synced page title.
4. Best practices
These build on the general syncing best practices in the Content Syncing Overview. Because only the title syncs, the habits below are specific to Confluence.
| Best practice | Why it matters |
|---|---|
| Make titles descriptive | Titles are the only searchable text a synced Confluence page brings into Spekit. "Competitive: Acme battlecard (2026)" surfaces far better than "Untitled" or "Notes." |
| Confirm Confluence access matches your audience | A user who lacks access in Confluence can see the title in Spekit but cannot open the page. Before you rely on a synced page, make sure the people who need it can open it in Confluence. |
| Reserve Confluence for reference documentation | For content reps need to read, present, or share with buyers inside Spekit, sync the file from Google Drive or SharePoint instead, so the content itself is available. Use Confluence for internal reference material that lives naturally as a page. |
| Use a Spek when reps need the content itself | If reps need the actual content of a page inside Spekit, not just a link, copy that content into a Spek. Syncing gives you a permission-aware pointer, a Spek gives you searchable, AI-readable content. |
| Sync whole spaces where it makes sense | Syncing a space keeps Spekit pointed at that documentation set as it grows, instead of returning to the picker each time a page is added. |