There is no QuickGrow app in the Zapier directory, and this page is not going to pretend otherwise. What QuickGrow does have is a signed webhook for every message you send through the API, a step in the journey builder that calls any URL you give it, and a REST API a Zap can call back into. Point them at a Catch Hook and a Webhooks by Zapier action, and you have a two-way connection you built in an afternoon.
Most integration pages open by telling you how easy everything is. This one opens with the part you would otherwise find out an hour in.
Search Zapier for QuickGrow and you will find nothing. There is no authorise screen, no ready-made trigger list, no pre-built actions. The Zapier tile inside Settings → Integrations stores an API key and then does nothing with it — it is unfinished, and switching it on will not start a Zap.
⚠ If a page ever told you otherwise, it was wrong. This is the correction.
Signed webhooks for four message events, with retries and a delivery record for each attempt. A webhook step you can drop into any journey, pointed at any URL. A REST API that sends messages and manages contacts. Zapier's own Catch Hook and Webhooks actions bolt onto all three without a directory listing in sight.
Every one of these ends the same way: a POST at a Catch Hook URL you paste in. They differ in what sets them off and how soon Zapier hears about it.
Add your Catch Hook URL in Settings → Developer, tick the events you want, and QuickGrow posts to it when a message goes out, is delivered, fails, or bounces. Each delivery is signed with a secret only you and QuickGrow hold, so your Zap can tell a real event from a stray request.
The journey builder has a Webhook action alongside send, wait, tag and branch. Give it a Catch Hook URL, pick the method, and add your own headers and body. When a contact reaches that step, Zapier gets the call — mid-journey, exactly where you placed it.
Webhooks only cover the messages you sent through the API. If you want campaign and journey sends too, give a Zap a schedule and a Webhooks by Zapier GET on the messages or contacts list, filtered to everything created since the last run.
{
"id": "evt_7c1e...",
"event": "message.delivered",
"createdAt": "2026-08-26T11:04:18Z",
"data": {
"message": {
"id": "msg_9fA2",
"channel": "whatsapp",
"status": "delivered",
"to": "+8801700000000",
"tags": ["order-update"],
"metadata": { "orderId": "INV-1042" },
"sentAt": "2026-08-26T11:04:11Z",
"deliveredAt": "2026-08-26T11:04:17Z",
"failureReason": null
}
}
}
# the fields under "metadata" are the ones you sent — your own order id
# comes straight back out, so the Zap knows which order it is looking atYou are pasting a URL into one form and a key into another. Nothing here waits on a review, a listing, or anyone at our end.
In Zapier, pick Webhooks by Zapier as the trigger and choose Catch Hook. Zapier gives you a URL and then sits waiting for a first payload so it can learn the field names.
Settings → Developer → Webhooks. Name it, paste the Catch Hook URL, and tick the events you care about. The signing secret is shown once, at that moment — copy it before you close the panel.
The Test button fires a sample straight at your Catch Hook and shows you the status code and the reply that came back. Zapier picks the sample up and your fields are ready to map — no waiting for a real message to happen along.
Give the Zap something to do — a row in a sheet, a message in a channel, or a Webhooks by Zapier POST back into QuickGrow. Turn it on. From then on it runs on its own.
A Webhooks by Zapier action and one API key turn any Zap into a sender. The same reference the API is documented in tells you the exact shape of every call.
Authenticate with a single X-API-Key header and call the endpoint you need. The reference lives inside the product, so the shape you read is the shape that is running.
# Tell the customer their order is ready curl https://server.quickgrow.ai/api/v1/messages \ -H "X-API-Key: mk_..." \ -H "Content-Type: application/json" \ -d '{ "channel": "whatsapp", "to": "+8801700000000", "templateId": "tpl_order_ready", "variables": { "orderId": "INV-1042" }, "tags": ["order-update"], "metadata": { "orderId": "INV-1042" } }' # Put a tag on the contact instead # PATCH /api/v1/contacts/:id {"tags": ["vip", "repeat-buyer"]}
Most people end up with two of these running side by side — webhooks for the sends they make themselves, and a scheduled read to catch everything else.
| Message webhooks | Journey webhook step | Scheduled read | |
|---|---|---|---|
| What starts it | A message you sent through the API goes out, is delivered, fails or bounces | A contact reaches the webhook step you placed in a journey | Zapier's own timer — every fifteen minutes, hourly, or daily |
| How soon Zapier hears | Straight away, and again on a retry if your Zap was down | While the journey is running | On the interval you picked |
| Where you set it up | Settings → Developer, in QuickGrow | The journey builder, in QuickGrow | The trigger step, in Zapier |
| What proves it came from you | A secret only you and QuickGrow hold, sent with every delivery | Whatever headers you choose to put on the step | Your Zap made the call, so there is nothing to prove |
| Needs an API key | No — an endpoint and its secret | No | Yes, one scoped to reading |
No. You will not find QuickGrow when you search for an app inside Zapier, and there is no one-click authorise screen. Everything on this page is built with Zapier’s own Webhooks by Zapier trigger and action, which are the general-purpose pieces every Zapier plan includes for exactly this situation.
Not what you would hope. That tile asks for an API key and stores it, but nothing in QuickGrow reads it or sends anything anywhere as a result. It is unfinished, and connecting it will not start a Zap. Use the webhook route on this page instead — that one is wired all the way through.
Anything the REST API covers, with a Webhooks by Zapier action and an API key. Send an email, SMS or WhatsApp message; create a contact or update one; put tags on a contact; read a contact or a message back; pull delivery statistics. Give the key only the access that Zap needs and nothing more.
No. Journeys are started from inside the portal or by a date on a contact record, and the endpoint that fires tag and contact events is not reachable with an API key. So a Zap can add a tag to a contact, but the tag will not set a journey running. The dependable automatic trigger is the date-based one: put a date on a contact and QuickGrow acts on it a set number of days before or after, on its own.
For the outbound half, no — a Catch Hook URL pasted into a form and a Test button. For the half that sends messages back you are filling in a Zapier action with a URL, a header and a small block of JSON; if that is unfamiliar territory, half an hour with whoever looks after your site will settle it for good.
Email will. SMS and WhatsApp are checked against consent, a quiet-hours window and a per-contact limit before they go — in Bangladesh the window runs from nine at night to eight in the morning, and it applies to codes and confirmations too. Build your Zap so a blocked send is handled rather than assumed.
An API key, a Catch Hook URL and a Test button. Email, SMS and WhatsApp all sit in the same account, on one bill.
CyberCraft BangladeshQuickGrow AIRun every channel from one platform. Bring your own SMTP, SMS gateway, and WhatsApp number — or use ours.
See pricing →