n8n-nodes-subscriby

Verified community node for n8n that drives Subscriby — subscription + access-code monetisation for Telegram communities.

Provides two nodes:

• Subscriby Trigger — starts a workflow when a Subscriby event fires. Covers subscriptions, payments, members, access codes, coupons, plans, projects, project resources, payment methods, connector installations and outages, billing, groups, roles, teams, team members, member support conversations, saved replies and inbox settings, message broadcasts, and the Disaster Recovery ledger (165 events total). Uses the /v1/webhook-subscriptions lifecycle and validates the SB-Signature HMAC on every request.
• Subscriby — action node for every documented route on api.subscriby.net. Covers 31 resources across creator-facing surfaces (projects, plans, pass windows, subscriptions, subscribers, members, broadcasts, support conversations, canned replies, support inbox settings, coupons, the Referral Program, the Partner Program, creator tasks, the notification centre, the Disaster Recovery ledger, the Connector Directory and a project's installations, access codes, resources, payment methods), admin surfaces (teams, team members, roles, groups, tokens, webhook endpoints, webhook deliveries, activity log), and read-only data surfaces (analytics, distribution links).

Installation

Community install (recommended)

Inside n8n:

1. Settings → Community Nodes → Install
2. Enter n8n-nodes-subscriby
3. Confirm and restart n8n

Manual install (self-hosted)

cd ~/.n8n/custom
npm install n8n-nodes-subscriby

Restart the n8n process after install.

Setup

1. Mint an API token at https://app.subscriby.net/settings/tokens. Every token is auto-bound to a team (scope:team:<uuid>); you pick the abilities it carries. See the ability catalogue for the full list. Minimums per use-case:
   • Trigger node — webhook-endpoint:manage. Restrict to a single project by also scoping the token to that project (scope:project:<uuid>).
   • Read-only workflows — combine *:view / *:view-any abilities for the resources you list or fetch (e.g. project:view-any, project-subscription:view, project-subscription-plan:view, project-access-code:view-any, team-member:view-any, role:view, group:view, project-recovery:view-any, activity:read, dashboard:read, distribution:read, billing:read).
   • Write workflows — add the matching *:create / *:update / *:delete abilities (e.g. project:create, project-subscription-plan:update, project-access-code:create, project-resource:delete). Cancelling a subscription is project-subscription:update; banning/kicking a member is project-user:update.
2. In n8n, Credentials → New → Subscriby API and paste the sbt_... token. Leave the base URL at the default unless you are self-hosting.
3. Add a Subscriby Trigger node, pick one or more events, optionally scope to a single project, and activate the workflow. On activation n8n registers the endpoint with Subscriby. Deactivating the workflow deletes the endpoint.

Supported events (165)

The full catalogue is defined in nodes/SubscribyTrigger/events.ts and mirrors the event reference. This table is generated from that file by npm run sync:readme — do not edit it by hand.

Supported actions

Every mutation automatically sends a fresh Idempotency-Key header so node re-runs never double-fire.

Development

npm install
npm run build    # compile TS + copy icons
npm run dev      # watch mode
npm run lint

To test against a local n8n:

npm link
cd ~/.n8n/custom
npm link n8n-nodes-subscriby
n8n start

Links

• Subscriby documentation
• n8n integration guide
• API reference
• Event reference

License

MIT