Short answer: Drop the "Confluence → Update Confluence Page" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Page ID page_id | string | Required | Page ID. Example: 789012 |
Title title | string | Required | Title |
Body (HTML) body | string | Required | Message body content. Plain text unless the API specifies HTML/markdown. |
Version Number version_number | string | Required | Current version + 1 (get current via Get Page) |
{"page_id": "e.g. 789012","title": "{{trigger.title}}","body": "e.g. Hi there, thanks for reaching out.","version_number": "e.g. 2"}
{"id": "789012","title": "Updated Page","version": {"number": 2}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.