Webhooks
Webhooks are how AcquisitionSuite talks to other systems. It can send them from automation rules (Pro), and receive them from your payment gateways.
Sending: the Send Webhook action
In an automation rule, add the Send Webhook action and enter a Webhook URL. When the rule fires, AcquisitionSuite makes a POST request to that URL with a JSON body. Use it to reach Zapier, Make, n8n, a CRM, a Slack workflow or any tool with an incoming webhook.
What the request contains
The body is JSON with the details of the event that fired the rule (lead fields such as name and email, and related data such as the file or order where relevant), plus:
| Key | Meaning |
|---|---|
lead_id |
The lead’s ID in AcquisitionSuite |
site_url |
Your site’s address |
timestamp |
When it was sent, in ISO 8601 (UTC) |
The request is sent in the background with a short timeout and does not wait for a reply, so a slow receiver never slows your site down.
Setting it up in Zapier or Make
- Create a new Zap or scenario with a Webhook trigger (Catch Hook).
- Copy the webhook address it gives you.
- Paste it into the rule’s Webhook URL and save the rule.
- Submit a test form so the receiver can capture a sample, then map the fields.
Receiving: payment gateway webhooks
Stripe, Paystack and Flutterwave confirm payments by calling your site. Each gateway has its own address, for example https://yoursite.com/?acquis_pay_webhook=1&gateway=stripe, shown on its tab in Payment Settings. Register it in the gateway’s dashboard. See Payment webhooks and the activity log.
Security notes
- Use HTTPS webhook URLs only.
- Treat the receiving URL as a secret; anyone who knows it could post to it.
- The plugin validates that the URL is well-formed and refuses anything that is not.