OnSync Zapier integrationAutomate OnSync with Zapier.
The OnSync Zapier integration gives you 1 trigger, 2 actions and 0 searches. You can react to new contacts, add contacts from other tools and send WhatsApp messages through OnSync. Here is what each one does, what it costs and what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the OnSync Zapier integration actually does
OnSync is a CRM, a shared place where business teams manage customer conversations, contacts and sales follow-up. Connected to Zapier, it can start a Zap when a contact arrives, receive contacts from other tools, and send WhatsApp messages without anyone typing them.
Three outcomes cover most uses. A contact base fed by your forms: a form or a booking tool starts the Zap and Create Contact adds the person to OnSync, so sales stop retyping leads. A WhatsApp message on cue: Send Message writes to a phone number through OnSync, for a confirmation, a reminder or a welcome. Your contacts copied elsewhere: New Contact passes each new OnSync contact to a spreadsheet, a mailing tool or an accounting app.
Now what the app page leaves out. There is no search for OnSync on Zapier: a Zap cannot check whether a contact already exists before creating it, so the same person can land twice. There is no action to update or delete a contact either; the integration only creates. And both actions need a phone number: a source that does not carry one cannot feed them.
The trigger is also a polling trigger, so a new contact does not move instantly. If you are still weighing tools, start with the Zapier review.
Zapier vocabulary in one minute
Eight words come back throughout this page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. OnSync has one: a new contact.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, such as creating an OnSync contact.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps what it has not seen before.
- Instant trigger
- A trigger the app reports itself, calling Zapier the moment the event happens. OnSync has none on Zapier.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
What an OnSync Zap really costs
The New Contact trigger never costs a task, however often Zapier checks OnSync. What you pay for is each action that succeeds: one contact created, one task; one WhatsApp message sent, one task.
- New Contact trigger0 task
- Create Contact, Send Message1 task each when it succeeds
- Free plan100 tasks a month, 2-step Zaps
- Premium appNo, OnSync runs on the free plan
A Zap that creates a contact and then messages it uses two tasks per person. A message that fails is not counted. OnSync is not a premium app, so the free plan works: 100 tasks a month, unlimited Zaps, two steps per Zap, and a check every 15 minutes for New Contact. That last point matters: on the free plan, a welcome message can leave up to 15 minutes after the contact appears. A filter or a second action makes the Zap multi-step, which needs a paid plan.
Connect OnSync to Zapier in 3 steps
- 01
Open your connections
In your Zapier account, open the Apps page and click + Add connection. A connection is your OnSync account linked to Zapier once, then reused by every Zap that uses OnSync.
- 02
Find OnSync
Type OnSync in the search box of the dialog, pick it, then click Add connection. You need an existing OnSync account here, so have the login of the right workspace ready.
- 03
Sign in and grant access
Sign in to OnSync in the tab that opens and grant Zapier access. Pick an account that can read and create contacts, including contacts other people on the team own.
Your first OnSync Zap
GoalLog every new OnSync contact in a spreadsheet, then greet it on WhatsApp through OnSync.
- 01
Pick the trigger
Start a new Zap, choose OnSync as the app and New Contact as the event, then select the OnSync connection from the previous section.
- 02
Test on a real contact
Run the test. Zapier brings back the three most recent contacts of the connected account, so the next steps are mapped on a real person, not a placeholder.
- 03
Add the spreadsheet row
Add the spreadsheet app as the first action and map what OnSync sent into the columns. Test this step and check the new row before going on.
- 04
Add the WhatsApp message
Add OnSync again with Send Message. Map the contact's number into Phone Number, country code included. Two actions make this a multi-step Zap, so it needs a paid plan.
- 05
Test, then publish
Test the message on your own number first and read what came back. When it looks right, publish the Zap. Each new contact then costs two tasks.
The OnSync trigger
1 event starts a Zap when something happens in OnSync. Zapier checks for them at the interval your plan allows.
New Contact
Polling triggerIn Zapier“Triggers when there's a new contact.”
Starts your Zap whenever a new contact shows up in your OnSync account, and hands that contact to the steps that follow. It is the way to let the rest of your tools know someone new has entered the CRM.
The 2 OnSync actions
OnSync gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Contact
ActionIn Zapier“Creates a new contact in your account.”
Adds a new contact to your OnSync account from whatever started the Zap: a form, a booking, a payment.
Send Message
ActionIn Zapier“Send a message to a whatsapp number through OnSync”
Sends a WhatsApp message to a phone number through OnSync, with the text you compose from earlier steps.
When an OnSync Zap breaks
Zapier attaches no help article to OnSync, so no app-specific error is on record. What breaks here comes from the required fields and from the limits every Zap shares.
Most of these do not show up on day one. They appear as a contact created twice, a message that never left, or a task count draining faster than planned. When one hits, the Zapier troubleshooting page is the next stop.
A phone number without its country code
Send Message needs the recipient's number with the country code. A source that stores local numbers only will make the step fail on every run.The contact loop
New Contact plus Create Contact in OnSync is a Zap writing where its own trigger watches. Each contact creates a new one, which starts the Zap again and burns tasks.Duplicates on the way in
There is no OnSync search on Zapier, so Create Contact cannot check first. If the same person fills your form twice, OnSync gets two contacts.Old contacts are never picked up
A Zap only reacts to what happens after it is switched on. Contacts already in OnSync when you publish will not start it; moving them is a separate job.A bulk import gets held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the runs back instead of firing them all.The same contact twice? Not from the trigger
Zapier keeps track of what it has already seen on a polling trigger, so one OnSync contact does not start the Zap twice. Duplicates come from the source.
Need help automating OnSync with Zapier?
A person reads every message.
