Daily Stripe Charge Summary
Every day, see all Stripe charges without logging in. Stay on top of transaction activity effortlessly.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Charges
Retrieves a list of stripe charges with filtering and pagination; use valid cursor ids from previous responses for pagination, and note that charges are typically returned in reverse chronological order.
Why this helps
You forget to check daily transaction activity in Stripe, missing spikes, unusual patterns, or payment issues.
- Daily charge summary delivered to your preferred channel automatically
- Spot transaction patterns, spikes, or anomalies instantly
- Stay informed without manual Stripe login
Setup
Build it in a few focused steps.
- 1Connect Stripe to Notis.
- 2Create the automation: 'Every day at 10am, pull a list of all charges from Stripe and send me a summary'.
- 3Set the trigger to 'Daily at 10am' (or your preferred time).
- 4Choose your notification channel (Telegram, Slack, or email).
- 5Review the first summary to confirm it has the details you need.
Questions about this workflow
Can Notis summarize by payment method or customer?
Yes. Specify in your prompt: 'group charges by payment method' or 'show top 10 customers by charge volume', and Notis will organize the summary accordingly.
Does it include failed charges?
By default, it lists all charges. You can refine it to 'only successful charges' or 'only failed charges' if you prefer.
Can I get a weekly or monthly summary instead?
Yes. Change the frequency to 'weekly' or 'monthly', and Notis will adjust automatically.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Stripe. A trigger fires from one place; an action lands in another.
Notion triggers
Stripe actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
New Page
Triggers when a new page is added to a Notion database.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Not just Notion and Stripe. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Stripe.