Skip to main content
Sigmora’s automation connectors are thin adapters over the public /v1 API: projects, URL media import, jobs, workflow proposals, transcripts and publishing, plus signed webhook events as triggers. They never move media bytes through the automation platform; Sigmora imports from a public URL and the flow passes IDs. Every connector authenticates with a workspace API key. Mint one in Settings → API keys; it acts and bills as you, in the workspace it belongs to. Every action that changes something takes an idempotency key: map a stable value from the upstream record (for example a row ID plus its version) so a retried step never creates a second project, paid run or post.
Listing status. None of the connectors below is in its platform’s public directory yet; each is waiting on that platform’s review. This page says so per connector and will switch to “install from the directory” as each listing goes live. Power Automate works today by importing the connector file. Until a listing is live you can always call the API directly, for example from an HTTP step, with the same key.

​
n8n

Status: not yet published. The community node n8n-nodes-sigmora is not on npm yet. Once it is:
  1. In n8n, open Settings → Community nodes and choose Install.
  2. Enter n8n-nodes-sigmora, accept the community-node notice, and install.
  3. Add a Sigmora node to a workflow and create a Sigmora API credential with your API key. The credential test calls GET /v1/capabilities.
  4. For events, add the Sigmora Trigger node. On a self-hosted n8n, set WEBHOOK_URL to a public HTTPS origin first, so the trigger registers a reachable URL.
The node covers projects, media import, jobs, approved workflow recipes, context snapshots, proposal decisions, transcript export and publishing, and the trigger verifies each event’s signature.

​
Zapier

Status: not yet published. The Sigmora app is not in the Zapier directory yet. Once it is:
  1. In Zapier, create a Zap and search for Sigmora as the trigger or action app.
  2. Connect a Sigmora account and paste your API key. Zapier checks it before saving the connection.
  3. Use the Job, Artifact, or Publish Event trigger for signed events, or the actions and searches for projects, media, jobs, workflow proposals, transcripts and publishing.

​
Make

Status: not yet published. The Sigmora app is not in the Make app directory yet. Once it is:
  1. In a Make scenario, add a module and search for Sigmora.
  2. Create a connection and paste your API key.
  3. Use Watch job, artifact, and publish events (an instant trigger with signed delivery) or the modules for projects, media, jobs, workflow proposals, transcripts and publishing.

​
Pipedream

Status: not yet published. The Sigmora app is not in the Pipedream registry yet. Once it is:
  1. In a Pipedream workflow, add a step and search for Sigmora.
  2. Connect your Sigmora account with your API key.
  3. Use the New Job Event source as a trigger, or the actions for projects, media import, jobs, workflow recipes and proposals, runs, provenance, transcripts and publishing.

​
Power Automate

Status: available as a custom connector. Sigmora is not a certified connector, so you import it into your environment:
  1. Download the connector file: sigmora-power-automate.swagger.json.
  2. In Power Automate, open Custom connectors → New custom connector → Import an OpenAPI file, and choose the file.
  3. Create the connector, then add a connection. In the Authorization field enter Bearer followed by your API key (Bearer sk_live_...); the connector file cannot add the prefix itself.
  4. Every action that changes something needs an Idempotency-Key.
For completion, subscribe a flow’s HTTP trigger to webhooks or loop on Get Job until the job finishes.