# Zapier

> Connect the Webphone to Zapier so call events start automations in thousands of other apps.

- URL: https://kb.voipcloud.online/au/integrations/zapier/
- Section: Integrations
- Type: guide
- Applies to: All countries
- Portal page: /integrations/zapier
- Last reviewed: 2026-11-09

With Zapier, Webphone calls can start automations in other apps. For example, add a row to a Google Sheet when a call ends, or create a lead in your CRM when a call is answered. You activate Zapier once in the portal, then connect each user's Webphone in Zapier.

## Before you start

- The **Integrations** licence must be on: **Services** › **PBX licences** › **Advanced features**. See [Integrations overview](https://kb.voipcloud.online/au/integrations/integrations-overview/#the-integrations-licence).
- You need a Zapier account.
- Each user you connect needs a Webphone account (an **Email** under **Webphone** in their [User](https://kb.voipcloud.online/au/pbx/accept-make-divert/user/) settings), and must be able to sign in to the Webphone while you connect them.

## 1. Activate Zapier in the portal

1. Go to **Integrations** › **Zapier**.
2. Click **Activate**.

Zapier is then available to every user with a Webphone account.

## 2. Connect a user's Webphone in Zapier

**Note:** Menus can change between versions. If a label is different, check the vendor's own help.

1. Sign in to Zapier and open the list of your connected apps.
2. Search for the **Webphone** app and click **Connect**.
3. Choose the country of your service and continue.
4. Sign in to the user's Webphone when asked, and authorise the connection. The user must be signed in to the Webphone while you connect.
5. To connect another user, add another connection to the same Webphone app in Zapier and repeat steps 3 and 4.

## 3. Create a Zap

1. In Zapier, create a Zap and choose the **Webphone** app as the trigger.
2. Choose a trigger event (see the table below) and the user's connection.
3. Choose the call direction: incoming, outgoing or both. For **Call Ended**, also choose answered, unanswered or both.
4. Add the action in the other app, for example a new row in a Google Sheet, and map the call fields to it.
5. Turn the Zap on.
6. Reload the user's Webphone. It picks up changes made in Zapier only after a reload.

In the Webphone, **Settings** › **Integrations** shows Zapier under **Automation**, marked **Enabled** or **Disabled** for that user.

## Triggers and data

| Trigger | When it fires | Data sent |
| --- | --- | --- |
| **Call Started** | A call starts ringing on the Webphone, or the user starts an outbound call. Useful to look up the caller before answering. | Agent (user) name, inbound number or outbound number, caller's number or dialled number, call direction, call start time. |
| **Call Answered** | A call is answered on the Webphone. | As **Call Started**, plus call answer time. |
| **Call Ended** | A call ends. | As **Call Answered**, plus call status (answered or unanswered) and call end time. |

The fields mean:

| Field | What it is |
| --- | --- |
| Agent (user) name | The name of the User in the PBX. |
| Inbound number / Outbound number | For incoming calls, the number the caller dialled. For outgoing calls, the number the user called from. |
| Inbound caller's ID / Outbound dialled number | For incoming calls, the caller's number. For outgoing calls, the number the user dialled. |
| Call direction | Incoming or outgoing. |
| Call start, answer and end time | Date and time with the UTC offset, for example `2026-10-29T18:00:18+11:00`. |
| Call status | Answered or unanswered (**Call Ended** only). |

## Check it works

1. Make a test call to or from a connected user's Webphone.
2. In Zapier, open the Zap's history and check that the trigger ran and the action succeeded.

If nothing arrives, check that the user was signed in to the Webphone when you connected, that Zapier is activated in the portal, and that Zapier isn't turned off for that user.

## Turn Zapier off for one user

Open the user's **User** object in the PBX and turn off Zapier under **Webphone** › **Integrations**. See [Integrations overview](https://kb.voipcloud.online/au/integrations/integrations-overview/#turn-an-integration-off-for-one-user).

## Related

- [Integrations overview](https://kb.voipcloud.online/au/integrations/integrations-overview/)
- [Webhooks](https://kb.voipcloud.online/au/integrations/webhooks/), for events from the whole PBX, not just the Webphone