ASDK and Make: send website leads to any scenario

Make shows each automation as a visual scenario: a trigger, a router, a few branches, each with its own steps. ASDK fits in at the start of that diagram. Every lead its agents capture can be sent to a Make webhook, and your scenario decides where it goes, whether that is a CRM, a spreadsheet, a team chat or all three.

What ASDK and Make do together

ASDK's agents capture leads during website conversations:

• Chat (early access, from the Free plan) answers visitors from your content and, when it cannot help, offers to take their contact details.
• Sales (early access, from the Pro plan) asks the qualifying questions you write in plain language, scores each lead by your rules and offers a meeting to visitors who fit.

With a webhook to Make, each new lead runs your scenario. Typical scenarios:

• Route by fit. A router sends high-scoring leads to your CRM and an alert channel, and everyone else to a nurture list.
• Route by region or product. A filter on what the visitor told the agent picks the right owner.
• Keep a record. Every lead becomes a row in a sheet or a record in a data store, alongside your CRM.
• Bridge to a CRM such as Pipedrive or HubSpot while ASDK's native connections for them are coming soon.

ASDK sends webhooks in early access, from the Starter plan.

How it works: Make's custom webhooks

Make receives webhooks with the Custom webhook module of its Webhooks app. According to Make's Webhooks app documentation, saving a new webhook makes Make generate a URL and start listening for requests, and it accepts JSON, form data and query strings (checked October 2026). A few rules from Make's webhooks help page and the app documentation are worth knowing:

• Instant runs. A scenario with an instant webhook runs as soon as a request arrives. By default, runs can happen in parallel; a scenario setting processes them in order instead.
• One webhook, one scenario. You cannot use the same webhook in more than one scenario. For a second destination, add a second route inside the scenario.
• Idle webhooks are switched off. A webhook that is not connected to any scenario for more than five days is deactivated and returns an error.
• Queues and rate limits. Each webhook has its own queue, and Make can process up to 300 incoming webhook requests per 10 seconds. That is far more than lead traffic from a website usually needs.

Set up a Make scenario for ASDK leads

An example scenario: one webhook, three routes

Picture a logistics company whose website gets quote requests from shippers and job questions from drivers. It uses Chat for questions and the Sales agent for quote requests. Its scenario looks like this:

1. Custom webhook receives each lead from ASDK.
2. Router splits the bundle into three routes.
3. Route one, for leads with a high score, creates a person and a lead in the CRM and posts an alert to the sales channel.
4. Route two, for leads that mention a driver job, sends an email to the recruiting inbox.
5. Route three, for everything else, adds a row to a sheet that someone reviews daily.

Each route has a filter on fields the agents collected, so nobody has to sort leads by hand. Build one route first, test it with real leads for a week, then add the next.

What is available and what is coming soon

ASDK as a whole is in early access: webhooks work and you can use them, but details may change while we improve them.

Tips for reliable scenarios

• Define the data structure once you have a sample. Make can validate incoming data against a structure; without one, it accepts anything, and later modules may fail on a missing field.
• Match records by email. When a scenario creates contacts, search by the visitor's email first so a returning visitor updates a record instead of creating a duplicate.
• Handle optional fields. Visitors do not always leave a phone number or a company. Add fallbacks or skip steps that need them.
• Protect the URL. Anyone who has the webhook URL can send data to it. Paste it only into ASDK, and use Make's options for API keys or IP restrictions if your policy requires them.
• Watch the scenario's history. A failed run shows up in Make's history and logs. Check it after you change a destination's fields.

Prefer a step-by-step builder to a diagram? Zapier works the same way from ASDK's side: one webhook URL per destination.