Zapier

The Subscriby Zapier app exposes 106 instant triggers, 45 write actions, and 45 searches — full parity with the live api.subscriby.net/v1 surface plus the complete WebhookEvent catalog.

Install

The Subscriby Zapier integration is currently invite-only and is not yet publicly listed in the Zapier App Directory. To request access, contact the Subscriby team. Once you receive an invite link, click it to connect your account. During the OAuth-less connection step Zapier asks for an API token — mint one at app.subscriby.net/settings/tokens with the abilities listed per trigger / action below.

Triggers — 106 webhook events

Grouped by family. Every trigger uses the REST Hook pattern: on Zap activation Zapier calls POST /v1/webhook-subscriptions, on deactivation it calls the matching DELETE. All triggers additionally implement a polling fallback (performList) against /v1/webhook-events so the Zap editor can show a sample even before any live event has fired.

Every trigger additionally requires webhook-endpoint:manage on the token so Zapier can create and delete the underlying webhook endpoints.

How triggers work

POST https://api.subscriby.net/v1/webhook-subscriptions
Authorization: Bearer sbt_live_<id>_<secret>
Idempotency-Key: <zap-scoped-uuid>
Content-Type: application/json

{
  "name": "Zapier — New Subscription",
  "url": "<zapier-inbound-url>",
  "events": ["subscription.created"]
}

Actions — 45

All writes auto-inject a fresh Idempotency-Key header per call — retries are safe.

Project (5)

• create_project — POST /v1/projects
• update_project — PATCH /v1/projects/{project}
• archive_project — POST /v1/projects/{project}/archive
• restore_project — POST /v1/projects/{project}/restore
• delete_project — DELETE /v1/projects/{project}

Plan (5)

• create_plan — POST /v1/projects/{project}/plans
• update_plan — PATCH /v1/projects/{project}/plans/{plan}
• publish_plan — POST /v1/projects/{project}/plans/{plan}/publish
• unpublish_plan — POST /v1/projects/{project}/plans/{plan}/unpublish
• delete_plan — DELETE /v1/projects/{project}/plans/{plan}

Plan Kind — a breaking change in 3.0.0

Create Plan and Update Plan now open with a Plan Kind dropdown, and the fields below it change to match:

Only the fields your chosen kind accepts are shown, mirroring the API, which refuses a block belonging to another kind rather than ignoring it.

Building a Pass Series

A series points at windows that already exist on your pass plans, so the order matters:

1. Find Pass Windows — the new search. Returns each window's ID, its local range, whether it is still on sale and how many people hold it. Filter by plan, status or date range.
2. Create Plan with Plan Kind → Pass Series, pasting those IDs into Pass Window IDs.
3. Optionally add Automatic Inclusion Rules. A rule describes windows rather than naming them and keeps matching after the save: a window scheduled later is added to the slate and granted to everyone already holding the series, at no charge. Handpicked IDs never grow on their own — the two compose.

Resource IDs is optional on a series and means a lounge the holder keeps for the whole span; each window already grants its own plan's resources.

Subscription + Member (4)

• cancel_subscription — POST /v1/subscriptions/{subscription}/cancel
• ban_member — POST /v1/projects/{project}/members/{member}/ban
• unban_member — POST /v1/projects/{project}/members/{member}/unban
• kick_member — POST /v1/projects/{project}/members/{member}/kick

Support conversation (3)

• reply_support_conversation — POST /v1/support/conversations/{conversation}/messages (set Private Note to record a private team note instead of messaging the member)
• resolve_support_conversation — POST /v1/support/conversations/{conversation}/resolve
• assign_support_conversation — POST /v1/support/conversations/{conversation}/assign (leave the assignee empty to clear an assignment)

Resource + Access code (5)

• create_resource — POST /v1/projects/{project}/resources
• unlink_resource — POST /v1/projects/{project}/resources/{resource}/unlink
• delete_resource — DELETE /v1/projects/{project}/resources/{resource}
• bulk_generate_access_codes — POST /v1/projects/{project}/plans/{plan}/access-codes/bulk-generate
• delete_access_code — DELETE /v1/projects/{project}/plans/{plan}/access-codes/{access_code}

Webhook endpoint + Token (5)

• create_webhook_endpoint — POST /v1/webhook-endpoints (the response surfaces the one-time plaintext secret)
• delete_webhook_endpoint — DELETE /v1/webhook-endpoints/{endpoint}
• rotate_webhook_secret — POST /v1/webhook-endpoints/{endpoint}/rotate-secret
• test_webhook_endpoint — POST /v1/webhook-endpoints/{endpoint}/test
• revoke_token — DELETE /v1/tokens/{token}

