Modes
- Post-call (Zapier and Make): after a call ends, Nixflex sends the full call data to your webhook. Your scenario then does whatever you build — create a CRM record, add a spreadsheet row, send a notification.
- In-call action (Make only): the AI calls your Make scenario during the call and uses the response live (for example, looking something up and reading it back). Zapier cannot return a synchronous response, so in-call is Make only.
Zapier — post-call
Create a Catch Hook trigger (Webhooks by Zapier) and copy its URL, then:post_call_url is required and must be https://. Read returns post_call_url_set: true (the URL itself is not returned); DELETE removes it:
Make — post-call and/or in-call
Make accepts a post-call URL, an in-call URL, or both. At least one is required.post_call_url— fires after the call (same as Zapier).in_call_url— the AI calls this during the call. Your Make scenario must end with a Webhook Response module returning JSON; the AI uses that response live.tool_name,tool_description, andparametersdescribe the tool to the AI so it knows what it does and what to send.
tool_description — the AI decides when to call the tool based on it.
Read returns which URLs are set plus the tool fields:
What gets sent (post-call)
Post-call delivery uses the same reliable engine as Webhooks — it retries on failure and stops on a bad URL. Your scenario receives the full call data: summary, sentiment, outcome, caller number, call details, transcript, and any extracted data.Connect via dashboard
Prefer the dashboard? Go to Integrations → Zapier (or Make), pick the agent and number, paste the webhook URL(s), and Save.Tips
- Test your Zap or scenario with one real call before relying on it.
- For Make in-call tools, keep the scenario fast — the AI waits for the response during the call (5 second limit).
- Each number is independent — different numbers can trigger different scenarios via per-number setup.