Get Confluence Page: Confluence action

Inputs

The fields this action accepts.

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
Expand expand	string	Optional	Comma-separated fields to expand

Sample request

{
  "page_id": "e.g. 789012",
  "expand": "e.g. body.storage,version"
}

Returns

{
  "id": "789012",
  "body": {
    "storage": {
      "value": "<p>Content here</p>"
    }
  },
  "type": "page",
  "title": "Meeting Notes"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Confluence Page.

What does the Get Confluence Page action do in Confluence?

Returns the page with body in storage format, version number, ancestors, and labels. Use to read existing content before update (Confluence enforces optimistic concurrency — pass version+1 on update).

What inputs does Get Confluence Page require?

Required: Page ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Confluence returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Confluence Page support batch operations?

Yes. Run Get Confluence Page inside a Loop node to process arrays. Tiny Command handles Confluence's rate limits automatically so you don't have to throttle manually.

More actions