Zappio integrations: what connects today, and what connects through the API

Connect it today

Three things connect from inside Zappio with no code, on Standard and above. Standard is ₹4,000/month on a yearly term, or ₹5,000/month billed quarterly, plus 18% GST.

WooCommerce is not on that list. It connects through our Engage module, which we grant rather than you switching on, and it is covered further down.

SMS and TikTok connect screens exist in the app but are not part of the WhatsApp plans, so ask us before building a process on one.

If you are still working out what to automate before you work out what to connect, start at WhatsApp automation.

Shopify: order alerts, cancellations and abandoned carts

Shopify has the fullest connect flow of the three. We connect your store with you, then you choose which events send a WhatsApp message and which approved template each one uses.

• Order, shipping and cancellation alerts. Once you switch them on, the customer hears from you when the order is placed, when it ships, and if it is cancelled.
• A checkout reminder. A checkout left open gets one reminder with its recovery link, after a delay you set.

More on Shopify with WhatsApp and email.

The connector runs one way. Shopify tells Zappio what happened; nothing a bot collects is written back into the store. It does not run Shopify checkout inside WhatsApp, and it is not a catalogue sync.

What those messages cost is Meta's charge, which you pay to Meta directly; Zappio adds nothing. Utility messages are ₹0.115 in India and marketing messages ₹0.8631, a difference of 7.5 times, so a Bengaluru boutique sending 8,000 marketing and 1,500 utility messages a month pays ₹7,077.30 to Meta. The full rate card is on our WhatsApp API pricing page.

Google Sheets: one direction, and it is the useful one

For plenty of small businesses the CRM is still a spreadsheet, and Google Sheets connects for that reason. A bot node writes a row as the conversation ends: the name, the number, what they asked about. The sheet the office already opens every morning fills itself.

Be clear about the direction, because only one of them exists. Zappio writes into your sheet. It does not read your rows. We ask for access to the single file you pick, look at row 1 to populate the column picker, and append rows below it. Nothing else.

So a sheet can never feed a broadcast list. That list is built inside Zappio from your own contacts. If you need the reverse, that is webhook work into our API rather than a setting. Tell us and we will scope it.

WooCommerce: through the Engage module

WordPress stores connect through Engage, which is a module rather than a switch on the integrations screen. Engage registers webhooks on your store for orders and customers, verifies the signature on each one, and runs a history sync so past orders arrive too. Customers, orders and products then sit inside Zappio next to the conversation.

Two things to know before you plan around it. Engage is included on Premium and an add-on on Standard, and it is not available on Compact, so check plans and pricing against the plan you are on. And we grant it: there is no toggle for you to find until we switch it on for your workspace. Ask us and we will price it against your plan.

It runs inbound, the same way Shopify does. Nothing a bot collects is written back into WooCommerce; write-back is REST API and webhook work.

What a webhook is, and what the API lets your software do

A webhook, in plain English. Picture two systems that need to tell each other things. The slow way is your software asking Zappio every minute whether anything happened. A webhook reverses that. You give Zappio a web address, Zappio calls it the moment something happens, and the details arrive with the call.

Four events are available. A customer sent you a message. An agent or the API sent one. A delivery status changed to delivered, read or failed. A bot flow finished for a contact. You pick the ones you want, and a Send test button fires a real payload at your address before anyone writes a line of code. Every call is signed, so your side can prove it came from us.

The REST API runs the other way, so your own software can send: free-form text inside the 24-hour customer service window, an approved template outside it, and a bot or a queued trigger on demand. Keys are scoped and revocable. The endpoints, the signature scheme and the rate limits are on our developer docs.

What data flows which way

Integrations go wrong when nobody writes down the direction, so here is the whole of it.

What does not happen matters as much. A broadcast list is never read out of a spreadsheet. Nothing a bot collects is written into Shopify or WooCommerce. Nothing appears in Salesforce, Zoho CRM or HubSpot unless somebody catches our webhook and puts it there. A booking taken in chat lives in Zappio, not in your Google Calendar, until that wiring exists.

Everything else, through the API

Salesforce, HubSpot, Zapier, Zoho CRM, Intercom, Mailchimp, Notion, Twilio, Google Calendar, Freshdesk, Pipedrive and Make are not one-click connectors on Zappio today. They all connect the same way instead, through our REST API and webhooks. If the tool can call a web address when something happens, it can ask Zappio to send a message. If it can be told an address to call, it hears about every message and every delivery.

So tell us what you run. We will say whether it is an hour, a day, or not worth doing. Small wiring we do with you during onboarding; larger work we scope and quote first.

Four things make that conversation short.

• The tool's name, and whether your plan on it includes API access. Many products hold that back on the cheapest tier.
• The event that should send a message, in your own words. When the invoice is marked paid is enough.
• The message itself. Meta approves every template, and the category it lands in sets what it costs.
• Who holds the keys, and who we should call when something stops working.

Questions people ask