Zapier private beta
Send work into AckPost without bypassing approvals.
AckPost’s Zapier integration uses scoped workspace keys and the AckPost MCP endpoint so automation can create drafts, inspect queue state, and support operations while sensitive actions remain auditable.
Endpoint
https://ackpost.com/api/ackpost/mcpAuthentication uses an AckPost API key from Settings > Developer. Do not paste provider tokens or social account passwords into Zapier.
Supported beta actions
Create Draft
Create a post draft in AckPost for human review.
List Queue Items
Read recent scheduled or queued work for reporting and workflow routing.
Approval-safe expansion
Future actions can add approvals, proofs, and webhooks after safety review.
Setup checklist
- 1Create an AckPost API key in Settings > Developer.
- 2Use the private Zapier invite or Zapier developer app while the integration is in beta.
- 3Connect AckPost in Zapier with the API key and default MCP endpoint.
- 4Start with read-only queue checks or draft creation, not direct publishing.
- 5Review drafts inside AckPost before scheduling or publishing.
Current beta boundary
Direct publish, delete, invite, send-reply, and billing-change actions are not exposed as public Zapier actions. Those actions require explicit approval gates and should stay inside AckPost until the safety review is complete.