Confluence spaces hold the written record of a team: runbooks, decisions, retros. Connecting it lets your Brain cite those pages, and lets Fivo publish meeting reports where the team already reads.
What it adds to your Brain
For each space you choose, Fivo reads the current pages: their text (macros are stripped, only readable content stays), the author and last editor, and both page comments and inline comments. Each page and its comments form one episode in the graph.
Fivo also writes. A meeting report can be published as a Confluence page in the space you pick, optionally nested under a parent page. The page contains the report's sections rendered as rich text.
Example question your AI can then answer: "Which runbook covers the payments outage, and what did people comment on it?"
Before you start
- An Atlassian account with access to the Confluence spaces you want to read.
- Organization scope requires the organization owner. See Connect your tools.
- If your account reaches several Atlassian sites, know which site holds the spaces you need. Fivo lists spaces from every site it can reach and names them after their site when more than one has spaces.
Step by step
- Open Integrations in app.fivo.ai and find Confluence.
- Click Connect. Atlassian opens its authorization page. You approve permissions to read spaces, pages, comments, space permissions and user profiles, to create pages, and to stay connected without signing in again.
- Back in Fivo, open the integration's Configuration and choose:
- Space: the space where reports will be published.
- Parent page (optional): the page to nest reports under. Without it, reports go to the space root.
- Save.
- To feed your graph, go to the Brain view, connect Confluence as a source and pick the spaces to read. Fivo lists every live space in every site the connection reaches.
What happens next
Fivo reads each space newest-modified-first within the history window of the source and shows progress in the Brain view. A Confluence connection of this kind cannot register webhooks, so there are no instant updates: pages are re-read on a regular schedule and changes arrive with the next read.
Confluence tells Fivo who can read a space, so with organization scope a space's facts are visible to the people who have read permission on that space in Confluence. One limit: Fivo reads users granted directly, not members of groups, so someone who only reaches a space through a group may not see its facts in the graph. With personal scope only you see them. See Permissions: what your Brain can see.
Publishing a report does not depend on reading. The page is created by the account that connected Confluence, in the space and under the parent you chose.
Disconnect
Open Integrations, select Confluence and click Disconnect. To stop reading while keeping publishing, use Remove from graph in the Brain view: what Confluence brought in leaves your graph, and you can turn it back on later.
Troubleshooting
- The parent page list is empty. Fivo lists pages of the chosen space in batches and stops at a thousand. If the listing fails, reports go to the space root. Pick the space first, then the parent page.
- A space you chose shows as unreachable. Confluence answers the same way for a trashed space and for one you can no longer open. Check the space in Confluence, or pick a different one.
- Fivo asks you to reconnect. Connections made before Fivo could read Confluence only had permission to publish. Sharing keeps working; reconnecting grants the reading permissions.
- Names show as account ids. Resolving ids to names needs the user profile permission, which arrives on reconnect. Until then Fivo keeps the ids.
Related: Connect chat and documents.
- integration
- docs