Zapier
Enabling Zapier integration in Ventla
Last updated
Was this helpful?
Enabling Zapier integration in Ventla
Last updated
Was this helpful?
Your app needs to be enabled for the Zapier integration. This can be done by reaching out to support@ventla.io
Once the app has Zapier integration enabled, you can turn Zapier integration on or off per event.
This is done under “Settings” -> “Features & Integrations”.
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.
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.
Start by creating a new Zap on your Zapier.com subscription.
Click on select “Trigger” and search for “Ventla”. Click to select.
Select trigger event to subscribe to
In the right hand side of Zapier, select the appropriate trigger for event to subscribe to
On the “Account” tab click connect to enter your API key (obtain from Ventla Admin)
Click continue
Optionally test the trigger to review the triggers data fields
Configure the Zapier “Action” by clicking on “Action”
This is defining where Zapier will send the data from Ventla
In this example we will select Hubspot
Continue by setting up the details of the action, here we will create a new contact in Hubspot based on the accepted invitees information.
Configure the account
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.
When done with the action configuration move ahead to test it.
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:
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
First name
Name of invitee
Last name
Name of invitee
Company
Company name for the invitee
Phone
Phone number to the invitee
Job title
Job title of invitee
Email address of invitee
Event name
The name of the event the invitee accepted an invitation for
Have questions? Contact support@ventla.io
