Connect Power Automate with a custom connector
Import the Marcomm AI connector into your Power Automate environment from the OpenAPI file, then run Marcomm AI actions from your flows with a personal API key.
- 1In Marcomm, go to Settings → Integrations → Power Automate to see the status and the values you need.

The Power Automate 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.
- 4In Power Automate, open Custom connectors, choose New custom connector, then Import an OpenAPI from URL, and enter
https://marcomm.works/api/v1/openapi.json. - 5On the Security step choose API Key, set the parameter name to
Authorizationand the location to Header, then create the connector. - 6When a flow asks for a connection, enter
Bearer, a space and your key.
Test publish and send steps with a draft first, because they cannot be undone.
The connector is not in the Microsoft connector list. You import it into your own environment from the OpenAPI file, so its actions follow the API: read news and approvals, create and update press releases, blog posts, press events and RSVP invitations, request approval, approve or reject, and publish and send. It has actions only and no triggers.
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. In the connector, these actions have a confirm field and an Idempotency-Key field.
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 Power Automate, 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 Power Automate card as connected. Settings → API shows when each key was last used.
Not with this connector, because it has actions only. Start the flow with another trigger, such as a schedule, and read the latest items with a list action.