Short answer: Drop the "Buffer → Create Update (Queue)" 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 |
|---|---|---|---|
Profile IDs profile_ids | string | Required | Comma-separated profile IDs to post to |
Text text | string | Required | Post text content |
Link media_link | string | Optional | Optional link to attach |
Shorten Links shorten | options | Optional | Shorten URLs using Buffer's shortener |
Send Now now | options | Optional | Send immediately instead of queueing |
{"profile_ids": "e.g. 4eb854340acb04e870000010,4eb854...","text": "What's on your mind?","media_link": "https://example.com/article","shorten": "{{trigger.shorten}}","now": "{{trigger.now}}"}
{"success": true,"updates": [{"id": "4eccf2e1512f7e6307000001","text": "Hello world","due_at": 1712839200,"status": "buffer","created_at": 1712835600,"profile_id": "4eb854340acb04e870000010"}],"buffer_count": 1,"buffer_percentage": 25}
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.