ASDK and Zapier: send website leads to any app

Every team keeps leads somewhere different: a CRM, a spreadsheet, a shared inbox, a project board. ASDK does not try to connect to all of them directly. Instead, it sends each new lead to a webhook, and Zapier, which connects to a long list of business apps, takes it from there. If your process lives in tools ASDK has no native connection for, this is the way in.

What ASDK and Zapier 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 Zapier, each new lead starts a Zap. What the Zap does next is up to you. Common examples:

• Create or update a contact in a CRM, such as HubSpot or Pipedrive, while ASDK's native connections for them are coming soon.
• Add a row to a spreadsheet that your team reviews every morning.
• Post an alert to a team chat channel, or email the account owner for a region.
• Create a task or a card in your project tool for every qualified lead.

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

How it works: Webhooks by Zapier

Zapier receives webhooks with its own Webhooks by Zapier app. According to Zapier's help center, the Catch Hook event gives you a unique URL, parses the body of each request it receives and splits the data into fields you can map in later steps (checked October 2026). The same article notes:

• A paid Zapier plan is needed. Webhooks by Zapier is available on Zapier's paid plans, not on the free plan.
• The URL changes if the Zap changes owner. When ownership of a Zap is transferred, update the URL in ASDK.
• A switched-off Zap stops accepting data. Its URL eventually returns an error, so leads sent while it is off are not processed by that Zap.

Set up a Zap for ASDK leads

An example Zap: qualified leads to the CRM, everyone to a sheet

Picture a B2B software company that uses the Sales agent with three qualifying questions and a score. Its Zap has four steps after the trigger:

1. Catch Hook receives the lead from ASDK.
2. Google Sheets adds a row for every lead, so marketing can see the full list, including people who were not a fit.
3. Filter continues only when the score meets the company's threshold.
4. HubSpot creates or updates the contact by email, and a team chat step posts a short alert for the account owner.

Every lead is recorded, but only the qualified ones create CRM records and interrupt a salesperson. When the company later switches on ASDK's native HubSpot connection, it can remove step 4 and keep the rest.

Start smaller than this. A Zap with one action that works every time beats a clever Zap nobody trusts. Add the filter and the second destination once you have seen a week of real leads, and you will know which fields your team actually reads and which ones can stay out of the CRM.

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 Zaps

• Use email as the key. When a Zap creates records, match on the visitor's email address so a returning visitor updates a record instead of creating a duplicate.
• Filter before you notify. A Zapier filter on the lead score, if you use the Sales agent, keeps alerts for the leads that need a fast reply.
• Watch for missing fields. Visitors do not always leave a company name or phone number. Give optional fields a fallback, or skip steps that need them.
• Keep the URL private. Anyone who has a Catch Hook URL can send data to your Zap. Paste it only into ASDK.
• Write down who owns the Zap. If the person who built it leaves, the URL changes when the Zap is transferred, and the leads stop arriving until ASDK has the new one.

If you prefer visual scenarios with routers and data stores, Make works the same way from ASDK's side: one webhook URL per destination.