Integrations · Docs & knowledge

Confluence in the conversation.

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

Confluence
Docs & knowledge
01 · COPILOT

Ask for it in plain language. It does the Confluence part.

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.

  • Search spaces for a page
  • Read a page’s content
  • Create a page in a space
  • Update or append to an existing page
  • Comment on a page

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.

02 · WORKFLOWS

Something happens in Confluence. A workflow starts.

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.

  • A page is created or updated

The picker is the authority on which events your Confluence connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

One step that decides which Confluence tools to call.

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.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what Confluence said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the Confluence tools you left enabled and nothing else.

What teams do with it

Two ways Confluence earns its connection.

01

One source, two audiences

The internal runbook stays in Confluence; the agent answers customers from it without anyone maintaining a second public copy.

02

Document what support learned

A workflow drafts a Confluence page from a recurring question the inbox keeps seeing, ready for a human to approve.

Setup

Connect Confluence in about a minute.

  1. 1

    Open Settings → Apps

    It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.

  2. 2

    Find Confluence in Browse

    The catalogue runs to hundreds of apps and is searchable. Connect Confluence from its card.

  3. 3

    Authorize with your own Confluence account

    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.

  4. 4

    Choose the tools it may call

    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.

Confluence questions.

How do I connect Confluence to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Confluence. Connecting it opens Confluence's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.
What can Cloodot do in Confluence?
Work of this kind: search spaces for a page; read a page’s content; create a page in a space; update or append to an existing page; comment on a page. The exact list depends on what your Confluence account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Confluence tools Cloodot may use?
Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Confluence connection is a matter of leaving the writes off.
Can an event in Confluence start a Cloodot workflow?
Yes. Events like a page is created or updated appear in the workflow editor's trigger picker once Confluence is connected, and the event's own fields become variables the rest of the workflow can read.
Who in my team can connect Confluence?
Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Confluence account that authorized it, so a docs & knowledge connection is only ever as broad as the account behind it.
See it on your own inbox

Try the whole thing, today.

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.