Short answer: Drop the "Confluence → Create 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 |
|---|---|---|---|
Space Key spaceKey | string | Required | The short key of the Confluence space |
Page Title title | string | Required | Page Title. Example: Meeting Notes — Jan 15 |
Page Body body | string | Required | HTML content of the page. Use Confluence storage format for rich content. |
Parent Page ID parentId | string | Optional | Create as a child of this page. Leave empty for a top-level page. |
{"spaceKey": "e.g. ENG","title": "e.g. Meeting Notes — Jan 15","body": "<p>Notes from today's meeting...</p>","parentId": "e.g. 123456"}
{"id": "789012","type": "page","title": "Meeting Notes","_links": {"webui": "/spaces/ENG/pages/789012/Meeting+Notes"}}
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.