> For the complete documentation index, see [llms.txt](https://support.ventla.io/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ventla.io/kb/integrations/zapier.md).

# Zapier

Enabling Zapier integration in Ventla

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2FK36ZvjQPZLLyTuSF5PHJ%2Ffor_gitbook.png?alt=media&amp;token=0788c0cb-7cb2-49b3-8170-b52c73c3eeda" alt=""><figcaption><p>Click to enlarge</p></figcaption></figure>

{% hint style="info" %}
Your app needs to be enabled for the Zapier integration. This can be done by reaching out to <support@ventla.io>
{% endhint %}

## Configuration

Once the app has Zapier integration enabled, you can turn Zapier integration on or off per event.

This is done under “Settings” -> “Features & Integrations”.

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2FSFpE3QCn5qELHpoqT3iq%2FBild2.png?alt=media&amp;token=87735e0a-d7d9-4dc2-ace7-be75f8b27904" alt=""><figcaption><p>Click to enlarge</p></figcaption></figure>

When enabling Zapier functionality for an event you will be presented with an API key, this API key is the same for all events.

The API key is used for authenticating your Zapier Zap with Ventla. Copy this and use it while setting up your Zap.

{% hint style="warning" %}
**Important notes**

Zapier is enabled per event but configured based on application. This means that one Zap in Zapier can handle triggers for multiple events. The triggering of the Zap will only happen for events where Zapier is enabled under Settings -> Features & integrations.

Hence it is only necessary to create a Zap the first time the Zapier integration is enabled.

Each Zap works on one specific Ventla Trigger. Allowing you to define which of the Ventla trigger events you want to subscribe to.

Carefully consider that your Zapier subscription plan is capable of handle the number of expected triggers for your events.
{% endhint %}

### Setting up a Zapier Zap for Ventla

1. Start by creating a new Zap on your Zapier.com subscription.

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2F9r1LgyxTbGdv2SmcKJ18%2FBild4.png?alt=media&amp;token=5dfe99f1-a3db-4383-920a-c88ea1b2cc98" alt=""><figcaption><p>Click to enlarge</p></figcaption></figure>

2. Click on select “Trigger” and search for “Ventla”. Click to select.

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2Fm5cj7PpRFTZras0aJNvI%2FBild5.png?alt=media&amp;token=a7df871d-cdf8-4e31-874d-6556f86406eb" alt=""><figcaption><p>Click to enlarge</p></figcaption></figure>

3. Select trigger event to subscribe to

In the right hand side of Zapier, select the appropriate trigger for event to subscribe to

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2FIo4JhtplMJ1pppwfsRrO%2FBild6.png?alt=media&amp;token=ccae45be-6b18-4467-b211-763d5244c9ee" alt=""><figcaption><p>Click to enlarge </p></figcaption></figure>

4. On the “Account” tab click connect to enter your API key (obtain from Ventla Admin)

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2FkR28wDkQVu4OpNcrt2zY%2FBild7.png?alt=media&amp;token=414c93c8-b243-4e1d-ba5b-d3084baa16f9" alt=""><figcaption><p>Click to enlarge</p></figcaption></figure>

5. Click continue
6. Optionally test the trigger to review the triggers data fields
7. Configure the Zapier “Action” by clicking on “Action”
   1. This is defining where Zapier will send the data from Ventla
8. In this example we will select Hubspot

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2FR6TEBTdtpWLdbdSImzHw%2FBild8.png?alt=media&amp;token=004eda21-a224-4098-8a50-1123a0a8c602" alt=""><figcaption><p>Click to enlarge </p></figcaption></figure>

9. Continue by setting up the details of the action, here we will create a new contact in Hubspot based on the accepted invitees information.

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2Fk5tsDjQdyFpMqFZXhRpG%2FBild9.png?alt=media&amp;token=5ad937aa-68a5-4207-8cac-8a2057afb1f6" alt=""><figcaption><p>Click to enlarge </p></figcaption></figure>

10. Configure the account

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2FJa8NXznTPlDInWJa7PDD%2FBild10.png?alt=media&amp;token=e9f73a93-bc50-4bc6-9342-387e4b67ca77" alt=""><figcaption><p>Click to enlarge</p></figcaption></figure>

11. Map the Ventla output data to the Hubspot input data

Here is an example on how we map the First name and Last name obtained from Ventla to the new contact record in Hubspot.

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2FnySUf0sB98INEkQ9867z%2FBild11.png?alt=media&amp;token=548e5c92-1aee-49d3-8402-a5b80e15aeb4" alt=""><figcaption><p>Click to enlarge</p></figcaption></figure>

12. &#x20;When done with the action configuration move ahead to test it.
13. When done with testing you can now publish your Zap. Once the Zap is published it will automatically run the configured action every time the Ventla trigger condition is applied.

Your final Zap shall look something like this:

<figure><img src="https://117182291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ1spIYLb1bYBR8mzUcvA%2Fuploads%2FcTBW6zb8yxuNLEJ1NoSu%2FBild12.png?alt=media&amp;token=afbd71d2-4e10-4b97-91de-c6685c493544" alt=""><figcaption><p>Click to enlarge</p></figcaption></figure>

## Current trigger support and data-formats

**Accepted invitation to event**

Triggers in Ventla Invite when an invitee registers for an event, or when an administrator manually sets and invitee to “Accepted” status.

**Data format**

<table data-header-hidden><thead><tr><th></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>First name</strong></td><td>Name of invitee</td><td></td></tr><tr><td><strong>Last name</strong></td><td>Name of invitee</td><td></td></tr><tr><td><strong>Company</strong></td><td>Company name for the invitee</td><td></td></tr><tr><td><strong>Phone</strong></td><td>Phone number to the invitee</td><td></td></tr><tr><td><strong>Job title</strong></td><td>Job title of invitee</td><td></td></tr><tr><td><strong>Email</strong></td><td>Email address of invitee</td><td></td></tr><tr><td><strong>Event name</strong></td><td>The name of the event the invitee accepted an invitation for</td><td></td></tr></tbody></table>

*Have questions? Contact <support@ventla.io>*
