Automation integration

Multi-step scenarios, triggered by your referral pipeline.

Q: Can one event drive multiple actions?

Yes. Make’s routers split a single webhook into parallel branches, each with its own filters and apps.

Q: What is in the payload?

JSON with the event name, timestamp, and the referral or contact data, ready for Make’s visual field mapper.

Build powerful visual automations with Make (formerly Integromat). Design multi-step scenarios that react to Introzy events via webhooks, branching, filtering, and transforming along the way.

Event feed

pipeline_deal.stage_changedjust now

Router: if stage = Proposal → create task; else → update sheet

pipeline_deal.closed_won14m ago

Generate PDF statement → email partner → log to Notion

contact.created1h ago

Enrich → add to newsletter audience

Sample payload

{
  "event": "pipeline_deal.closed_won",
  "timestamp": "2026-09-04T14:12:09Z",
  "data": {
    "id": "deal_7f2k91",
    "name": "Harbor & Bell",
    "stage": "Closed won",
    "referralSource": "Dana Whitfield"
  }
}

Real event names, illustrative scenarios. Make’s routers and filters turn one webhook into an entire branching workflow.

What the connection does

Visual, multi-step automation scenarios

React to Introzy events in real time

Connect to hundreds of services

How it connects

Add a webhook module

Start a Make scenario with a custom webhook module and copy its URL.

Register it in Introzy

Paste the URL into Introzy’s webhook settings and choose which events to send.

Branch and build

Use Make’s routers, filters, and iterators to fan one event out into every system that cares.

make.com Make webhooks documentation

Useful on day one, whoever you are

For the team

One closed referral can update the sheet, email the partner, and notify finance, in a flowchart you can actually read.
Operations owns the automation without filing an engineering ticket.
Scenarios are visual, so the person who inherits them can follow them.

For the builder

Webhook-triggered scenarios; JSON payloads with { event, timestamp, data }.
Events cover the referral pipeline lifecycle plus contact create/update.
Automatic retry with exponential backoff on failed deliveries.

Questions teams ask

How is this different from the Zapier integration?

Same webhook events, different builder. Make favors visual multi-step scenarios with routers and iterators; Zapier favors quick linear Zaps. Pick the one your team already knows.

Can one event drive multiple actions?

What is in the payload?