One source, two audiences
The internal runbook stays in Confluence; the agent answers customers from it without anyone maintaining a second public copy.
Atlassian's wiki, and the internal documentation of record in most larger organizations. Connect it once and your copilot works with spaces, pages, attachments and comments without leaving the thread — and your workflows can act on it while the customer is still typing.
No credit card required · 7-day free trial
Copilot rides inside the inbox. With Confluence connected it reads spaces, pages, attachments and comments and acts on them from the same panel as the conversation — no second tab, no copying an order number across.
What a specific connection exposes is decided by Confluence, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.
Once Confluence is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.
The picker is the authority on which events your Confluence connection publishes — these are the kinds that apps of this sort emit.
A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.
The rows you name become the variables downstream steps read, so a branch can test what Confluence said.
A step budget and a model tier per node — the loop stops where you told it to.
The loop can call the Confluence tools you left enabled and nothing else.
The internal runbook stays in Confluence; the agent answers customers from it without anyone maintaining a second public copy.
A workflow drafts a Confluence page from a recurring question the inbox keeps seeing, ready for a human to approve.
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
The catalogue runs to hundreds of apps and is searchable. Connect Confluence from its card.
You sign in on Confluence's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.
Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.