> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.bitbybit.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Zapier with bitbybit

> Connect Zapier to bitbybit through webhooks and HTTP requests to automate workflows across 9,000+ apps. Trigger Zaps from bitbybit events and trigger bitbybit actions from Zaps.

## Overview

bitbybit does not have a native, one-click Zapier app. Instead, you connect the two through bitbybit's webhooks and HTTP-request actions. This lets you move data in both directions:

* **bitbybit event → Zapier:** bitbybit fires a webhook to a "Webhooks by Zapier" Catch Hook trigger, so any bitbybit event can start a Zap across Zapier's 9,000+ apps.
* **Zapier → bitbybit:** a Zap calls the bitbybit API through an HTTP-request action, so any app in Zapier can trigger a bitbybit action.

Because the connection runs over webhooks, review the [Webhooks overview](/api-reference/webhooks/overview) and the [Webhook events](/api-reference/webhooks/events) reference before you begin. They describe the available events, payloads, and headers you will work with in Zapier.

## Before you begin

Make sure you have the following:

* A Zapier account with permission to create Zaps.
* Access to your bitbybit dashboard, including **Settings > Developer** to register webhook endpoints and **Settings > Advanced settings** to copy your API key.
* A basic understanding of bitbybit webhooks. Read the [Webhooks overview](/api-reference/webhooks/overview) for setup, signature verification, and retry behavior, and the [Webhook events](/api-reference/webhooks/events) reference for the full list of events and payloads.

## Step 1: Trigger a Zap from a bitbybit event

Use this direction when you want a bitbybit event — such as `customer.created`, `order.created`, or `message.received` — to start a Zap.

1. In Zapier, create a new Zap and choose **Webhooks by Zapier** as the trigger app.

2. Select the **Catch Hook** trigger event, then continue.

3. Copy the custom webhook URL that Zapier generates. This is the endpoint bitbybit will send events to.

4. In your bitbybit dashboard, go to **Settings > Developer** and click **Create Webhook**.

5. Paste the Zapier webhook URL into the **Endpoint URL** field, select the events you want to send, and save. After creation, store the signing secret securely.

6. Back in Zapier, test the trigger so it captures a sample payload from bitbybit, then map the fields into the rest of your Zap.

For the structure of each event payload and the headers bitbybit sends, see the [Webhook events](/api-reference/webhooks/events) reference.

## Step 2: Trigger a bitbybit action from a Zap

Use this direction when you want an app in Zapier to trigger a bitbybit action, such as sending a WhatsApp message.

1. In bitbybit, go to [Advanced settings](https://app.bitbybit.studio/settings?section=advance-settings) and copy your API key.

2. In your Zap, add an action step and choose the **Webhooks by Zapier** app.

3. Select the **Custom Request** action event, then continue.

4. Configure the request:
   * Set the method to **POST**.
   * Enter the bitbybit API endpoint URL for the action you want to run, for example `https://api.bitbybit.studio/whatsapp/api/v3.1/message`.
   * Add a header with the key `x-bitbybit-key` and your API key as the value.
   * Set the data (request body) using fields from your earlier Zap steps.

5. Test the action to confirm Zapier sends the request and bitbybit returns a success response, then turn on your Zap.

For the full list of API endpoints and request formats, see the [bitbybit WhatsApp API documentation](https://api.bitbybit.studio/whatsapp/docs).

## Verify

Confirm the connection works in both directions:

* **bitbybit event → Zapier:** trigger the subscribed event in bitbybit (for example, create a test customer or send an inbound message), then open your Zap's history in Zapier to confirm the Catch Hook received the payload.
* **Zapier → bitbybit:** run the Zap that calls the bitbybit API, then confirm the action completed in bitbybit (for example, that the message was sent).

If an event does not arrive in Zapier, check the webhook delivery status in **Settings > Developer** and review the retry behavior in the [Webhooks overview](/api-reference/webhooks/overview).