You can use Cobot as a basic CRM to track leads and members. However, if you’re already using a more powerful CRM (or plan to), Cobot’s Zapier integration allows you to send member data directly from Cobot into that CRM—saving you duplicate work.
How It Works
When set up correctly, the workflow works like this:
A new membership (or other trigger event) happens in Cobot.
Zapier sends the relevant data from Cobot into the CRM of your choice.
Depending on how you define your workflow:
If the person is a lead, your CRM becomes home for their data.
If the person becomes a full member, Cobot retains the membership information.
If the membership ends, you can direct that data back into your CRM for follow-up or future leads.
IMPORTANT NOTE
The integration only works one way: from Cobot → CRM (via Zapier). Cobot cannot import or update data from the CRM via this integration.
Setting up the Integration
Here’s how to get started:
Register for a Zapier account
Within your Zapier account, connect Cobot by going to My Apps and searching for Cobot.
OR, connect through Cobot under Add-ons » Available Add-ons » Zapier. Check out this guide for more details.
From there, search for your CRM and get connected!
Creating Workflows
All of the setups will be done via your Zapier dashboard, and they provide simple step-by-step instructions. It really is that easy.
Create multiple Zaps for different use-cases (for example: when a member cancels, update their CRM record; when a new booking is made, create a note or lead). This gives you more value from the integration.
Some of the triggers Cobot supports include:
“Membership Confirmed”
“Membership Cancelled”
“Membership Plan Change Date Reached”
“Booking Created”
“External Booking Created”
PRO-TIPS
Make sure you’ve clearly defined what constitutes a “lead” vs a “member” in your process. Then map those accordingly in your CRM so you don’t get duplicate or conflicting records.
Regularly audit your Zaps: if you change a field in Cobot or your CRM schema, you’ll need to update the mapping.
Test thoroughly when first implementing: create a dummy member, trigger the event, check the CRM record created/updated.
Keep in mind that since the integration is one-way (Cobot → CRM) you will need a separate process if you want CRM → Cobot updates.
Use naming conventions in Zapier (e.g., “Cobot → CRM – Member Confirmed”) so you can easily manage and troubleshoot many Zaps.
Document your workflow: which Cobot triggers map to which CRM actions, and who owns maintenance.
Available CRM Integrations
Zapier supports hundreds of CRMs (and thousands of apps) that can integrate with Cobot via Zapier.
If your preferred CRM is not listed, you can request support from Zapier (or build a custom workflow using a webhook or API).