Catch QuickGrow activity
Point a QuickGrow webhook at a Make custom webhook URL and receive message, delivery, failure and automation events as they happen.
Make.com
QuickGrow events, ready for your Make scenarios.
There is no directory app to install. QuickGrow sends signed webhook events to Make, and Make can call the QuickGrow API back when a scenario needs to update contacts, tags or messages.
Works with Make custom webhooksSigned QuickGrow deliveriesScoped API write-back
01What connects
Webhook in, API back out.
The dependable Make setup is explicit: QuickGrow pushes events into a custom webhook, and Make uses HTTP modules only for the actions you choose.
Branch and enrich in Make
Use Make filters, routers and data stores to fan events into sheets, CRMs, finance tools and internal alerts without waiting for a native app.
Write back with scoped keys
When a scenario needs to act inside QuickGrow, call the REST API with a narrowly scoped key for contacts, tags, messages or reports.
02Setup
Four steps from blank scenario to live automation.
You can test the payload before going live, keep the signing secret private, and rotate keys without rebuilding the scenario.
Create a custom webhook in Make
Start the scenario with Webhooks -> Custom webhook. Make gives you a URL that waits for the first QuickGrow sample.
Register that URL in QuickGrow
Open Settings -> Developer -> Webhooks, paste the Make URL, choose the events to send, and keep the signing secret for verification.
Press Test and map the payload
The test delivery teaches Make the field names, so later modules can route by channel, status, campaign, contact or error code.
Add API actions only where needed
Use an HTTP module with a scoped QuickGrow API key when the scenario should create a contact, add a tag or send a follow-up message.
Send QuickGrow into the rest of your stack.
Use Make when the workflow belongs between tools: route replies to ops, push failed sends to support, enrich contacts, or update a spreadsheet the moment a campaign result lands.