OTHER
Grant Discord Role on Stripe Subscription Start
When a member completes a paid Stripe subscription, automatically assigns the matching Discord role so they get instant access to gated channels.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe subscription created webhookStripe
- LogicMap price ID to Discord tier role
- ActionLook up member's Discord ID in PostgresPostgres
- ActionAdd tier role to Discord memberDiscord
- ActionWrite grant to audit tablePostgres
- OutputDM member access confirmationDiscord
What it does
Listens for successful Stripe subscription events and grants the correct Discord role to the buyer the moment their payment clears, unlocking the channels that tier is entitled to. No manual role-handing in the server.
When to use it
Run this when you sell paid community memberships through Stripe and want access provisioned instantly instead of waiting for an admin to react to a screenshot of a receipt.
How it works
- 1A Stripe webhook fires on `customer.subscription.created` (or `checkout.session.completed`).
- 2The flow reads the price/product ID and looks up the matching Discord role in a tier map.
- 3A branch confirms the subscription is active and the price maps to a known tier; unknown prices route to a fallback notice.
- 4It resolves the buyer's Discord user ID from the linking record stored in Postgres.
- 5Discord's API adds the role to that member.
- 6The grant (customer, tier, role, timestamp) is written to a Postgres audit table and a confirmation DM is sent.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect DiscordCommunity channels + voice + bots.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Other workflows
Sweep stale visitor check-ins, auto-checkout, and flag overdue guests
On a recurring schedule this finds visitors still marked on-site past their expected departure, auto-checks-out anyone past end-of-day.
Pre-register a visitor, email a QR badge, and alert the host on arrival
When a host submits a visitor pre-registration form, this creates a visitor record, emails the guest a scannable QR badge with arrival instructions.
Build a daily expected-visitor roster and send it to the front desk
Every morning this pulls the day's pre-registered visitors from Airtable, builds a sorted arrival roster with hosts and times.
Agent-Driven Full IVR Re-Voicing for a Rebrand
An agent takes a rebrand brief from Notion, audits every IVR prompt for old naming, rewrites and re-synthesizes the affected ones with ElevenLabs, archives them to Dropbox.
Sync IVR Prompt Registry in Airtable to Fresh ElevenLabs Audio
Runs nightly against an Airtable IVR prompt registry, finds rows whose script text changed since last synthesis, regenerates only those ElevenLabs clips.
Slack-Approved IVR Re-Voicing After a Product Rename
On demand from Slack, drafts updated IVR prompt scripts for a renamed product, posts them for human approval.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.