Paystack with Make
In Make: create a scenario → add a Webhooks module as trigger → copy the webhook URL → add it to Paystack webhook settings. Add action modules: Google Sheets (add row), Mailchimp (add subscriber), Airtable (create record), or HTTP (call your own API). Map Paystack webhook fields (event.data.reference, event.data.amount, etc.) to your destination app fields.
Setting Up a Paystack Webhook Trigger in Make
- Create a new scenario in Make (make.com).
- Add a Webhooks → Custom Webhook module as the trigger.
- Click Add to create a new webhook. Copy the generated URL.
- Go to your Paystack dashboard → Settings → API Keys & Webhooks.
- Paste the Make webhook URL in the Webhook URL field. Save.
- Back in Make, click Re-determine data structure. Trigger a test payment in Paystack test mode. Make will capture the webhook and show you the payload fields.
Add a Router module after the webhook to branch based on event type: one branch for charge.success, another for charge.failed.
Common Paystack + Make Scenarios
| Trigger | Action | Use Case |
|---|---|---|
| charge.success | Google Sheets: Add Row | Sales log / daily reconciliation |
| charge.success | Mailchimp: Add Subscriber | Add buyer to email list |
| charge.success | Airtable: Create Record | Order tracking database |
| charge.success | Gmail/SendGrid: Send Email | Custom receipt with branding |
| charge.failed | Slack: Send Message | Alert operations team |
| transfer.success | HTTP: POST to your API | Mark vendor payout as confirmed |
In each action module, map fields from the webhook payload. For amount, use the Make formula {{round(webhook.data.amount / 100, 2)}} to convert from minor unit to major unit.
Learn More
See Paystack with Zapier for the Zapier equivalent automation guide.
Key Takeaways
- ✓Make's generic Webhook module receives Paystack webhook events — no Paystack-specific module needed.
- ✓Filter on event.event === "charge.success" inside Make to only trigger on successful payments.
- ✓Map event.data.amount (in minor units) and divide by 100 in a Make formula for the major unit.
- ✓Make runs 1,000 operations/month free — enough for small volumes; paid plans for higher volume.
- ✓Common automations: payment → add to Mailchimp, payment → Airtable row, failed payment → Slack alert.
Frequently Asked Questions
- Does Make have a native Paystack app?
- As of 2026, Make does not have a dedicated Paystack app. Use the generic Webhooks module as the trigger to receive Paystack events, and the HTTP module to make Paystack API calls as actions. This gives you full flexibility to work with any Paystack endpoint.
- How do I filter to only run my Make scenario on successful payments?
- After the webhook trigger, add a Filter module (the small circle between modules). Set the condition: data.event = "charge.success". Make will only continue to the next module when this condition is true. You can also use a Router to handle multiple event types in separate branches.
- Can Make handle Paystack webhook signature validation?
- Make's Custom Webhook module does not natively validate HMAC signatures. For production, add an HTTP module as a second step that calls your own server endpoint to validate the signature before processing. Alternatively, accept that Make automations are low-risk for read-only operations like logging, but always validate before triggering fulfillment actions.
Ready to build real-world apps?
Join the McTaba Labs full-stack marathon (4 months full-time · 6 months part-time). Learn M-Pesa, USSD, and WhatsApp engineering while shipping 8 production apps.
Apply to the McTaba Marathon