Short answer: You can get confluence page in Confluence by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Confluence Get Confluence Page action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
{"page_id": "e.g. 789012","expand": "e.g. body.storage,version"}
{"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.
Any of these apps can fire this action as part of a workflow.