What is Zapier?
Contactually has integrations to several other products, and other products have integrations with Contactually. However, sometimes you are looking to connect Contactually with services where there is no integration. This is where Zapier can help.
Think of Zapier like a connector. Zapier helps build an integration between the services you use. Services publish “apps” to Zapier, allowing you to trigger an automated workflow based on a condition in one app, which then causes an action in another app. This saves you a lot of time and effort because it happens consistently and automatically each time the situation occurs.
These workflows are called Zaps. There are templates available for existing Zaps using Contactually, but you can also easily create your own.
How does Zapier work?
Zapier uses Zaps to connect Contactually with other apps. Zaps are made up of triggers and actions. A trigger is an event that happens in the first app and an action is an event that Zapier automatically performs in the second app.
Choosing Contactually as the trigger app
If you choose Contactually as the trigger app, i.e. the app that sends data, the contact will be pushed to the second app to start the workflow. You can choose whether to send all new contacts as they are created, or to only send a contact once it is Bucketed in a Bucket(s) of your choosing.
Choosing Contactually as the action app
If you choose Contactually as the second app, i.e. the app that receives data, you can choose any of the actions below to occur.
- Create contact
- Bucket a contact
- Create Task
- Create contact history/Interaction
How to create a Zap
A Zapier account is needed to create a Zap. If you start with a Zap template, you can just add your credentials for each app and you'll be ready to go. To build a Zap from scratch, you'll follow the basic outline below:
1. Choose a trigger and an action.
2. Connect app 1 (trigger app), choose your trigger (the action that starts the Zap), and provide your credentials for that app.
3. Add an optional filter if you want to choose only certain records to continue the Zap.
4. Connect app 2 (action app), choose your action (what should happen in that app), and provide your credentials for that app. As part of this step, you'll map the data coming in from app 1 into app 2.
5. Test the Zap, name it, and turn it on.
Does the action "Create Interaction" mean the email content will be logged?
No. Only the email's time and date will be logged. The subject line may also be logged, but only if you mapped that field when creating the Zap.
The Zap doesn't seem to be working; I don't see new or updated contacts. How do I know if an error is occurring?
Go to your Task History in Zapier to see if the Zap has been experiencing any issues or check last time it sent data. If no issues are shown, check if any of the below could be causing problems.
- Make sure the Zap is correctly mapped based on what you want to occur.
- Make sure your username and password for both the trigger and actions apps are correct.
- If the Zap is not creating contacts in Contactually, check that the trigger app's contacts have email addresses, first name, or last name. One of these is required to create a contact in Contactually.
- If the Zap is not Bucketing contacts in Contactually, check that the trigger app's contacts have email addresses and that you've specified an appropriate Bucket.
- If the Zap is not creating Tasks in Contactually, check that the trigger app's contacts have email addresses and that you've specified the Task title and due date.
- If the Zap is not logging any contact history in Contactually, check that the trigger app's contacts have email addresses and log the times' emails were sent or received.
If you still need assistance, Zapier's tech support will be able to assist you. Don't worry—they'll reach out to Contactually if they need more information from us.