Short answer: Drop the "Buffer → Schedule Update for Specific Time" 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 |
Scheduled At (Unix Timestamp) scheduled_at | string | Required | Unix timestamp (seconds) when the update should be published |
Link media_link | string | Optional | Optional link to attach |
Shorten Links shorten | options | Optional | Shorten URLs using Buffer's shortener |
{"profile_ids": "e.g. 4eb854340acb04e870000010","text": "What's on your mind?","scheduled_at": "1712839200","media_link": "https://example.com/article","shorten": "{{trigger.shorten}}"}
{"success": true,"updates": [{"id": "4eccf2e1512f7e6307000001","text": "Hello world","due_at": 1712839200,"status": "buffer","profile_id": "4eb854340acb04e870000010"}]}
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.