Ask Immiscible from a Make scenario

A Make scenario cannot pause until an outside service calls it, so a decision that needs a person splits into two scenarios: one asks, the other starts from a custom webhook that Immiscible calls.

#Before you start

Make an agent key: Agents, Add an agent, then Collect the agent’s key on its setup page. Every request below sends it as the header x-api-key.

#Scenario 2: carry on (make this first)

1. Trigger: Webhooks, Custom webhook. Copy its address.
2. HTTP, Make a request: method GET, URL https://immiscible.fly.dev/v1/actions/ followed by actionId from the webhook, header x-api-key, parse response on. This reads the decision with your key; the webhook alone proves nothing.
3. Filter: decision equal to allow.
4. Your action.
5. HTTP, Make a request: method POST, URL https://immiscible.fly.dev/v1/actions/ followed by actionId and /settle, body type JSON, content { "status": "completed" }.

#Scenario 1: ask

1. Your trigger, as now.
2. HTTP, Make a request: method POST, URL https://immiscible.fly.dev/v1/actions/authorize, header x-api-key, body type JSON, content describing the action (the same shape as the Zapier recipe), parse response on.
3. Router:
   • decision equal to allow: your action, then settle as in scenario 2.
   • decision equal to approval_required: HTTP, Make a request, method POST, URL https://immiscible.fly.dev/v1/actions/ followed by id and /callback, content { "url": "<the custom webhook address>" }.
   • decision equal to deny: stop, and send the reasons to someone.

When the approver decides, Immiscible calls the webhook with { "actionId", "decision", "status", "decidedAt" } and scenario 2 runs.

#Or by MCP

Make’s MCP Client app can call Immiscible’s tools from a scenario or a Make AI agent: server URL https://immiscible.fly.dev/mcp, an agent key as the token.