Short answer: Drop the "Notion → Append Content" 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 or Block ID block_id | string | Required | Notion block ID — a UUID. Most pages are also valid blocks (use the page ID). |
Text Content content | string | Optional | Text to add as a paragraph. For complex blocks, use the Blocks JSON field instead. |
Blocks JSON (advanced) blocks_json | string | Optional | JSON array of block objects for complex content (headings, lists, toggles, etc.) |
{"block_id": "e.g. a1b2c3d4-e5f6-7890-abcd-ef1234567890","content": "e.g. Here are the meeting notes...","blocks_json": "[{\"type\": \"heading_2\", \"heading_2\": {\"rich_text\": [{\"text\": {\"content\": \"Section Title\"}}]}}]"}
{"object": "list","results": [{"id": "block-id-123","type": "paragraph","object": "block","paragraph": {"rich_text": [{"plain_text": "Here are the 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.