Stripe to Telegram alerts with full checkout items
You get the “payment succeeded” ping… and then you still have no idea what the customer actually bought. So you click into Stripe, open the session, hunt for line items, and hope you didn’t miss the order bump or add-on.
This Stripe Telegram alerts automation hits marketers running offers the hardest. But creators with multiple products and operators trying to keep fulfillment tight feel it too. You get instant Telegram alerts that include every checkout line item, so you can act in minutes instead of digging through Stripe events.
Below, you’ll see exactly how the workflow pulls full checkout details from Stripe, formats them, and sends a clean breakdown to Telegram (with optional Gmail and WhatsApp routes).
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Stripe to Telegram alerts with full checkout items
flowchart LR
subgraph sg0["Stripe Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/stripe.svg' width='40' height='40' /></div><br/>Stripe Trigger"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Stripe | Get checkout line i.."]
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "split templates", pos: "b", h: 48 }
n3@{ icon: "mdi:cog", form: "rounded", label: "Aggregate", pos: "b", h: 48 }
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Stripe | Get product info"]
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Fields", pos: "b", h: 48 }
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Telegram"]
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/whatsapp.svg' width='40' height='40' /></div><br/>WhatsApp Business Cloud"]
n8@{ icon: "mdi:message-outline", form: "rounded", label: "Email with HTML design", pos: "b", h: 48 }
n9@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter by paid only", pos: "b", h: 48 }
n3 --> n5
n5 --> n6
n5 --> n8
n5 --> n7
n0 --> n9
n2 --> n4
n9 --> n1
n4 --> n3
n1 --> n2
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n9 decision
class n1,n4 api
classDef customIcon fill:none,stroke:none
class n0,n1,n4,n6,n7 customIcon
The Problem: Stripe Alerts Don’t Tell You What Sold
Stripe is great at telling you that money came in. It’s not great at giving you a fast, human-readable summary of what was in the cart, especially when a single checkout session contains a main product plus bumps, upsells, or “recommended add-ons.” The result is a constant context switch: you leave your work, open Stripe, click through events, and manually piece together what the customer purchased. Do that a few times a day and it becomes a background tax on your attention. Honestly, it’s not the time alone. It’s the broken flow.
The friction compounds quickly. Here’s where it breaks down in real life:
- You get a payment notification, but you still need 3-5 clicks in Stripe to see the full list of line items.
- Order bumps and extras are easy to miss, which means wrong fulfillment messages and messy handoffs.
- Teams end up copy-pasting item names into chats, and the wording changes every time.
- If you sell multiple SKUs, you can’t reliably spot patterns in what people bundle together without exporting later.
The Solution: Full Stripe Checkout Item Alerts in Telegram
This workflow listens for successful Stripe Checkout events, then immediately enriches the alert with the information Stripe doesn’t push into a simple notification. When a checkout is marked paid, n8n retrieves the session’s line items via Stripe’s API. After that, it breaks those items out, fetches the related product details, and compiles everything into a clean summary you can read at a glance. Finally, it maps the fields into a message format and sends the complete breakdown to Telegram. If you want, the same formatted payload can also go to Gmail and WhatsApp, which is handy for different teams or clients.
The workflow starts with a Stripe event trigger. From there, it filters for the paid status, retrieves all checkout items, and enriches them with product details. Then it aggregates the results and sends one readable alert to Telegram (plus optional email and WhatsApp routes).
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you run a small shop that gets about 10 Stripe checkouts a day, and each checkout can include a main product plus 2 extras. Manually, you might spend about 10 minutes per order opening Stripe, checking line items, and posting a summary to your Telegram channel, which is roughly 100 minutes daily. With this Stripe Telegram alerts automation, the “work” is basically waiting for the ping, then reading it, so maybe 1 minute per order. That’s well over an hour back each day, without losing visibility.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Stripe to trigger checkouts and fetch session data
- Telegram to receive instant line-item alerts
- Stripe API key (get it from Stripe Developers → API keys)
Skill level: Beginner. You’ll connect accounts and paste an API key, then tweak a message template.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Stripe checkout completes. The workflow starts when Stripe sends a successful Checkout event into n8n through the Stripe trigger.
Paid status is confirmed. A filter checks that the event is actually paid, so you don’t spam your channel with incomplete or irrelevant events.
Line items and product details are pulled. n8n uses HTTP requests to retrieve all checkout session items, then it breaks them out and fetches product information so names and details are readable.
One clean message goes out. The workflow aggregates everything into a single summary, maps the fields into a message, and sends it to Telegram. The same formatted output can also be routed to Gmail and WhatsApp if you want those notifications too.
You can easily modify the notification destination to Slack or Outlook based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Stripe Trigger
This workflow begins when Stripe sends a payment event to your n8n instance.
- Add and open Stripe Event Listener.
- Select the Stripe event type(s) you want to listen for (e.g., checkout or payment completion).
- Credential Required: Connect your Stripe credentials.
- Copy the webhook URL from Stripe Event Listener into Stripe’s webhook settings.
Step 2: Filter Paid Transactions
Only successful payments should continue to processing and notifications.
- Open Paid Status Filter.
- Set a condition to pass only paid/complete events based on your Stripe payload fields.
- Confirm the connection from Stripe Event Listener → Paid Status Filter is in place.
Step 3: Retrieve and Expand Line Items
This section fetches checkout line items, then breaks them out for per-item enrichment.
- Open Retrieve Checkout Items and set it to call Stripe’s line item endpoint for the checkout session.
- Credential Required: Connect your HTTP Request credentials (or configure authentication headers) for Retrieve Checkout Items.
- Open Breakout Templates to split the line items into individual entries.
- Open Fetch Product Details to retrieve product metadata for each line item.
- Credential Required: Connect your HTTP Request credentials (or configure authentication headers) for Fetch Product Details.
Step 4: Compile and Map Notification Data
Aggregate the enriched line items into a single record and map the final fields for outputs.
- Open Compile Records to aggregate all line items into a single payload.
- Open Map Output Fields and define the final fields used by your notification nodes.
- Confirm the flow Compile Records → Map Output Fields is connected.
Step 5: Configure Output Notifications
After mapping, the workflow sends alerts to Telegram, Gmail, and WhatsApp simultaneously.
- Open Send Telegram Alert and compose the alert message using fields from Map Output Fields.
- Credential Required: Connect your Telegram credentials.
- Open Dispatch Styled Email and configure the email subject, recipients, and HTML body.
- Credential Required: Connect your Gmail credentials.
- Open WhatsApp Business Notice and configure the message template and recipient.
- Credential Required: Connect your WhatsApp credentials.
- Confirm the parallel branch: Map Output Fields outputs to both Send Telegram Alert and Dispatch Styled Email and WhatsApp Business Notice in parallel.
Step 6: Test and Activate Your Workflow
Validate the full flow with a test payment before going live.
- In n8n, click Execute Workflow to listen for a test event.
- Trigger a test payment in Stripe and confirm that Paid Status Filter passes data forward.
- Verify that Telegram, Gmail, and WhatsApp notifications are received with correct mapped fields.
- When successful, toggle the workflow to Active for production use.
Common Gotchas
- Stripe credentials can expire or be restricted to the wrong mode (test vs live). If things break, check your Stripe Developers → API keys and the account mode first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Telegram bots can post to a chat only after being added and allowed to message. If alerts don’t arrive, confirm the bot is in the right channel/group and that the chat ID matches.
Frequently Asked Questions
About 20 minutes if your Stripe and Telegram accounts are ready.
No. You’ll mostly connect accounts and paste your Stripe API key. The only “tweaking” is editing the notification text to match what you want to see.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Stripe API usage (usually negligible for a small store).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s already partly wired for it. You can keep the same “Map Output Fields” step and route it to Dispatch Styled Email (Gmail) or WhatsApp Business Notice by adjusting the message body in those nodes. Common tweaks include adding the customer email, including shipping fields, or changing how line items are formatted for mobile readability.
Most of the time it’s an API key issue. Confirm you’re using the right key for live vs test mode, then update the credentials in n8n. If it fails only on some checkouts, you may be hitting missing permissions for certain endpoints, or Stripe is returning a session without the fields you expect because the event type doesn’t match.
Plenty for most small businesses. On n8n Cloud, the limit is mostly about monthly executions on your plan, and each order can create a few executions because the workflow fetches items and product details. If you self-host, there’s no hard execution cap, so it mainly depends on your server size and how bursty your sales are during launches.
Often, yes, because the “full line item breakdown” usually requires extra API calls and data shaping. n8n handles branching and aggregation cleanly, and you can self-host if you don’t want per-task pricing to creep up as volume grows. Zapier or Make can still work if you’re fine with a simpler alert that doesn’t always include enriched product details. If you’re unsure, Talk to an automation expert and map it to your exact checkout setup.
Once this is running, sales alerts become genuinely useful instead of noisy. The workflow handles the repetitive lookups so you can focus on fulfillment, support, and the next campaign.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
