Confluence Cloud integration

What it does

The Confluence Cloud integration lets you run knowledge-base automations on behalf of any client whose Atlassian site you manage. Connect a site once, then create new pages from upstream events, fetch existing pages by ID, update page content with optimistic version control, list and search pages across spaces, and route inbound page_created events into the rest of your workflow without writing any code.

Connect a Confluence Cloud account

1. In TaskJuice, open Settings -> Connections and choose Add connection -> Confluence Cloud.
2. Enter your client's Confluence site name (the part before .atlassian.net in the site URL, e.g. acme for acme.atlassian.net).
3. Enter the Atlassian account email TaskJuice should act as. This is the address used to sign in at id.atlassian.com.
4. At id.atlassian.com/manage-profile/security/api-tokens, choose Create API token, label it TaskJuice, copy the generated value, and paste it into the Atlassian API Token field.

The connection can read and write any space the connected account has access to. Rotate or revoke the API token from the same security page in your Atlassian account at any time.

Triggers

• confluence-cloud/page-created. Fires when a page is created in the connected Confluence Cloud site.

The trigger verifies the inbound POST against a shared-secret header. Register the webhook in Confluence by calling the REST webhook API (or by configuring an Atlassian Connect app), point it at the TaskJuice incoming webhook URL, and configure the shared secret on the X-Hub-Signature request header so TaskJuice can verify the source.

Actions

• confluence-cloud/create-page. Create a new page in a space with a title, optional parent page, and body in storage, atlas_doc_format, or wiki representation.
• confluence-cloud/get-page. Fetch a single page by numeric ID with an optional body format.
• confluence-cloud/update-page. Update an existing page's title, parent, body, and status, supplying the next sequential version number to detect concurrent edits.
• confluence-cloud/search-pages. List pages with optional filters by space, title, and status, paginated by cursor.

Known limitations

• Rate limits follow Atlassian Cloud's published quotas (see Atlassian Cloud rate limits). TaskJuice retries on 429 responses honoring the Retry-After header.
• Pages use the REST API v2 cursor pagination model. TaskJuice stops paginating after 100 pages by default; raise the ceiling on the action if you need a deeper sweep.
• API token authentication is scoped to the account that created the token. Switching accounts requires generating a new token under that user and rotating the connection.
• Confluence updates are version-checked. The update-page action requires the next sequential version number; a stale value returns 409 Conflict and the workflow can branch on that error code to refetch and retry.
• Confluence webhook registration is operator-driven. Webhooks must be registered via the REST webhook API (or via an Atlassian Connect app) with a shared secret configured on the X-Hub-Signature header; sites without that header configured are rejected.