April logoApril
Sign Up

Zapier & Make Automation

Send conversation data to Zapier or Make and trigger workflows across thousands of apps.

Connect a Zapier or Make webhook to let your agent push details it collects in a conversation straight into your automations. From there, your workflow can fan out to thousands of apps — add a row to a spreadsheet, post to Slack, create a task, open a ticket, or kick off a sequence — all without writing code.

Setup

Step 1: Create a webhook in Zapier or Make

If you use Zapier:

  1. Create a new Zap
  2. Choose Webhooks by Zapier as the trigger
  3. Select the Catch Hook event
  4. Copy the Custom Webhook URL Zapier gives you (it starts with https://hooks.zapier.com/hooks/catch/…)
  5. Build the rest of your Zap — add the actions you want to run when data arrives

If you use Make:

  1. Create a new scenario
  2. Add a Webhooks module as the first step
  3. Choose Custom webhook and click Add to create a new webhook
  4. Copy the address Make generates (it looks like https://hook.eu1.make.com/…)
  5. Add the downstream modules that should run when April sends data

Keep the webhook handy — you'll paste it into April next.

Step 2: Connect in April

  1. Open your chatbot in the April dashboard
  2. Go to Integrations in the sidebar
  3. Find Zapier or Make and click Connect
  4. Paste your webhook into the Webhook URL field
  5. Fill in When to use it — describe the situation that should trigger the workflow (for example, "When a visitor requests a quote, send their details to our sales pipeline.")
  6. Optionally add Fields to collect — a comma-separated list like name, email, company, request. Leave it empty to send a free-form summary instead.
  7. Click Connect Zapier (or Connect Make)

The webhook must be a valid Zapier or Make URL over HTTPS. April only accepts addresses on hooks.zapier.com for Zapier, or hook.<region>.make.com for Make.

Step 3: Test it

Go to the Playground and walk through the scenario you described in When to use it. When the agent has gathered the details, it sends them to your webhook. Check your Zap or scenario history to confirm the payload arrived, then turn your automation on.

How It Works

The two fields you fill in during setup shape exactly what the agent does:

  • When to use it tells the agent when to fire the workflow. The agent reads your description and triggers the automation only when the conversation matches that situation.
  • Fields to collect tells the agent what to gather before sending. Each field becomes something the agent asks for and includes in the payload.

When a conversation matches your description, the agent:

  1. Recognizes the moment — based on your When to use it description
  2. Collects the details — asks for each field you listed (or pulls together a short summary if you left fields empty)
  3. Sends the data — posts the collected information to your Zapier or Make webhook as JSON
  4. Continues naturally — confirms with the visitor and keeps helping

From there, your Zapier or Make workflow takes over and routes the data wherever you need it.

Example Conversation

Setup for this example — When to use it: "When a visitor asks for pricing or a quote, send their details to the sales pipeline." Fields to collect: name, email, company, request

Visitor: Hi, can I get a quote for the Enterprise plan for my team?

Agent: Happy to help get that moving! Can I grab a few details? What's your name and the best email to reach you?

Visitor: Jordan Lee, jordan@acme.co — we're at Acme, about 40 seats.

Agent: Thanks, Jordan! I've passed your request for an Enterprise quote (around 40 seats) to our sales team. Someone from Acme's account will follow up at jordan@acme.co shortly.

Behind the scenes, the agent sends name, email, company, and request to your webhook. Your Zap or scenario then creates the deal in your pipeline, notifies the sales channel in Slack, and logs the lead — whatever you've set up downstream.

FAQ

Which webhook URLs are accepted? Only Zapier Catch Hook URLs (hooks.zapier.com/…) and Make Custom webhook addresses (hook.<region>.make.com/…). Both must use HTTPS. To send data to a different endpoint, use the generic custom HTTP action instead.

What data gets sent? The fields you listed under Fields to collect, sent as a JSON payload. If you leave the fields empty, the agent sends a short free-form summary of the relevant information instead.

Can I require certain fields? Yes. The agent treats your listed fields as the information to gather and will ask for them before sending. Keep the list short and focused on what your workflow actually needs.

Does the agent decide when to fire on its own? It follows your When to use it description. The clearer and more specific that description is, the more reliably the agent triggers the workflow at the right moment — and only then.

Can I connect both Zapier and Make? You can connect both, but the agent sends to one automation at a time — it uses the first one connected (Zapier before Make). Keep only the one you want active if you need the data to land in a specific place.

What apps can I reach? Anything Zapier or Make connects to — Google Sheets, Slack, HubSpot, Salesforce, Pipedrive, Notion, Airtable, Trello, your CRM, your help desk, and thousands more. April hands the data to your workflow; your workflow handles the rest.

Tips

  • Write When to use it as a plain-language rule, not a keyword list — for example, "When a visitor wants to report a bug, send the details to our engineering tracker."
  • Match your Fields to collect to what the downstream app expects, so your Zap or scenario can map them cleanly.
  • Test end to end in the Playground with your Zap or scenario turned on before you deploy, so you can see real payloads land.
  • Embed the widget once you're happy, using your snippet:
<script data-chatbot="YOUR_CHATBOT_ID" src="https://theapril.app/widget.js"></script>