Skip to content

Connect your tools to Atlas Labs

To connect a tool to Atlas Labs, give it the base URL https://automationatlas.io/labs/api/v1, an Authorization: Bearer header holding one of your two sandbox keys and, for events, a public HTTPS webhook URL. Zapier, Make, n8n, Power Automate, Pipedream, Frends and any AI agent that speaks MCP use those same fields against this fictional company's API, Moxo receives the webhooks directly, and every recipe is readable here before you start a sandbox.

Start a sandbox and your keys are filled in for you. Every recipe on these pages uses the placeholders lab_off_YOUR_KEY and lab_fac_YOUR_KEY. Once you start a sandbox, a “Connect it” panel shows the same snippets with your real keys and a copy button.
Start a sandbox

Which key do I use, and where does it go?

Every tool on this page needs the same five things. Nothing else is tool-specific.

Reference table — Atlas Labs API fields, not part of the fictional simulation. Derived from the API source, checked 15 Oct 2026.
Field in your toolValue
Base URLhttps://automationatlas.io/labs/api/v1
Auth headerAuthorization: Bearer lab_off_YOUR_KEY for Head Office routes, Authorization: Bearer lab_fac_YOUR_KEY for Factory routes. X-Api-Key is accepted as an alias.
Which key/office/* wants lab_off_; /factory/* wants lab_fac_; /sandbox, /missions, /events and /webhooks take either. The wrong one returns 403 wrong_system with a hint naming the right prefix.
Body headerContent-Type: application/json on every write (otherwise 415 unsupported_media_type).
Idempotency-KeyA value that is stable per business event, for example the incoming webhook's id, at most 64 characters. Accepted on every write, required on 13 money and stock routes.
Webhook URLPublic https://, port 443, no redirects, answer 2xx within 5 seconds. Localhost and private hosts are refused with 422 webhook_url_rejected.
Spec to import/labs/api/v1/openapi-3.0.json (OpenAPI 3.0, the safe first choice), /openapi.json (3.1, for tools that state 3.1 support), /swagger-2.0.json (the one Power Automate accepts).
Factory key
lab_fac_…
Factory API
/factory/*
work orders, runs, stock
Head Office key
lab_off_…
Head Office API
/office/*
orders, suppliers, cash
Shared routes, either key
/sandbox /missions /events /webhooks
Solid arrows: the key a route requires. Dashed: shared routes accept either key. Cross them and the API answers 403 wrong_system with a hint naming the right prefix.

Which tools have a guide?

Pick your tool. Each guide has the exact field names to type, the steps in the tool's own words, the webhook leg, and a label saying how far we verified it. The logos are each vendor's own mark, shown only to identify the tool; none of these products is affiliated with Atlas Labs.

Zapier

Written from vendor docs

Good for: pushing Atlas Labs events into the apps you already run in Zapier, and simple writes back.

  • ReceiveWebhooks by Zapier → Catch Raw Hook
  • CallWebhooks by Zapier → Custom Request
  • KeyHeaders field: Authorization: Bearer lab_off_YOUR_KEY
Read the Zapier guide →

Make

Blueprint structurally validated

Good for: visual scenarios with routers and iterators over Atlas Labs lists.

  • ReceiveWebhooks → Custom webhook
  • CallHTTP → Make a request
  • KeyCredentials keychain, API key: Key Bearer lab_off_YOUR_KEY, Header, name Authorization
Read the Make guide →

n8n

Workflow structurally validated

Good for: self-hosted or Cloud workflows with a Code node for signature checks.

  • ReceiveWebhook node, Options → Raw Body
  • CallHTTP Request node, or Import cURL
  • KeyCredential: Bearer Auth (token only) or Header Auth
Read the n8n guide →

Power Automate

Connector generated, schema-validated

Good for: Microsoft tenants; a typed custom connector from our Swagger 2.0 file.

  • ReceiveWhen an HTTP request is received, set to Anyone
  • CallHTTP action, or the custom connector
  • KeyConnector connection: type Bearer lab_off_YOUR_KEY
Read the Power Automate guide →

Pipedream

Step syntax-checked

Good for: pasting the JavaScript snippets unchanged into a Node.js code step.

  • ReceiveHTTP / Webhook → New Requests trigger
  • CallSend any HTTP Request, or a Node.js step
  • KeyHeaders, or an environment variable read in code
Use the REST snippets →

Workato

Written from vendor docs

Good for: Workato teams who want to import our OpenAPI or Swagger file as a connector.

  • ImportOpenAPI connector: openapi-3.0.json or swagger-2.0.json (Workato's docs list both formats)
  • CallHTTP connector, Header auth: Authorization: Bearer lab_off_YOUR_KEY
  • ReceiveHTTP connector with authentication None gives you a webhook URL
  • Not checkedplan, raw-body access and retries
Use the REST snippets →

Moxo

Tested: Atlas Labs to Moxo AI by webhook

Good for: Moxo AI flows that start from an Atlas Labs sales order.

  • ReceiveTemplate Webhook trigger, None (secret URL), with field mapping
  • CallMoxo Webhook step → a Make, n8n or Zapier hook that adds the key
  • KeyNever in Moxo
Read the Moxo guide →

Frends

Not run in a tenant

Good for: enterprise integration teams building a Process with HTTP shapes.

  • ReceiveHTTP Trigger, unparsed Base64 option for HMAC
  • CallTask Frends.HTTP.Request
  • KeyHeaders list from an Environment Variable
Read the Frends guide →

Postman

Collection generated, schema-validated

Good for: exploring every route before you automate anything.

  • ImportImport → link …/api/v1/openapi-3.0.json. We have not confirmed which OpenAPI versions Postman accepts, so start with 3.0; swagger-2.0.json is the fallback
  • AuthAuthorization tab → Bearer Token
  • KeyA collection variable, never plain text
Authenticate with your key →

AI agents (MCP)

Proven against the live API

Good for: Claude Code, Cursor and any MCP client; the agent creates its own sandbox.

  • Endpointhttps://automationatlas.io/labs/mcp, Streamable HTTP
  • Toolscreate_sandbox binds both keys to the session
  • GotchaAccept must list JSON and text/event-stream
Connect an agent →

REST: curl, JavaScript, Python

Proven against the live API

Good for: anything with a shell, Node 20 or Python 3.9.

  • ReadGET /sandbox, GET /office/sales-orders
  • WritePOST …/accept with Idempotency-Key
  • EventsPOST /webhooks, verify the raw body
Authenticate with your key →

Can I try the integrations before I get a token?

Yes. Every guide reads completely with the placeholder keys, so you can set up a Zap, a scenario or a flow first and paste real keys last. Start a sandbox from the hub when you are ready and the same snippets reappear there with your keys filled in. Nothing on these pages needs JavaScript, so crawlers and AI assistants read the same recipes you do.

How do I connect an AI agent?

Point an MCP client at https://automationatlas.io/labs/mcp over Streamable HTTP and call the create_sandbox tool; the session then holds both keys. The client must send Accept: application/json, text/event-stream. Connect an AI agent has the tools, the limits and the client commands.

Does Atlas Labs publish an OpenAPI file?

Reference table — specification downloads for the Atlas Labs API, not part of the fictional simulation.
FormatURLUse it in
OpenAPI 3.1https://automationatlas.io/labs/api/v1/openapi.jsonCode generators and importers that state 3.1 support
OpenAPI 3.0https://automationatlas.io/labs/api/v1/openapi-3.0.jsonPostman (we have not confirmed which OpenAPI versions it accepts; start with 3.0), Workato, tools that reject 3.1
Swagger 2.0https://automationatlas.io/labs/api/v1/swagger-2.0.jsonPower Automate custom connectors; fallback for Postman and Workato

All three describe the same set of operations. Every operation has a readable operationId and summary, so importers name each request from its summary (for example “List sales orders”), with a unique operationId such as listSalesOrders behind it. n8n and Make have no OpenAPI import, and none was found in Zapier's documentation, so their guides use the HTTP modules instead.

How do I get events pushed to my tool?

  • Subscribe with POST /webhooks using either key: {"url": "https://…", "events": ["office.sales_order.received"]}. The whsec_ secret is shown once. The bridge recipes subscribe to office.sales_order.accepted instead, because only an accepted order can be bridged.
  • Up to 3 subscriptions per sandbox. The URL must be public https:// on port 443; the subscription activates when the test ping (POST /webhooks/{id}/test) gets a 2xx.
  • Shared platform hosts (hooks.zapier.com, hook.*.make.com, *.app.n8n.cloud, *.m.pipedream.net, *.logic.azure.com, webhook.site) get a higher delivery allowance than a private host.
  • Every delivery is signed (Standard Webhooks: webhook-id, webhook-timestamp, webhook-signature). Verify against the raw body; most tools need a “raw” option for that.
  • Failed deliveries retry after 10 s, 60 s and 300 s; 5 consecutive failures disable the subscription. De-duplicate on the event id. Events are sent only for the types you subscribed to.

Webhooks in five minutes →

Downloads

Each file says how far it was verified. “Generated and schema-validated” never means “confirmed to import into the real tool”.

Reference table — connector templates for Atlas Labs, not part of the fictional simulation.
FileVerified
atlas-labs.postman_collection.jsonGenerated and schema-validated
atlas-labs-power-automate-connector.zip (Swagger 2.0 + properties)Generated, byte-deterministic
n8n workflow: bridge accepted order → work order (needs a manual-bridge preset: Standard or Full)Structurally validated only
Make blueprint: bridge accepted order → work order (needs a manual-bridge preset: Standard or Full)Structurally validated only
Zapier recipe (Markdown): bridge accepted order → work order (needs a manual-bridge preset: Standard or Full)Written from vendor docs, not built
Pipedream step (JavaScript)Syntax-checked and lint-clean
Bruno collectionStructurally validated only
History pack (.xlsx / .csv), twelve fictional months of one companyGenerated by the simulator