Datapipe
Founders
See revenue and refunds every morning without logging in.
Read & reportControlled changes
See your Stripe numbers in Claude.
Bring payment and customer reporting into one project. Changes you can allow for teammates and AI tools: customer, product, price, discount, subscription, invoice and refund changes. Allowed changes apply right away and are recorded in history. Refunds and price changes can be set to need approval first.
- Payments, refunds and customers in a sheet that refreshes itself
- Revenue by month without exporting from Stripe
- Tidy customer records from Datapipe, with every change recorded
ClaudeUpdated November 2026
| Date | What it was | Customer |
|---|---|---|
| Oct 27 | Card payment | Avery Chen |
| Oct 28 | Refund | Jordan Blake |
| Oct 29 | Invoice | Sam Okonkwo |
- SetupSign in, no key to copy
- Reads37 metrics and 187 ways to split them
- Changes17 change actions
- RefreshDaily to every 15 minutes
Who uses Datapipe with Stripe
Finance leads
Reconcile payments in the spreadsheet you already use.
Subscription teams
Watch churn and renewals next to signups.
What you can do with Stripe
Read and report
Read supported payments, payouts, subscriptions and customer reports.
- Customer Discount
- Refund Customer Account
- Charge Amount
- Charge Amount Captured
- and 4 more
Controlled changes
- Update approved customer fields
- Update a customer's email, phone or address
- Set or remove one metadata value
- Rename a product or change its description
- Archive or restore a product
- Change a product's default price
- Add a new price to a product
- Archive or restore a price
- Create a coupon
- Delete a coupon
- Create a promotion code for a coupon
- Turn a promotion code off or on
- Cancel a subscription at period end, or keep it renewing
- Pause or resume payment collection on a subscription
- Finalize a draft invoice
- Void an open invoice
- Refund a payment
Changes stay off until you allow them. Allowed changes apply to Stripe right away, and history keeps the values before and after.
Full read details
Use each report's definitions when comparing amounts and dates.
Examples for your team
Review payments and payouts
Put the payment and payout reports side by side before a finance check-in.
- Scheduled refresh
- Latest Stripe data
- Updated report
Limit: Their separate dates and meanings remain visible rather than being treated as the same cash movement.
Keep a customer label accurate
Correct a customer name, description or an owner-allowed metadata value.
- Allowed
- Applied
- Recorded
Limit: History keeps the before and after values.
Fix things in Stripe without opening it
Spot it, fix it
See the problem in your report, then make the fix in Datapipe instead of opening Stripe, finding the record and retyping it.
More people can help
Teammates and AI tools you allow can make changes without getting edit access to Stripe.
You decide what can change
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
Jobs you can stop doing by hand in Stripe
Update approved customer fields
Give customers real names
TodaySearch Stripe for customers named after an email or "test" and fix each one in the dashboard.
With DatapipeYour customers report shows every name in one list. Set the right company name for each, if that field is allowed.
Add CRM IDs to customer metadata
TodayCopy each customer's HubSpot ID into Stripe metadata by hand.
With DatapipeChatGPT reads HubSpot and Stripe in your project and sets the value for a metadata key the owner allowed. Each change is recorded in history, and Stripe webhooks may react.
Note who owns each account
TodayOpen customers one by one and type the account manager into the description.
With DatapipeFilter the report for blank descriptions and add a short note for each. Payments, invoices and subscriptions stay untouched.
Exactly what this can change
Updates only owner-selected customer name, description and metadata keys. Stripe webhooks and connected automations may react. External edits can race the final read and write. No payments, refunds, balances, payment methods, invoices or subscription changes.
The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.
Update a customer's email, phone or address
Send invoices to the new billing contact
TodayA client emails that invoices should go to accounts@ instead of the founder, and someone has to find the customer in Stripe and edit it.
With DatapipeChange the email on that customer, and Stripe sends future receipts and invoices there.
Fix a billing address before tax season
TodayCopy the corrected address from an email into the Stripe dashboard, field by field.
With DatapipeChatGPT corrects the street, city, postal code and country from the client's message. History keeps each line before and after.
Exactly what this can change
Changes the email, phone or billing address on one existing customer. Stripe sends receipts and invoice emails to the new email, and Stripe Tax uses the new address on future invoices. Webhooks and connected apps may react. Name, payment methods, balance, invoices and subscriptions are unchanged.
Supported fields: Email, Phone, Address line 1, Address line 2, City, State, county or province, Postal code, Country (two-letter code, for example US).
Set or remove one metadata value
Tag subscriptions with the CRM deal ID
TodayOpen each new subscription in Stripe and paste the HubSpot deal ID into metadata by hand.
With DatapipeChatGPT reads HubSpot and Stripe in your project and sets the deal ID on each subscription. History records each key and value.
Clear an old metadata key after a migration
TodayHunt through products for a legacy_sku key and delete it on each one.
With DatapipeRemove the key from each product in the report. Other keys stay as they are.
Exactly what this can change
Sets or removes one metadata key on one customer, product, price, subscription, invoice, promotion code, payment or charge. Other keys stay as they are. Apps and webhooks that read metadata may react. Amounts, prices and statuses are unchanged.
Supported fields: Metadata key, Change, Value.
Rename a product or change its description
Rename a plan customers see at checkout
TodayOpen the product in Stripe, rename it from Pro v2 to Growth and hope nobody missed a spot.
With DatapipeRename the product from Datapipe, and new checkouts, invoices and receipts show the new name.
Rewrite a vague product description
TodayCopy the description into a doc, collect edits from the team and paste the final text back.
With DatapipeA teammate writes the clearer description from Datapipe, and history keeps the old wording. Prices and subscriptions stay the same.
Exactly what this can change
Changes the name or description of one existing product. Customers see the new text at checkout and on new invoices and receipts. Prices, availability and subscriptions are unchanged.
Supported fields: Product name, Description.
Archive or restore a product
Retire a product you no longer sell
TodayFind the product in Stripe and archive it, then double-check that existing customers still renew.
With DatapipeArchive it from the products report. New sales stop, and existing subscriptions keep billing.
Bring back a seasonal product
TodayDig through archived products each autumn to restore the holiday bundle.
With DatapipeRestore the product from Datapipe when you're ready to sell it again.
Exactly what this can change
Archiving a product stops it from being used in new checkouts, invoices and subscriptions. Existing subscriptions keep billing. Restoring makes it available again. Prices are not changed.
Supported fields: Product.
Change a product's default price
Switch a plan to its new price
TodayAfter adding a new price, open the product and change which price is the default.
With DatapipeSet the new price as the product's default. Existing subscribers keep the price they already pay. Price changes can be set to need approval first.
Make the annual price the default
TodayRemember to swap the default price on each plan when you change how you sell.
With DatapipeA teammate sets the yearly price as the default for each plan, one product at a time.
Exactly what this can change
Changes the price that one product uses by default to another of its active prices. Anything that relies on the product's default price then charges the new amount. Existing subscriptions, invoices and payment links keep the prices they already use.
Supported fields: New default price ID (price_...).
Add a new price to a product
Raise a plan's price for new customers
TodayCreate a new price in the Stripe dashboard and make sure the amount and interval are right.
With DatapipeAdd the new monthly amount on the product after checking the amount, currency and interval. Current subscribers aren't moved.
Add an annual option to a monthly plan
TodayWork out the yearly amount, then add a second price to the product by hand.
With DatapipeChatGPT creates a yearly price from your monthly one. History records the exact amount.
Exactly what this can change
Creates one new price on an existing product. Stripe prices can't be edited, so this is how a price changes: add the new price here, then make it the default or archive the old one as separate changes. Nobody is charged, and existing subscriptions keep their current price.
Supported fields: Amount in the smallest currency unit (cents for USD), Currency (three letters, for example usd), Charged, Repeat every this many periods (optional), Internal nickname (optional).
Archive or restore a price
Stop selling an old price
TodayFind last year's price on the product and archive it so new checkouts can't use it.
With DatapipeArchive the old price after the new one is the default. Existing subscribers keep paying the old price.
Restore a price archived by mistake
TodaySearch archived prices and restore the right one before customers notice.
With DatapipeRestore that price ID from Datapipe, and the price can be used again.
Exactly what this can change
Archiving a price stops new checkouts, invoices and subscriptions from using it. Customers already subscribed at this price keep paying it. A product's default price can't be archived, so choose another default first. Restoring makes the price usable again.
Supported fields: Price.
Create a coupon
Set up a launch discount
TodayCreate a coupon in Stripe, pick the percentage and remember to add an end date.
With DatapipeCreate a 20% coupon that lasts once and ends on launch week's last day. History records the exact terms.
Offer a fixed credit to a partner's clients
TodayWork out the amount in cents and create the coupon by hand.
With DatapipeA teammate creates a coupon for a fixed amount off with a use limit, after checking the amount and currency.
Exactly what this can change
Creates one new coupon that takes a percentage or a fixed amount off. No customer gets it until it's used at checkout, added to an invoice or subscription, or offered through a promotion code. Set a redemption limit or an end date to cap its use.
Supported fields: Name customers see on invoices and receipts, Percent off (1 to 100), Amount off in the smallest currency unit, Currency for an amount off (three letters), Lasts, Number of months, when it repeats, Maximum number of uses (optional), Last day it can be redeemed (UTC, optional).
Delete a coupon
Retire a discount that's being shared
TodayNotice a coupon posted on a forum and delete it in Stripe as fast as you can.
With DatapipeDelete the coupon from Datapipe. New customers can't use it, and existing discounts stay.
Remove test coupons before launch
TodaySearch for coupons named test and delete each one in the dashboard.
With DatapipeDelete each test coupon from the report. You can set deletes to need approval first.
Exactly what this can change
Deletes one coupon. New customers can no longer redeem it. Customers and subscriptions that already have the discount keep it. This can't be undone.
Supported fields: Delete.
Create a promotion code for a coupon
Give a podcast sponsor its own code
TodayCreate a promotion code for the coupon in Stripe and type the code in by hand.
With DatapipeAdd a code like PODCAST20 to the existing coupon, with a use limit.
Make a first-order-only code
TodayCreate the code and remember to tick the first-time customer box.
With DatapipeA teammate creates the code for first-time customers only, after checking the settings.
Exactly what this can change
Creates one customer-facing code, such as SPRING25, for an existing coupon. Anyone who has the code can use it wherever your checkout accepts promotion codes, so set a use limit or an end date if needed.
Supported fields: Code customers type, Maximum number of uses (optional), Last day it works (UTC, optional), Who can use it.
Turn a promotion code off or on
Turn off a code after the campaign ends
TodayRemember to open Stripe on the last day and deactivate the code.
With DatapipeTurn the code off from Datapipe, and nobody can redeem it again.
Bring back a partner code
TodayFind the old promotion code and switch it back on when the partnership restarts.
With DatapipeTurn the code back on when the partner is ready.
Exactly what this can change
Turning a promotion code off stops anyone from redeeming it again. Discounts already applied stay in place. Turning it back on lets anyone with the code use it again.
Supported fields: Promotion code.
Cancel a subscription at period end, or keep it renewing
Honor a cancellation request at renewal
TodayRead the client's email, find their subscription and set it to cancel at the end of the period.
With DatapipeA teammate sets the cancellation for period end. The client keeps access until the period ends.
Keep a client who changed their mind
TodayFind the subscription that's set to cancel and undo it before the period ends.
With DatapipeUse Keep renewing on that subscription. Nothing is charged right away.
Exactly what this can change
Sets one subscription to cancel when its current billing period ends, or removes that scheduled cancellation so it keeps renewing. Nothing is charged or refunded right away. Emails set up in your Stripe settings, webhooks and connected apps may react.
Supported fields: Renewal.
Pause or resume payment collection on a subscription
Pause billing while a client's project is on hold
TodayPause payment collection on the subscription in Stripe and remember to resume it later.
With DatapipePause collection with new invoices voided. The subscription stays active.
Resume billing when work restarts
TodayFind the paused subscription and resume collection by hand.
With DatapipeResume collection from Datapipe, and Stripe collects from the next invoice.
Exactly what this can change
Pausing stops Stripe from collecting payment on one subscription while it stays active. Invoices created during the pause are voided, kept as drafts or marked uncollectible, as chosen. Resuming starts collecting again from the next invoice. Nothing is refunded.
Supported fields: Collection.
Finalize a draft invoice
Finalize a custom invoice after review
TodayCheck the draft with the account manager, then finalize it in Stripe yourself.
With DatapipeA teammate finalizes the draft after checking the amount and customer, and chooses whether Stripe charges or emails automatically.
Finalize without charging the card yet
TodayFinalize the invoice, then rush to turn off automatic collection.
With DatapipeUse Finalize only. Stripe doesn't charge or email until you decide.
Exactly what this can change
Finalizes one draft invoice so it can be paid. It can't be edited afterwards. With the invoice's own collection setting, Stripe may then charge the customer's saved payment method or email them the invoice. Choose Finalize only to stop Stripe from charging or emailing automatically.
Supported fields: Finalize.
Void an open invoice
Cancel an invoice sent by mistake
TodayFind the wrong invoice and void it before the client pays it.
With DatapipeVoid the open invoice after checking its number and amount due.
Clear a duplicate invoice
TodaySpot two open invoices for the same work and void the extra one by hand.
With DatapipeChatGPT flags the duplicate in your invoices report and voids it. History records the exact invoice.
Exactly what this can change
Voids one finalized, unpaid invoice. The customer can no longer pay it and Stripe stops collecting it. Nothing is refunded and this can't be undone. Invoices that already have a payment can't be voided here.
Supported fields: Void.
Refund a payment
Refund a double charge
TodayFind both charges in Stripe, check the amounts and refund the duplicate.
With DatapipeRefund the duplicate charge with the reason Duplicate payment. Datapipe shows what was paid and what's refundable. Refunds can be set to need approval first.
Give a partial refund for a missed delivery
TodayWork out the amount, open the payment and type a partial refund.
With DatapipeA teammate refunds the partial amount. Datapipe refuses anything above what's left to refund.
Exactly what this can change
Sends money back to the customer. Refunds one successful payment, in full or in part, up to the amount not yet refunded. The amount is in the currency's smallest unit (cents for USD). Stripe usually keeps its processing fee, and a processed refund can't be undone.
Supported fields: Amount to refund in the smallest currency unit, Reason (optional).
Update approved customer fieldsCustomer · cus_Q2f8Lm · made by Jordan Blake
| Field | Before | After |
|---|---|---|
| Name | billing@northwind.co | Northwind Traders |
You control who can change what
- A change is allowed for this data source
- A teammate or AI tool makes it
- It applies right away, or waits for approval if you set that
- Recorded with the values before and after
Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?
Provider rules and limits
Provider permissions still apply, and automations in Stripe may react to changes.
Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.
Before you connect
What you need
Sign in with Stripe.
Read and write
Read access for reports. The 17 change actions need edit access in Stripe and stay off until the owner, an admin or a project manager allows them.
Limits and exclusions
A restricted key only shows what you allowed it to read.
Full details and limits
Ready-made reports start with charges and payouts. Invoices, refunds, and fees can be picked when you build the report. A restricted key only shows what you allowed it to read.
Metrics and dimensions
37 metrics and 187 ways to split them.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Send Stripe data anywhere
Google SheetsA sheet that refreshes every morning.
Data StudioCharts that read the same numbers.
BigQueryA warehouse table for the same columns.
Excel / CSVA Drive file you can open in Excel.ClaudeAsk Claude about these numbers in a sentence.
ChatGPTAsk ChatGPT about these numbers in a sentence.
APIRead the same rows from your own tool.Don't see yours? Use CSV or APIDownload the rows, or read them from your own tool.Ask AI about your data
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also make allowed Stripe changes. They can never widen their own access.
What were the primary refund reasons and disputed charge amounts in Stripe this billing cycle?
Disputed charges totaled $3,200 across 14 transactions, concentrated in annual subscription renewal notices.
Better than exporting by hand
- It refreshes on its own, so nobody pastes in a new export.
- The same numbers can be split by who they came from.
- You can keep a row per day instead of one lump sum.
- People and the way you reach them can be their own rows.
- Products can be listed with the price and the status.
What can you do with this data?
Explore all use cases →Finance
Build a Stripe payments dashboard with ChatGPT in Looker Studio.
Review charge activity, amounts, status and currencies with ChatGPT. Export the selected Stripe report and build custom charts that keep payments distinct from payouts and profit.
See this use case →FinanceWhich unpaid invoices need a support check?
Use Stripe to find the remaining invoice balance and Zendesk to understand the customer’s open questions. Give finance and support one coordinated follow-up list.
See this use case →FinanceIs traffic growth keeping pace with our payment target?
Compare GA4 traffic, Stripe paid-payment amounts and your targets in Google Sheets without turning traffic into guessed revenue attribution.
See this use case →Start from a goal
Stripe payments dashboard
Payments, refunds on selected charges, payouts, current subscriptions and new customers.
Use this template →Card payments
Payments Stripe collected.
Use this template →Payouts to my bank
Money Stripe sent to your bank.
Use this template →Monthly subscriptions
What subscribers pay you in a typical month.
Use this template →How it works
Sign in with Stripe.
Pick where it goes. This one sends the numbers to Claude.
You're done. It refreshes every day.
Sample report
| Date | What it was | Customer | Amount | Status | Date | Amount |
|---|---|---|---|---|---|---|
| Oct 27 | Card payment | Avery Chen | $80.00 | Paid | Oct 27 | $80.00 |
| Oct 28 | Refund | Jordan Blake | $125.50 | Pending | Oct 28 | $125.50 |
| Oct 29 | Invoice | Sam Okonkwo | $42.00 | Refunded | Oct 29 | $42.00 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Works well with Stripe
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Questions
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.
No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected Stripe account. Nobody else gets a Stripe login from this.
Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.
Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.
Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that Stripe received it, the request is marked Uncertain and is never retried automatically, so you can check Stripe first.
Yes. Datapipe reads the reports on this page and can make 17 kinds of change: update approved customer fields; update a customer's email, phone or address; set or remove one metadata value; rename a product or change its description; archive or restore a product; change a product's default price; add a new price to a product; archive or restore a price; create a coupon; delete a coupon; create a promotion code for a coupon; turn a promotion code off or on; cancel a subscription at period end, or keep it renewing; pause or resume payment collection on a subscription; finalize a draft invoice; void an open invoice; refund a payment. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.
This page lists 37 metrics and 187 ways to split them. You pick the columns when you build the report.
Available rows depend on the connected account, selected report type, its date rules and provider limits. Current-inventory reports show current records rather than earlier historical states.
One for each Stripe account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Try Stripe with sample data first
Build the report first, then add Stripe when you are ready.