A webhook sends an HTTPS request from Mateflow to a URL you control whenever something happens in your community, such as a new member joining or a payment arriving. Use webhooks to keep a CRM, email tool, or your own app in sync. You set them up under Admin → Settings → Integrations → Webhooks.
Who can do this: Owners and admins. · Where: Web (admin console). · Plan: Webhooks, and how many you can create, depend on your platform plan. If your plan stops including them, deliveries stop. Your webhooks are kept and start again when you upgrade.
Create a webhook endpoint
- Go to Admin → Settings → Integrations and open the Webhooks tab.
- Click Add Webhook.
- Enter a Name and an HTTPS Endpoint URL.
- Optionally generate a signing secret and copy it to your receiver. See signature verification below.
- Choose at least one explicit event subscription. Search events or select a category; Event docs opens the matching developer reference.
- Click Create Webhook. New webhooks are saved inactive.
- Save, send a sample test, then enable the webhook when the receiver is ready.
If the Add Webhook button shows an upgrade prompt, your plan doesn't include webhooks or you've reached your plan's webhook limit. See Check plan usage and limits.
Webhook events you can subscribe to
| Category | Events |
|---|---|
| Members | Member Joined, Member Left, Role Changed, Member Suspended (also sent for bans), Member Reinstated, Member Added to Access Group, Member Removed from Access Group |
| Content | Post Created, Comment Created, Post Deleted, Comment Deleted |
| Payments | Payment Received, Payment Failed, Subscription Created, Subscription Renewed, Subscription Canceled, Refund Issued |
Older webhooks may show events that are no longer available. You can remove them, but you can't add them again.
An older configuration with an empty event list means all events, not no events. Preserve it unchanged or choose explicit subscriptions. Unavailable events are retained when you edit other settings; changing subscriptions requires removing unsupported entries and choosing at least one current event. If the event catalog cannot load, retry before selecting or testing events.
How access group webhook events work
Member Added to Access Group and Member Removed from Access Group (access groups were previously called member tiers) fire when a member's groups actually change. Each event covers one member and one group, and includes the member's username and email, the group's name, and what caused the change: an admin, a subscription, an invitation, the default access group, or a deleted group.
- No access group event is sent before Member Joined, so a new member's default group at sign-up isn't announced, and neither are changes while a member waits for approval.
- Deleting an access group sends one removal event per member who held it. These, and events from setting a default group, can arrive a few minutes later.
- Removing a group that a subscription grants sends a removal and then an addition, because the subscription adds it back right away. See Add or remove a member's access group.
How the Member Left webhook event works
Member Left is sent once when someone stops being a member of your community, so you can remove them from your CRM or mailing list. It fires when:
- an admin uses Remove from community or Anonymize member;
- the member deletes their account. A scheduled deletion counts when the 30-day cooldown ends, not when they ask; if they cancel it, nothing is sent;
- your data retention policy erases an inactive member. This runs nightly, so many events can arrive at once.
Each event includes the member's username and email from before they left, even if their account was anonymized, so you can find them in your own system. It also says how they left and, when an admin removed or anonymized them, which admin. If the admin wrote an Internal note (optional) when removing the member, the note is included too.
Member Left isn't sent when a member deactivates their account, is suspended or banned (that's Member Suspended), leaves a space, or never finished joining. The access groups a leaving member held don't send Member Removed from Access Group.
Connected apps whose card shows Pushing all events start sending Member Left as well, including to Slack or Discord channels. To leave it out, choose Edit settings and pick the events to push. See Integrations overview: API, webhooks, and Zapier.
Verify webhook signatures with the signing secret
When a webhook has a secret, Mateflow signs each request with HMAC-SHA256 so your server can check that it came from Mateflow and wasn't changed (signature verification). Each request carries two headers:
X-Mateflow-Timestamp: when the request was sent, in Unix seconds.X-Mateflow-Signature:sha256=followed by the hex-encoded signature.
To verify a request on your server:
- Read the raw request body exactly as received, before parsing the JSON.
- Build the signed string: the
X-Mateflow-Timestampvalue, a period (.), then the raw body. - Compute an HMAC-SHA256 of that string, keyed with your secret, and hex-encode it.
- Compare it with the part of
X-Mateflow-Signatureaftersha256=, using a constant-time comparison. Reject the request if they differ. - Optionally, reject requests with a timestamp more than a few minutes old, to block replays.
Requests from an automation rule's Trigger webhook action are signed the same way when the rule has a secret. See Automate tasks with rules.
After you save, the secret is hidden. To keep it, leave the field blank when you edit the webhook. To rotate it, generate a new one and update your server at the same time.
Test, pause, edit, or delete a webhook
Save changes before testing or opening delivery logs. In the webhook's actions, open its test dialog, choose a subscribed event currently supported for sample testing, and click Send test. The sample is marked test=true and goes to the saved URL, including while the webhook is inactive. Your receiver must recognize test data. A 2xx response confirms HTTP receipt only, not completion of your own business process. Check the status, response, and delivery logs.
Enable the webhook after testing; disable it to pause live deliveries. Editing an enabled webhook takes effect immediately when saved. Delete removes the webhook and its delivery logs permanently. If settings change after a test, its old result expires: test the saved configuration again.
Check webhook deliveries and retries
Open the Delivery Logs tab to see each request, its HTTP Status, Duration, and Source. To see one webhook's deliveries, use Filter by webhook. Click Show Details for the full Request Payload and Response Body. Delivery logs are kept for 30 days.
When a delivery fails, Mateflow retries it automatically after 1 minute, 10 minutes, 1 hour, and 6 hours. HTTP 429 and 408 responses are retried too; other 4xx responses aren't. When retries run out, or on a 4xx that isn't retried, the owner and admins get an email, at most once a day for each webhook.
To send a delivery again yourself, click Resend in its row. It sends the same body, signed again, to the webhook's current URL. Refresh to see the result as a new row. A webhook that's deleted or turned off can't resend. Each attempt gets its own row. An automatic retry gets a new Delivery ID, Resend keeps the original one, and the Event ID stays the same, so rows that share an Event ID are attempts at one event. Deliveries can arrive more than once or out of order, so have your server de-duplicate on the event ID. For payload fields and code samples, click Open documentation on the Webhook developer reference card in the Webhooks tab, or go to mateflow.com/developers/webhooks. You can send that link to your developer.
Delivery filters include event, result, webhook, date range, Source, and Platform. Delivery metrics follow the selected scope and window, and count HTTP attempts including tests, retries, and manual resends; they are not unique business events. The page shows available history and retention. Configuration totals are a separate snapshot of registered webhooks, including enabled, inactive, and enabled webhooks with recent failures.
Related articles
Was this guide helpful?