Connect Zapier with a personal API key
Use the Marcomm AI app for Zapier to start Zaps from press releases, blog posts and press events, and to create, publish and send them. The app is open by invitation.
- 1In Marcomm, go to Settings → Integrations → Zapier to see the status and the values you need.

The Zapier page shows the current status, the steps, the values to copy and whether API access is approved for this workspace. - 2Open Settings → API. If the workspace has no API access yet, an owner or admin fills in Apply for API access and selects Submit application.
- 3After approval, open Create a key, choose Personal key, tick the Scopes you need and select Create key. Copy the key, because it is shown only once.
- 4Open the invitation link from Marcomm AI and add the Marcomm AI app to your Zapier account.
- 5Create a Zap, choose Marcomm AI as a trigger or an action, and paste the key in API Key when Zapier asks you to connect.
Test publish and send steps with a draft first, because they cannot be undone.
The app is not in the public Zapier directory yet, so you need an invitation link from Marcomm AI. It has seven triggers: New Press Release, Press Release Approval Requested, Press Release Published, New Blog Post, Blog Post Published, New Press Event and RSVP Invite Updated. Its actions create, update, request approval for, publish and send press releases, create and publish blog posts, create press events, and create, fill and send RSVP invitations. Two searches find a press release or a blog post.
Scopes decide what a key can do. Content (content) reads press releases, blog posts and press events, Write content (content:write) creates and edits drafts, Publish and send (distribution) publishes and sends email, and Approvals (approvals) covers approval steps. The last three work only with a Personal key, because the action is recorded under the person who created the key. A Workspace key can only read, and every key acts with the role and permissions of its creator.
Publishing and sending cannot be undone. The API runs them only when the request has confirm: true or an Idempotency-Key header, and it publishes nothing and answers 409 while approval is still required or the item is scheduled or under embargo. A retry with the same Idempotency-Key and the same request returns the first result for 24 hours instead of running again. Each write step sends an idempotency key built from the Zap and its input. If a Zap must repeat the very same step within 24 hours on purpose, enter a value that changes on every run in Repeat Key.
The API is available on the Team plan and above. The Marcomm AI team reviews each application, and keys work only after approval. A key can use only the scopes approved for the workspace, and each person can have up to 10 keys. By default a workspace can make 60 requests per minute and 10,000 per day; above that the API answers 429 with a Retry-After header. To raise the limits, use Need higher limits? in Settings → API. To disconnect Zapier, select Revoke next to the key; systems using it lose access right away.
FAQs
Call
GET https://marcomm.works/api/v1/mewith the headerAuthorization: Bearerfollowed by your key. It works with any approved key whatever its scopes, and returns the workspace, the key name and its scopes.A key does not record which service uses it, so Marcomm does not mark the Zapier card as connected. Settings → API shows when each key was last used.
No. The Zapier app can request approval, and the approver decides in Marcomm. The API can approve or reject with a personal key that has the Approvals scope.