Crelate’s Zapier integration connects Crelate to more than 1,500 web services, so you can automate everyday tasks without writing code. It is available on Business and higher subscriptions.
What is Zapier?
Zapier is an online integration platform. You build automations, called Zaps, from triggers and actions. A trigger is an event that starts a Zap, and an action is what the Zap does in another app.
What do you need to use Zapier with Crelate?
You need a Zapier account and a Crelate API key. API access is available on Business and higher subscriptions, and an admin must allow API Access for non-admin users. See API Key Management and Documentation.
Where do you find the Zapier getting started guides in Crelate?
How do you set up the Zapier integration?
Create a Zap in Zapier. Choose Crelate as the trigger app, then select the trigger event.
Connect to Crelate. Use your Crelate API key to authenticate.
Configure the Zap. Map the fields between Crelate and the other app so data flows correctly.
Test the Zap. Run a test to confirm that the trigger and action work.
For a full walkthrough, see Creating a Zap.
Which triggers, actions, and searches are available?
Triggers start a Zap when something changes in Crelate:
New Contact
New Company
New Job
Updated Contact
Updated Company
Updated Job
Actions are what Zapier does in Crelate:
Create Contact
Create Company
Create Job
Create Task
Create Note
Update Contact
Update Company
Update Job
Searches find a record in Crelate by name, email, Crelate ID, or External ID:
Find Contact
Find Company
Find Job
Update actions need a Crelate ID to know which record to update. You can enter the ID directly in the Zap, keep it as an external ID in the trigger app, or retrieve it with a search step.
💡 Pro Tip: If your Zap updates a Contact, Company, or Job, add a Find step first. The Find step looks up the Crelate ID so the update goes to the right record.
How are Zapier triggers different from Crelate webhooks?
Zapier registers its own triggers for you. When you create a Zap with a Crelate trigger and connect it with your API key, Zapier registers the trigger on that user’s API key automatically. You do not add it yourself.
A Crelate webhook is separate. An admin adds a webhook in Security > API Access to send record changes to any address. Webhooks are available only on Business Plus and Enterprise plans, while Zapier works on Business and higher. See Configuring Webhooks.
Where do you see your Zapier triggers in Crelate?
On Business Plus and Enterprise plans, admins can see them in Security > API Access. Select the user whose API key the Zap uses, then look in the Webhooks section. A Zapier trigger appears only after the Zap has run at least once.
The Webhooks section is not available on Business plans. On a Business plan, manage your Zaps in Zapier.
Why is a Zapier trigger not showing in Crelate?
Check each of the following:
Your organization is on a Business Plus or Enterprise plan. The Webhooks list is not available on Business plans.
The Zap is connected to the correct Crelate user and API key.
The API key is active. API access must be on, and an admin must not have cleared the key.
The Zap has run at least once, which registers the trigger.
The field mappings in Zapier are correct.
What happens to your Zaps if an API key changes?
A Zap stops working when the API key it uses stops working. This happens when a user regenerates the key, when an admin clears the key, and when API access is turned off.
Regenerated key: Update the Crelate connection in Zapier with the new key.
API access turned off: Turn it back on. The same key works again, and your Zaps resume.
How can you keep Zapier integrations secure?
Keep your API key private, and review your Zaps in Zapier regularly. On Business Plus and Enterprise plans, you can also review the Webhooks list in Security > API Access to see which triggers are active.