Automations and Integrations for Paid Communities
Zapier, n8n, Make, an MCP server for AI assistants and a REST API with signed webhooks: every one of them does what the dashboard does, within the permissions you grant, on every plan.
Zapier
An instant trigger for each of the 145 events, an action for every write and a search for every read, on a token you scope yourself
n8n
A verified community node: a trigger for each of the 145 events and an action for every REST endpoint, on Cloud and self-hosted
Make
A webhook listener for any of the 145 events and HTTP modules for every read and write, on the same token and spec as everything else
Claude and AI Agents
An MCP server with 161 tools for Claude, ChatGPT, Cursor and VS Code: sign in once, then work in plain language within your own permissions
REST API and Webhooks
A versioned REST API and 145 signed webhook events, behind tokens you scope yourself, on every plan
Two doors, every tool
Every automation and integration on Subscriby goes through the same two doors: a versioned REST API that does everything the dashboard does, and 145 signed webhook events that tell your systems what happened. Zapier, n8n, Make, the MCP server for AI assistants and your own code all stand on those two.
Pick the door that fits how you work. Zapier and Make for click-together automation; n8n for automation you host yourself; the MCP server when an assistant should do the chores in conversation; the API and webhooks when you are writing the code. A token carries only the abilities you tick, so each integration holds exactly the rights it needs and no more.
Each page states what the integration does, how to connect it and what it costs, then answers the questions creators and developers ask before wiring it in.
Which one do you need
Clicking, not coding
Zapier: an instant trigger for every event, an action for every write and a search for every read. Invite-only while the listing is reviewed.
Automation on your own server
n8n: a verified community node with a trigger node and an action node, on Cloud or self-hosted, with signature checks and idempotency built in.
Already on Make
Make: a custom webhook listener for any event and HTTP modules for every endpoint from the OpenAPI spec, with the signature check as a short module.
Letting an assistant do the chores
The MCP server: 161 tools for Claude, ChatGPT, Cursor and VS Code, within your own permissions, with a sign-in or a token.
Writing the code yourself
The REST API and webhooks: 30 resource families, tokens scoped by ability, idempotent writes and signed, retried deliveries.
Building an agent of your own
Start from the API and the OpenAPI spec with a narrow token, add the webhooks for what happened, and read the custom-agents guide for the retry, error and audit patterns.
Common Questions
Do integrations cost extra?
No. The API, the webhooks, the MCP server and the integrations built on them are on every plan, including Free. Zapier, n8n and Make bill you for their own plans as usual.
Which one should I start with?
If you already use Zapier or Make, start there. If you host your own tools, n8n. If you want to ask questions and delegate chores in conversation, the MCP server. If you are writing code, the API and webhooks, which is what all the others stand on.
Can an integration do more than I can?
No. Every integration signs in with a personal access token or an OAuth sign-in that carries only the abilities you grant, out of 107, and nothing reaches a project you cannot reach.
Are webhook deliveries reliable?
Each delivery is signed, logged and retried up to 8 times over about 4 days when your endpoint is down. Deliveries are not strictly ordered under retry, so act on the event data rather than the order of arrival.
Is the Zapier app public?
Not yet: it is invite-only while its public listing is reviewed. Ask the team for the invite link; the n8n node, the MCP server and the API need no invite.