Which integration fits
Salesforce and ChabadOne write into your CRM's own records. Zapier, Make and a custom webhook send Ovante's events to any tool you point them at.
ProOwner
Pick Salesforce or ChabadOne CRM when you want people, attendance and money to land in your CRM's own records. Pick Zapier, Make or a custom webhook when you want Ovante's events sent to some other tool: a mailing list, a spreadsheet, a chat channel or your own code. All five are cards under Settings → Integrations.
Side by side
| Salesforce | ChabadOne CRM | Zapier, Make, custom webhook | |
|---|---|---|---|
| What it does | Writes Contacts or Leads, Campaigns and Tasks in your Salesforce org | Writes ChabadOne's own records on the Salesforce org that runs it | Posts a signed message to a URL each time an event you picked happens |
| How you connect | Sign in to Salesforce | Sign in to the Salesforce org that runs ChabadOne | Paste a URL |
| Who a person is | Your matching rules find the existing record, or Ovante creates one | Every new person arrives as a Web contact, and ChabadOne's merge rules decide who it is | The receiving tool decides |
| What you set | Matching, field mapping, Campaigns, Tasks | Three switches | Which events to send, and what to leave out |
| How many | One per org | One per org | As many as you want |
What each one hears
- Salesforce hears registrations, check-ins and Not going for its Campaigns, the contact changes registrations cause, and, when you switch them on, donations and purchases as Tasks.
- ChabadOne CRM hears registrations and check-ins for its Event campaigns, and ticket purchases and donations as Income.
- Zapier, Make and a custom webhook hear exactly the events you tick when you create the connection. See Webhook events.
The same for all five
- Only the org's owner sees and manages integrations.
- Connecting one needs Pro. On Free, a connection you already made keeps running, but you can't connect or reconnect one.
- Only changes that come from a registration go out. Your own edits and merges on the People page stay in Ovante. See What Ovante sends, and what stays.
- Every connection has a log of what Ovante sent, or decided not to send, and why.
- Ovante has no public API. Webhooks are how your data leaves Ovante for a system of your own.
- When
- You edit, merge or import contacts
- Then
- Nothing goes to your CRM or webhooks. Only contact changes that a registration makes are sent.
- When
- A request is waiting
- Then
- Your contacts, CRMs and webhooks hear nothing about it. When you approve it, they get it as a new registration and a completed order.
Was this helpful?
Related
Connect SalesforceSign in to Salesforce from Settings, Integrations. Ovante then acts as that Salesforce user, with exactly that user's access.Connect ChabadOneSign in to the Salesforce org that runs ChabadOne. Attendance, ticket purchases and donations start landing in ChabadOne's own records, with all three switches on.Connect Zapier or MakePaste the webhook URL from your Zap or Make scenario, tick the events to send, and click Send test so Zapier or Make has sample fields to map.What Ovante sends, and what staysRegistrations, check-ins, orders, refunds, gifts and the contact changes they cause go out. Your own edits, merges and imports stay in Ovante, and so do requests until you approve them.