Discover destinations
List accessible workspaces and connected channels before scheduling.
Postly + Make
Build a visual workflow from content to publication.
Shape the logic around your publishing process. Map records, choose a destination, and hand delivery to the Postly workspace your team already manages.
Available by invitation · public directory review pending. Postly API access is required. Your automation platform’s plan and limits also apply.
The outcome
A scenario with explicit destinations, scheduled content, and post IDs you can follow up.
Schedule and inspect
Schedule a text post, then use Get a Post to inspect the returned post ID.
Make an API Call
Call documented relative Postly API paths using the same saved connection.
A clear path from input to outcome.
- 01
Your source
Start with a reviewed record or a deliberate scenario input.
- 02
Map and filter
Check required fields and select the intended workspace and channel.
- 03
Schedule in Postly
Send a stable source ID, text, and future publishing time.
- 04
Check the outcome
Use Get a Post and the scenario execution log to investigate delivery.
Start with the right setup.
- A Postly account with API access and permission to the target workspace.
- A Make account and a scenario with a deliberate publishing trigger.
- A connected channel and a future publishing time for each scheduled record.
Put it to work.
Approved records → scheduled posts
Filter your content calendar to the records your team has approved.
Read the workflowWorkspace → destination discovery
Use List Workspaces and List Connected Channels to map the right account.
Read the workflowSchedule → post status
Keep the post ID as the reference for later status checks.
Read the workflowQuestions about Postly + Make
Is the Make connection a separate publishing account?
No. The API key connects Make to your existing Postly access. Workspace permissions, plan eligibility, and publishing limits still apply.
Can I make other Postly API requests?
The universal module accepts relative paths on the Postly API, such as /v1/workspaces. Use the API reference for the method, body, permissions, and response expected by each endpoint.
Can a scenario publish to several channels?
The Schedule a Post module targets one explicit channel per call. Route records or repeat the module deliberately when your workflow needs separate destination requests.
How do I troubleshoot a failed run?
Inspect the module error and Postly post status. Check the key, workspace, connected channel, text, and future schedule before changing or replaying the record.