CONNECTOR · CONFLUENCE
Your Confluence, in the planning conversation.
A connector is the bridge to one tool. This one connects your Confluence: the planning agent searches your spaces, reads a page and the comments on it, and writes back when you say so, a new page, an edit, or a comment. It signs in with your own Atlassian account, so what you can see in Confluence is what it can see, and what you cannot, it cannot.
What the agent does with your wiki
Connect Confluence once and the agent works it as you: searching, reading, and writing back when you approve. What you can see in Confluence is what it can see.
| In your wiki | What the agent can do |
|---|---|
| A space | Searched and listed, so a plan starts from what is already written down |
| A page | Read as text the agent can quote, with the images and files attached to it |
| A comment | Read with who wrote it and whether it was resolved, so an objection is not missed |
| Crossed-out text | Stays crossed out, so a decision that was reversed does not come back to life |
| A new page | Written from the plan, in the space you choose, after you approve it |
| An existing page | Updated in place. If somebody edited it since the agent read it, the write stops and tells you |
Three steps to a wiki the agent can read and write
- 1
Connect
Click Connect Confluence and sign in with your Atlassian account. One approval, the same account Jira uses. The connection belongs to you, not your whole site, and takes about a minute.
- 2
Turn it on
An owner switches Confluence on for the workspace. It stays off until they do, and any project can switch it off on its own without affecting the others.
- 3
Ask
Ask what your runbook says, or tell the agent to write the plan up as a page. It shows you what it found, and every write asks you first.
Questions, answered
- Can the agent change our Confluence without asking?
- No. Every write asks you first, in the conversation, showing what it is about to do. You can allow one write, or allow a kind of write from then on, and either way it acts on your own connection so your Confluence history names you.
- What can it see?
- Exactly what you can see. It signs in as you, so a space you have no access to is invisible to it. It cannot delete anything: that permission is not requested at all.
- Who needs to connect Confluence?
- Everyone who wants the agent to use it. Connections are personal, so a teammate gets their own. Everyone else can still plan, and nobody borrows anybody else's access.
- Do images and attachments come across?
- Yes. A screenshot on a page is something the agent can open and talk about, not a broken link, and it can put the image into a Spec for you.
- Do I need Confluence before I start planning?
- No. Plan first and connect Confluence whenever you want the agent reading what your team already wrote down. A plan without it still produces build-ready specs and prototypes.
Your wiki, read and written with you in the room.
Explore other connectors: All connectors