Skip to product information

n8n Stripe Webhook Telegram Bot Access + Daily Reconciliation

n8n Stripe Webhook Telegram Bot Access + Daily Reconciliation

 (200+Reviews)
Regular price £43.99
Regular price £43.99 Sale price
SAVE Sold out
Instant Digital Download
Unlimited Downloads
Lifetime Access in Your Account
🔥
128+ Sold
Popular with n8n builders
23 people viewing
High interest right now
9 added today
Fast-moving digital product
n8n Stripe Webhook Telegram Bot Access + Daily Reconciliation

n8n Stripe Webhook Telegram Bot Access + Daily Reconciliation

Regular price £43.99
Regular price £43.99 Sale price
SAVE Sold out

Keep Telegram access in sync with Stripe—instantly and every morning

This n8n workflow listens to Stripe webhook events to grant or revoke Telegram access, then performs a daily reconciliation to correct any drift by checking each subscription’s live status in Stripe. If something doesn’t match what access was granted, it fixes the entitlement and posts a summary to Slack.

What this workflow does

  • Handles Stripe webhooks for checkout completion, subscription updates, and subscription deletions.
  • Ensures idempotency by checking a Data Table ledger to skip Stripe events already processed, and records new event IDs as they’re handled.
  • Maps entitlements from Stripe metadata: extracts the Telegram user ID and subscription details from Stripe metadata, then maps the Stripe Price ID to a tier.
  • Updates your access ledger: upserts each user’s entitlement (tier, active flag, and Stripe IDs) into a Data Table keyed by Telegram user ID.
  • Runs daily reconciliation: scheduled execution reads all entitlement rows, fetches each subscription’s live status from the Stripe API, and detects mismatches using a configurable grace period for past-due statuses.
  • Corrects drift automatically: updates entitlement rows to match Stripe and posts a corrections summary to a Slack channel.
  • Protects Telegram content: when Telegram messages arrive, it checks the sender’s entitlement in the Data Table—either sends the protected message or replies with a Stripe Payment Link prompt.

Use cases

  • Preventing “access drift” when subscriptions change but webhooks are delayed or missed.
  • Automating subscription-based access to Telegram content for SaaS and digital products.
  • Providing operational visibility by reporting reconciliation corrections in Slack.

Technical details

  • Integrations/Nodes used: Stripe Trigger, if, set, code, Slack, filter, Telegram, plus HTTP calls for subscription lookup.
  • Credentials required: add Stripe credentials for the Stripe Trigger and an HTTP Bearer Auth credential using your Stripe secret key for the subscription status lookup request.
View full details