# Send to Zapier

Add a Send to Zapier step to an action, and start a Zap with the details the AI receptionist collected during a chat, a text conversation or a call.

Updated Nov 18, 2026. Source: https://smallbusinesschatbot.com/docs/user-guides/conversation-actions/send-to-zapier

## What this does

A **Send to Zapier** step sends an action's details to Zapier while the conversation carries on. The AI receptionist in Small Business Chatbot replies without waiting for the Zap. Use it to pass what a customer asked for into another app: a job request in your field service tool, a lead in your CRM, a row in a spreadsheet.

- **Where:** [Conversation Actions](https://smallbusinesschatbot.com/app?panel=tools) › an action › **Steps** › **Type**: Send to Zapier
- **Starts:** Every Zap that is on and starts with the **Conversation Action Called** trigger
- **In one action:** One such step, anywhere in the list
- **Counts as:** A change, so the [limits](https://smallbusinesschatbot.com/docs/user-guides/conversation-actions#limits) on those runs apply

## Add the step to an action

1. **Open the action**

   In the app, open **Conversation Actions** and click **Edit** on the action's card.

2. **Add the step**

   Under **Steps**, click **Add step** and change **Type** to **Send to Zapier**. The step has no settings of its own.

3. **Place it**

   Move the step with the arrow buttons. It sends the action's parameters and the fields kept by the steps before it.

4. **Save**

   Click **Save**. Until a Zap is on for this action, the card shows "No Zap is listening for this action."

## Build the Zap

1. **Pick the trigger**

   In Zapier, create a Zap. For its trigger, choose the Small Business Chatbot app and the **Conversation Action Called** event. [Zapier](https://smallbusinesschatbot.com/docs/integrations/automation/zapier) covers signing in from Zapier.

2. **Choose the action**

   Under **Action**, pick the action by name. Leave it empty to run the Zap for every action that has a **Send to Zapier** step.

3. **Test the trigger**

   In Zapier, test the trigger. It shows the action's most recent runs. For an action that has not run yet, it shows one sample with the action's own fields.

4. **Map the fields**

   Add the Zap's action steps and map the fields into them, such as **Parameter: service_type** into a job description.

5. **Turn the Zap on**

   Turn the Zap on, then reload **Conversation Actions**. The warning on the action's card is gone.

6. **Run it once**

   In the action editor, under **Test**, fill in the parameters and click **Run for real**. The step's result reads "Sent to 1 Zap(s)." and the run shows in your Zap history.

## What Zapier receives

| Field in Zapier | What it holds | Where it comes from |
|---|---|---|
| **Action name**, **Action ID** | The action that ran | The action |
| **Channel** | `chat`, `text` or `phone` | The conversation |
| **Conversation ID** | The chat, the text conversation or the call | The conversation |
| **Contact phone** | The phone number of the caller or of the person texting. It is empty for a website chat. | The phone carrier |
| **Parameter:** and a parameter's name | One field for each of the action's parameters, such as **Parameter: service_type** | The customer, as said or typed |
| **Step** and a step's name and field | One field for each field kept by a step before this one, such as **Step look_up: price** | Your lookup table or your system |
| **Test run** | True for a run from the action editor's **Test** | The app |

Send messages to **Contact phone**. A phone number or an email under a parameter is whatever the customer said, so use parameters for the content of a record and the contact for who it belongs to.

## Change the action later

The fields follow the action. After you add a parameter, test the trigger again in Zapier and the new field is there to map. After you rename or remove a parameter, open the Zap and map that field again.

## If something goes wrong

| What you see | Why | What to do |
|---|---|---|
| **No Zap is listening for this action. In Zapier, start a Zap with the "Conversation Action Called" trigger and turn the Zap on.** | No Zap that is on names this action or takes every action. | Turn the Zap on, then reload **Conversation Actions**. |
| **An action can have one "Send to Zapier" step.** | The action has two of these steps. | Remove one. One step runs every Zap that listens for the action. |
| In Zapier: **That Conversation Action no longer exists. Pick another one.** | The Zap's **Action** is an action that has since been deleted. | Pick another action under **Action**, or leave it empty, and turn the Zap on again. |
| The action ran, and the Zap has no run | The action stopped at a step before this one, or the Zap is off. | Run **Test** in the action editor to see which step stopped it, and check the Zap in Zapier. |
