Connect Make to Atlas Labs

To connect Make to Atlas Labs, create a Custom webhook module to receive events and an HTTP Make a request module to call the API with an Authorization: Bearer header stored in a Credentials keychain. Make assigns the webhook URL on a hook.<region>.make.com host, which Atlas Labs accepts as a shared automation destination.

How do I receive Atlas Labs events in Make?

1. Add module → Webhooks → Custom webhook → Add, name it and Save. Make generates the URL and starts listening.
2. Open Advanced settings. Set Get request headers to Yes so webhook-id, webhook-timestamp and webhook-signature are mappable. Set JSON pass-through to Yes if you plan to verify the signature: the body then reaches later modules as one text string, not as fields, so parse it first (Make's JSON parsing tools; we did not confirm the module name in a live account) before mapping id or data.sales_order_id. Leave pass-through off to get parsed fields straight away and skip the signature check. Whether the pass-through string is byte-exact is not stated in Make's docs, so test it once.
3. Subscribe the URL with either key. Make answers 200 “Accepted” at once, inside the 5-second window Atlas Labs allows.

   Method

   POST

   URL

   https://automationatlas.io/labs/api/v1/webhooks

   Headers

   Authorization: Bearer lab_off_YOUR_KEY
Content-Type: application/json

   Body

   {"url": "https://hook.<region>.make.com/…", "events": ["office.sales_order.accepted"]}

4. Send the test ping (POST /webhooks/{id}/test) and, if Make asks, click Re-determine data structure. Activate the scenario (scheduling ON; a webhook scenario runs instantly).
5. Signature. Make has no Standard Webhooks module. For a fictional sandbox you may accept unverified deliveries; otherwise compute the HMAC yourself (we have not confirmed which Make module or function can produce an HMAC-SHA256) or pass the raw string and headers to an external verifier (the algorithm is on the Webhooks page).

How do I call the Atlas Labs API from Make?

1. Add module → HTTP → Make a request. Set URL and Method, for example GET https://automationatlas.io/labs/api/v1/office/sales-orders/<id> to read the accepted order's quantity and due_sim_day.
2. Authentication type: API key → Credentials → Create a keychain. Name it “Atlas Labs Head Office”; Key Bearer lab_off_YOUR_KEY (type the word Bearer yourself); API key placement Header; API key parameter name Authorization. Make a second keychain, “Atlas Labs Factory”, for lab_fac_YOUR_KEY.

   Authentication type

   API key

   Keychain name

   Atlas Labs Factory

   Key

   Bearer lab_fac_YOUR_KEY

   API key placement

   Header

   Parameter name

   Authorization

3. For a write, set Body type Raw, Content type JSON (application/json) and paste the JSON into Request content. Add a Headers item Idempotency-Key mapped to the webhook-id header from the Custom webhook, or to the parsed body's id; both are the event id.

   Method

   POST

   URL

   https://automationatlas.io/labs/api/v1/factory/work-orders

   Headers

   Idempotency-Key = the webhook-id header

   Request content

   {"sales_order_id": "<sales_order_id from the parsed body>", "quantity": <from the order>, "due_date": <due_sim_day from the order>}

   Preset matters. Pick a preset with a manual bridge (Standard or Full) or this write returns 409 already_bridged, because Starter bridges automatically.

4. Turn on “Return error if HTTP request fails” so 4xx and 5xx stop the scenario and reach your error handlers.
5. Add a Router after the request: one route for 201 or 409 with error.code = already_bridged (success), a fallback route for everything else.

Idempotency and retries

• The HTTP module has no retry setting. In Scenario settings turn on Store incomplete executions, then attach the Retry error handler (earlier called Break) with your attempts and interval; Make's example is “try 3 more times, every 15 minutes”.
• Make reruns ConnectionError and RateLimitError automatically once incomplete executions are on; an instant scenario reruns the incomplete execution with exponential backoff. For a 429 from Atlas Labs the wait in Retry-After is usually one or two seconds.
• Calls made in parallel share one key's budget, for example when scenario runs overlap, so keep calls to Atlas Labs to one or two at a time: more at once only collect more 429s, and enough of them put the key into a short cooldown.
• Because the Idempotency-Key is the event id (the webhook-id header), a rerun returns the original response (Idempotency-Replayed: true) rather than a second work order.

Common errors

Gotchas

Download the blueprint

Questions people ask

Which Make modules do I use?

Webhooks → Custom webhook to receive, HTTP → Make a request to call. Nothing else is needed; a Router sorts the responses.

Which Make webhook hosts does Atlas Labs accept?

Any public HTTPS URL on port 443, and hook.<region>.make.com is on the list of shared platform hosts with a higher delivery allowance.

How do I treat a duplicate delivery?

As success. Deliveries are at-least-once; with the event id as Idempotency-Key a second delivery gets the original response, and a bridge that already happened returns 409 already_bridged.

Does Make verify the Standard Webhooks signature?

Not out of the box. Turn on Get request headers and JSON pass-through, then compute the HMAC yourself or skip verification for this fictional sandbox.

Why do I get 401 although the key is in the keychain?

The Key field must contain Bearer followed by the key; Make sends the Key value verbatim as the header value.

Can Make import the Atlas Labs OpenAPI file?

No official import exists for HTTP calls; a Make community thread confirms it. The HTTP module takes under a minute to fill in.

Sources (checked 15 Oct 2026): apps.make.com/http, apps.make.com/api-key-authentication-type, apps.make.com/gateway (Custom webhook), help.make.com/webhooks, help.make.com/fix-rate-limit-errors, help.make.com/retry-error-handler. Atlas Labs facts from the API source, observed live.