> For the complete documentation index, see [llms.txt](https://distance.gitbook.io/distance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://distance.gitbook.io/distance/getting-started/integrations/setting-up-integration-with-zapier.md).
# Setting up integration with Zapier
Connect Distance to Zapier to enable automated workflows with third-party applications and configure Distance as either a Trigger or an Action.
### **Setting up integration with Zapier**
Zapier connects Distance to external applications, enabling automated workflows between Distance and other platforms such as CRMs, project tools, and messaging systems.
This integration is used to either send data from Distance to external apps or trigger messages in Distance based on events from external systems. All workflows are routed through Zapier as the bridge between platforms.
***
### **How the integration works**
Zapier can be configured in two directions depending on your use case:
#### **Distance as the trigger (outbound automation)**
When Distance is used as the trigger app, it can send data to external tools when events occur.
Available **Trigger events** include:
* **Contact Updated**
* **New Contact**
* **New Ticket**
* **Ticket Updated**
These triggers allow external systems to respond to activity in Distance, such as updating a CRM or logging data in another platform.
#### **Distance as an action (inbound automation)**
When Distance is used as an action inside a Zap, it receives data from external applications.
Available **Action events** include:
* **Create Contact**
* **Update Contact**
* **Enroll in Trigger**
The **Enroll in Trigger** action connects Zapier workflows to Distance [**automations**](/distance/getting-started/automations/setting-up-an-automation.md#creating-an-automation). When triggered from an external app, it allows Distance to send messages (Email or SMS) through configured automations.
In Distance, this works through the [**When this happens…**](/distance/getting-started/automations/setting-up-an-automation.md#when-this-happens) section when creating an automation. You can choose between **Distance event** and **Integration event**.
* **Distance event** refers to actions that originate inside Distance. These include **Form submitted**, **Call dropped**, **Contact updated**, and **Trigger enrollmen**t.
* For Zapier-based workflows, you must select **Trigger enrollment**, which allows external systems to initiate a Distance automation.
* **Integration event** refers to external applications connected through [**Settings** → **Integrations**](/distance/getting-started/settings/integrations-tab.md). These are used when Distance is reacting to events coming from connected third-party tools.
This setup ensures that **Enroll in Trigger only works when Trigger enrollment is selected**, and is used specifically to receive triggers from external applications through Zapier.
This setup is one-way: External application → Zapier → Distance
It is commonly used when an external event needs to trigger communication from Distance, such as sending a message when a deal stage changes or a project is updated.
***
### **Key limitation**
Zapier workflows are **one-way**. Each Zap starts with a single trigger and sends data in one direction only.
When integrating with Distance, each workflow must be designed as either:
* **Distance → Zapier → External application** (send data from Distance to another platform)
* **External application → Zapier → Distance** (trigger actions or messaging in Distance)
If you need synchronization in both directions, create **two separate Zaps**—one for each direction of data flow.
***
### **Access Zapier**
In Distance, go to **Settings**, then open **Integrations**. Locate **Zapier** under [**Essential integrations**](/distance/getting-started/settings/integrations-tab.md#essential-integrations) and click **View now**.
You will be redirected to **Zapier**. Click **Accept Invite & Build a Zap**.
***
### **Configure Distance in Zapier**
Distance can be used in Zapier in two different ways depending on your workflow:
* As a **trigger app**, where events in Distance start a workflow in an external system
* As an **action app**, where external events trigger actions inside Distance
Choose the setup that matches your use case.
#### **Option 1: Distance as the trigger**
In the Zap editor, click the **Trigger step**, search for **Distance**, select **Distance (2.0.0).**
In the configuration panel, select a **Trigger event** such as **Contact Updated**, **New Contact**, **New Ticket**, or **Ticket Updated**.
Click the **Account** field, then in the authorization window, click **Yes, Continue to Distance (2.0.0)** to allow Zapier to access your Distance account.
On the **Connect Distance to Zapier** screen, click **Confirm**.
#### **Option 2: Distance as an action**
In this setup, an external application triggers a workflow that performs actions inside Distance.
Complete the trigger step in your external application. In the **Test** sub-panel, click **Continue with selected record**, and Zapier will automatically generate the next step in the workflow.
Search for **Distance**, select **Distance (2.0.0).**
In the configuration panel, select an **Action event** such as **Create Contact**, **Enroll in Trigger**, or **Update Contact.**
Click the **Account** field, then in the authorization window, click **Yes, Continue to Distance (2.0.0)** to allow Zapier to access your Distance account.
On the **Connect Distance to Zapier** screen, click **Confirm**.
***
### **Continue with your integration**
Distance is now connected to **Zapier**.
The remaining configuration depends on the third-party application you are integrating and may include mapping fields, configuring filters, and adding additional workflow steps.
Refer to the appropriate integration guide for detailed instructions specific to your platform.
