Mateflow connects your community to other tools in three ways: connected apps (Slack, Discord, and Zapier), webhooks to your own server, and the Open API for developers. All three live on one admin page, Admin → Settings → Integrations.
Who can do this: Owners and admins. · Where: Web (admin console). · Plan: Webhooks, API access, and the daily API request limit depend on your platform plan.
Where to find integrations in the admin console
Go to Admin → Settings → Integrations. The page is called Integrations & API and has four tabs:
| Tab | What you do there |
|---|---|
| Integrations | Connect Slack, Discord, or Zapier under Connected Apps |
| Webhooks | Send community events to your own endpoint |
| API Access | Create and revoke API keys, and open the developer documentation |
| Delivery Logs | Check every request Mateflow sent to your webhooks, apps, and automation rules |
Connect Slack, Discord, or Zapier
Connected apps push community events, such as new members, posts, or payments, to another service:
- Slack: posts messages to a channel through an Incoming Webhook URL.
- Discord: posts messages to a channel through a Discord webhook URL. It only sends messages; it doesn't sync members or roles.
- Zapier: sends events to a Zapier Catch Hook, so a Zap can pass them on to thousands of other apps.
To connect one, open the Integrations tab and click Connect Slack, Connect Discord, or Connect Zapier. Paste the Webhook URL from that service, choose the Events to push, optionally add a Signing secret (optional), and click Connect. Then click Send test event to make sure messages arrive.
A connected card shows which events it's pushing. Use its menu to Edit settings, Send test event, or Disconnect.
Send events to your own server with webhooks
Webhooks send an HTTPS request to an endpoint you control whenever a chosen event happens, for example Member Joined, Member Added to Access Group, Post Created, or Payment Received. Each webhook has its own events, an optional signing secret, and an Active switch. Webhooks, and how many you can create, depend on your platform plan. See Set up webhooks.
Build your own integration with the Open API
The Open API lets a developer read and write your community's data from their own code: read posts, spaces, and members, create posts, upload media, and invite people. Each API key belongs to one community, and you choose its permissions (scopes) when you create it. API keys aren't managed in the creator dashboard (app.mateflow.com); its community Overview page links to this admin page instead.
Invitations sent through the API can include access groups, which the person gets when they accept. See How access groups work.
The full API reference is at mateflow.com/developers. On the API Access tab, click Open documentation to get there, and send the link to your developer; they don't need an account in your community. See Create an API key.
Check outgoing requests in Delivery Logs
The Delivery Logs tab lists outgoing requests sent by your webhooks, connected apps, and automation rules that use Trigger webhook. Filter by Event type, result, and date, and click Show Details to see the full request and response. Delivery logs are kept for 30 days. Failed webhook deliveries are retried automatically; there's no button to resend one yourself.
Requests made with your API keys aren't logged here. The API Access tab shows each key's Last Used date instead.
Related articles
Was this guide helpful?