Add Confluence Comment: 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
Comment Body (HTML) body	string	Required	Comment Body (HTML). e.g. "<p>Great work on this doc!</p>"

Sample request

{
  "page_id": "e.g. 789012",
  "body": "<p>Great work on this doc!</p>"
}

Returns

{
  "id": "comment123",
  "body": {
    "storage": {
      "value": "<p>Great work!</p>"
    }
  },
  "type": "comment"
}

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

FAQ

Questions about Add Confluence Comment.

What does the Add Confluence Comment action do in Confluence?

Posts a comment to a Confluence page's discussion thread. Useful for "Jira ticket updated → comment on the linked design doc with the change" cross-tool sync workflows.

What inputs does Add Confluence Comment require?

Required: Page ID, Comment Body (HTML). 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 Add Confluence Comment support batch operations?

Yes. Run Add Confluence Comment 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