Connect Marcomm to n8n, Zapier, Make and Power Automate
Automation tools call the Marcomm API with a personal API key to create press releases, blog posts, press events and RSVP invitations, then request approval, publish and send.
- 1In Marcomm, apply for API access in Settings → API. Keys work once the Marcomm AI team reviews and approves it.
- 2Once approved, create a personal key on the same screen and tick the scopes you need (
content,content:write,distribution,approvals). The key is shown only once, when you create it. - 3n8n: install the community node
n8n-nodes-marcommfrom Settings → Community Nodes → Install, create a Marcomm AI API credential and paste your key. - 4Zapier: the Marcomm AI app isn't in the public directory yet, so add it with an invite link. Pick Marcomm AI in a Zap and paste your key when it asks to connect.
- 5Make: our own app is in review, so use the HTTP module's Make a request. Add an endpoint after
https://marcomm.works/api/v1and add the headerAuthorization: Bearer YOUR_API_KEY. - 6Power Automate: in
Custom connectors → New custom connector → Import an OpenAPI from URL, enterhttps://marcomm.works/api/v1/openapi.json. Set security to API key, the parameter name to Authorization and the location toHeader, then enterBearerfollowed by your key when you connect. - 7Test read steps first, and try publishing and sending on a draft before you rely on them.
Publishing and sending can't be undone. Only personal keys can write, send and approve, and those actions are recorded under the name of the person who created the key.
Automation tools act with the name and permissions of the person who created the key. They can do only what that person's role in the workspace allows, and approval and sending rules and the monthly sending limit apply just as in the app.
Each workspace has per-minute and daily call limits. Past a limit, the response asks you to try again shortly. See your limits and usage in Settings → API.
The n8n and Zapier apps add a unique key to each request so a repeated request runs only once. When you call the API yourself from Make or Power Automate, add the Idempotency-Key header to get the same protection.
Connecting automation tools doesn't use Marcomm AI credits. Writing and sending don't use AI.
FAQs
Check that your API access request is approved, that the key's scopes include the action, and that the key hasn't expired. Keys don't work while the workspace is suspended for a billing problem.
No. Only personal keys can write, send and approve, so the record shows who did it.