Broadcast (1)

• broadcast_message — POST /v1/projects/{project}/broadcasts

Sends one Telegram message to a segment of a project's members. The send is queued, so the action returns the audience it resolved and the recipient count — not a delivery result. Pair it with the Broadcast Completed trigger to log sent and failed.

Choosing the audience

Three fields compose. Audience picks a segment, Narrow to a Plan optionally restricts it to one plan, and Running Out Within (Days) sets the horizon that Expiring Soon reads.

Narrow to a Plan composes rather than replaces: Customers Only plus a plan reaches people paying for it right now, Churned Users plus a plan reaches people who held it and left. The plan and the state always describe the same subscription, so somebody paying for Silver who once trialled Gold is not a Gold customer.

The API refuses a plan on Leads, who never subscribed, and on the pass segments, whose plan is implied by the window — a 422 rather than a silently widened send.

The two single-window pass segments additionally require a Pass Window ID; the API refuses the send without one rather than quietly addressing nobody.

Subscription lifecycle (3)

• pause_subscription — POST /v1/subscriptions/{subscription}/pause (suspends resource access; billing continues)
• unpause_subscription — POST /v1/subscriptions/{subscription}/unpause (restores access and issues fresh invite links — the ones revoked at pause do not come back)
• reactivate_subscription — POST /v1/subscriptions/{subscription}/reactivate (calls off a scheduled cancellation; Stripe only, other providers error)

Team + RBAC (14)

• create_team — POST /v1/teams
• update_team — PATCH /v1/teams/{team}
• delete_team — DELETE /v1/teams/{team}
• invite_team_member — POST /v1/teams/{team}/members (addressed by email, because the invitee may not have a Subscriby account yet; the role field takes a role code that must already exist on the team)
• update_team_member_role — PATCH /v1/teams/{team}/members/{user}/role
• remove_team_member — DELETE /v1/teams/{team}/members/{user}
• cancel_team_invitation — DELETE /v1/teams/{team}/invitations/{invitation}
• create_role — POST /v1/roles
• update_role — PATCH /v1/roles/{role}
• delete_role — DELETE /v1/roles/{role}
• create_group — POST /v1/groups
• update_group — PATCH /v1/groups/{group}
• delete_group — DELETE /v1/groups/{group}
• sync_group_members — PUT /v1/groups/{group}/members

Creating and re-permissioning need the Growth plan. Deleting and removing do not — a creator whose plan lapsed still has collaborators attached and has to be able to take access away.

Searches — 45

Return a single object (wrapped in [x]) or an array. Use them in dynamic dropdowns, cross-Zap lookups, or as standalone fetch steps.

Core resources

• list_projects, get_project, find_project_by_handle
• list_plans, find_plan_by_name, find_plan_by_id
• list_subscriptions, find_subscription_by_id
• list_members, find_member_by_id, find_subscriber_by_telegram_id
• list_resources, get_resource
• list_access_codes, preview_access_code_cost
• list_support_conversations, find_support_conversation, list_support_messages

Infrastructure

• list_payment_methods, get_payment_method
• list_webhook_endpoints, list_webhook_deliveries
• list_tokens, get_token

Teams + RBAC

• list_teams, get_team, get_current_team
• list_team_members, get_team_member
• list_roles, get_role
• list_groups, get_group

Ops + distribution

• list_activity (by subject_type + subject_id)
• get_bot_status, get_bot_link, get_portal_url, get_deep_link

Analytics

All require dashboard:read except list_transactions which uses project-subscription:view-any.

• get_dashboard_metrics — MRR, active subscribers, churn, revenue trend
• get_earnings_report — gross / fees / net, timeseries by day / week / month
• get_subscriber_analytics — signups, cancellations, churn rate, trial conversion
• get_transaction_breakdown — USD totals grouped by plan, payment_provider, currency, or project
• get_plan_performance — per-plan active subs, revenue, average ticket
• list_transactions — keyset-paginated transaction list

Recipes

Prebuilt Zap ideas combining Subscriby triggers with common downstream apps. Swap the destination for whatever CRM, spreadsheet, or messaging tool fits your stack.

Revenue ops

Access codes

Team + audit

Billing

Analytics & reporting

Integrations hygiene

Troubleshooting

Source

The Zapier app is maintained at github.com/envigo-innovations/subscriby-zapier. PRs welcome. See the CHANGELOG for per-version event / action / search deltas.

Related

• Webhook events — canonical catalog of every type value.
• API authentication — how sbt_live_ / sbt_test_ tokens are minted.