Zapier and Make
Both apps use your API token and a workspace UUID, call only the public API, and offer the same set of steps.
| Step | Zapier | Make | API |
|---|---|---|---|
| Post published (per account) | Trigger: Post Published | Watch Events → post.published | Webhooks |
| Post failed, with the network error | Trigger: Post Failed | Watch Events → post.publishing_failed | Webhooks |
| Account connection expiring | Trigger: Account Connection Expiring | Watch Events → account.token_expiring | Connection health |
| New post (polling) | Trigger: New Post | - | GET /{workspaceUuid}/posts |
| Create a post (draft, now, schedule, queue) | Action: Create Post | Create a Post | POST /{workspaceUuid}/posts |
| Schedule or publish an existing post | Action: Schedule Post | Schedule a Post | POST /{workspaceUuid}/posts/schedule/{postUuid} |
| Upload media from a URL | Action: Upload Media from URL | Upload Media from URL | POST /{workspaceUuid}/media/remote/initiate |
| Dry-run a post | Action: Validate Post | Validate a Post | POST /{workspaceUuid}/posts/validate |
| Find accounts | Search: Find Account | List Accounts | GET /{workspaceUuid}/accounts |
| Find a post | Search: Find Post | - | GET /{workspaceUuid}/posts/{postUuid} |
Connect
- In PostBoost, create an API token under Settings → Access Tokens.
- Copy your workspace UUID from the dashboard URL (
https://postboost.co/app/<workspace-uuid>/..., see Quick Start). - Paste both when the app asks for a connection. Connect once per workspace.
Instant triggers
The triggers register their own webhook through the subscription API when you turn a Zap or scenario on, and remove it when you turn it off. You can see them under Settings → Webhooks as "Zapier: …" or "Make: …". Creating them needs a workspace admin token and a plan with webhooks.
post.published and post.publishing_failed arrive once per account: a post to three accounts starts three runs. Use Post published (all accounts) (post.published_all) in Make if you want one run per post.
Schedule times
Both apps send schedule times in UTC, converted from the time zone of your Zap or scenario. To publish at a fixed local time, enter the time with your time zone or set the Zap or scenario time zone first.