Overview
Connect Confluence Cloud to Taskade so your documentation keeps up with your projects. A new page can start an automation, and any automation can create or update pages and add comments.
TL;DR: Confluence Cloud connects to Taskade automations with your site URL, your Atlassian email, and an API token. The New Page in Space trigger starts an automation when a page is published. Actions create, update, read, and search pages, add comments, and list spaces. Confluence steps need Pro and up.
Before You Start
- What you need: A Confluence Cloud site and an Atlassian account and a Taskade workspace
- Plan: Pro and up. On Free and Starter, the Confluence steps show a PRO badge and open the upgrade page.
- Time: About 5 minutes
Step 1: Create an Atlassian API Token
- Go to id.atlassian.com/manage-profile/security/api-tokens.
- Click Create API token.
- Copy the token.
Step 2: Connect Confluence in Taskade
Taskade stores the connection for the whole workspace, so every automation that uses Confluence reuses it.
- Open Automations in your workspace, and click Create.
- Add a trigger or a step, and search for Confluence.
- Click Connect.
- Fill in Site URL (for example
https://your-site.atlassian.net), the Email of your Atlassian account, and the API Token. The automation acts as you, so it can see and edit only what your account can. - Save the connection. Taskade tests it with Confluence before it saves it.
Step 3: Pick a Trigger or an Action
Pick a Confluence trigger to start an automation, or add a Confluence action after any trigger. See Automation Triggers and Automation Actions for the Taskade steps that you can combine with them.
| Trigger | Starts the automation when |
|---|---|
| New Page in Space | A new page is created and published in the Confluence space that you pick. A draft created earlier and published later does not start it. Checks every 15 minutes. |
| Action | What it does |
|---|---|
| Create Page | Creates a page in a space, optionally under a parent page. |
| Update Page | Changes the title or the content of a page. Empty fields keep their current value. |
| Get Page | Reads a page: its title, link, version, and content. |
| Search with CQL | Finds pages, blog posts, and comments with a CQL query. |
| Add Comment | Adds a comment at the bottom of a page. |
| List Spaces | Lists the spaces that the connected account can see. |
You are done when a test page shows in your Confluence space, or a newly published page starts the automation within 15 minutes.
Build Your First Confluence Automation
Start from one of these patterns, then add your own steps.
| Goal | Trigger | Steps that follow |
|---|---|---|
| Publish meeting notes | A Taskade task is completed | Summarize with AI, then Create Page in the team space |
| Teach an agent your docs | New Page in Space | Get Page, then Add Knowledge to Agent |
| Flag stale pages | Schedule | Search with CQL, then Add Task for each page in a Loop |
To describe an automation in plain words instead, ask Taskade EVE in your workspace. For example:
Build an automation that uses Confluence. When the trigger fires, add a task with the details to a project that I pick. Do not add any other steps yet.
The last sentence of the prompt keeps the first draft small, so you can test one step before you add more.
Frequently Asked Questions
Does Confluence Server or Data Center work?
The connector asks for a Confluence Cloud site URL that ends in atlassian.net. Use it with Confluence Cloud.
Why did a published draft not start my automation?
New Page in Space starts only for a page that is created and published as new. A draft created earlier and published later does not start it.
Related guides
- Notion Integration. Another docs tool for automations.
- Jira Integration. Connect Atlassian Jira.
- Agent Knowledge. Teach an agent from your pages.
- Automation Triggers. See every way to start an automation.
- Automations & Execution. Chain triggers and actions across 100+ integrations.
- Explore integrations and browse automations.