Confluence currently provides 1 trigger that can start a workflow and 3 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
New Page
Triggers when a new page is created.
Get Page Content
Get page content and optionally all its descendants
Create Page from Template
Creates a new page from a template with the given title and variables.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Confluence event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Page
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Confluence action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Get Page Content
Combine Confluence with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
New Page
Finishes with
Get Page Content, then preserve the outcome in Coherence
The exact authentication fields depend on Confluence. The workflow structure stays straightforward:
Authorize the Confluence account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Confluence or provide a complementary trigger or action.
Confluence currently provides 1 trigger that can start a workflow and 3 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Confluence currently lists 1 trigger and 3 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Confluence triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
