Connect Stripe to Airtable
Pull your Stripe data — customers, invoices, subscriptions, charges and more — into a sheet or database to track revenue, MRR and churn without a BI tool.
What you can pull from Stripe
Stripe exposes 8 objects you can pull, each as its own job. Every run pulls the records into a flat table, so nested fields arrive as ordinary columns that Airtable can sort, filter and total without further work.
Customers
The customer list with metadata.
Subscriptions
Plans, status and interval - the raw material for MRR.
Invoices
Billing history and outstanding amounts.
Charges
Individual payments and their status.
Payment intents
Attempts, including the ones that failed.
Balance transactions
What actually hit your balance, with fees.
Products
Your catalogue.
Prices
Price points against those products.
Options you can set
- resource
- Which Stripe object to fetch — defaults to
customers - created_after
- Only objects created at or after this time
- created_before
- Only objects created at or before this time
How it lands in Airtable
Airtable accepts append, upsert writes. Upsert is the one that matters on a schedule: it merges on a key you choose, so matching rows are updated in place and only genuinely new records are created. Append instead, and a daily job multiplies your data.
Upsert merges on up to three key fields. Matching records are updated in place; only genuinely new rows are created.
- At most 3 merge fields - Airtable rejects more.
- Writes go 10 records per request, at 4 requests per second by default (Airtable’s own ceiling is 5) - roughly 2,400 records a minute.
- typecast is on by default, letting Airtable coerce strings into select, number and date fields rather than rejecting the write.
- unknown_fields defaults to error, so a renamed source column fails loudly instead of silently dropping data. Set it to skip if you would rather drop.
Authentication
Stripe authenticates with an API key held as a stored connection, so it never appears in a spreadsheet cell, a formula, or a shared copy of a sheet.
Keeping runs incremental
Yes. Filter with created_after and created_before so a run fetches a window rather than your whole history.
Pair a narrowed read with an upsert write and a re-run costs almost nothing: the rows it already knows are updated, and nothing is duplicated. That combination is what makes a frequent schedule affordable.
A worked example
A customer table that stays in sync
Pull customers filtered to the last 90 days, upsert on the Stripe id, and the base updates rather than duplicating. Because the key is stable, you can link those records to deals or tickets and the links survive every run.
Schedule: 0 6 * * * — read it back in plain English
Limits and pacing
These are the provider-side ceilings that shape a schedule, not ours. Knowing them up front is the difference between a job that runs quietly every morning and one that starts failing the week your data grows.
| Limit | Value | Applies to |
|---|---|---|
| Page size Stripe's own maximum per request. | 100 records | Stripe |
Common gotchas
Most of what goes wrong with a scheduled sync is not a bug — it is a detail of how one side behaves that nobody wrote down. These are the ones that come up for this pair.
Amounts are in the smallest currency unit
A value of 5000 on a USD object is $50.00, not $5,000. Divide by 100 in a computed field, or you will present a number a hundred times too large.
Annual plans are not monthly revenue
A yearly subscription at $1,200 is $100 of MRR. If you have mixed billing intervals, normalise before summing.
Do not key an upsert on email
People change their email address. When they do, upsert cannot match, so it creates a second record - the exact duplicate you were trying to prevent, plus a stale one. Use a stable ID from the source system.
The key field has to be written
If you restrict which columns get written and the key field is not among them, there is nothing to match on and every row is treated as new.
A row that is a fact per period needs a compound key
For a daily history, one row is one entity per day. Key on the entity alone and each day overwrites the last, leaving no history at all.
Divide amounts before they reach a currency field
Stripe sends the smallest currency unit and Airtable currency fields do not know that. Convert in a computed field, or every figure is 100x too large.
Set it up in four steps
- 1
Connect Stripe
A Stripe API key. A restricted read-only key is enough - this never writes.
- 2
Connect Airtable
Connect your Airtable account once, then pick a base and table.
- 3
Shape the data
Select the columns you want, filter rows, cast types and add computed fields. Everything else is dropped before it reaches the destination.
- 4
Schedule it
Run once, or on a cron. Every run refreshes Airtable with the latest Stripe data.
Do I need an add-on or extension for this?
No. The job runs server-side and writes into Airtable through its API, so there is nothing installed in the destination itself. It keeps running when nobody has the file open, and a copy of the file does not need anything installed to work.
How often does the data refresh?
On whatever schedule you set with a cron expression — hourly, daily, or a specific time on specific days. Each run pulls the latest from Stripe.
Do I need to write any code?
No. You connect both sides, map the fields in a wizard and set a schedule. Computed fields accept small expressions — abs, round, min, max, len — but there is nothing to host or maintain.
Does this need write access to Stripe?
No. A restricted read-only API key is enough - the connector only ever reads.
Why are the amounts wrong by a factor of 100?
They are not wrong, they are in the smallest currency unit: 5000 means $50.00. Divide by 100 in a computed field before it reaches a currency column.
How do I stop duplicate records appearing?
Use upsert rather than append, and key it on a stable identifier from the source. Append creates new records every run, so a daily job leaves seven copies of every row by the end of the week.
How fast can it write?
Airtable accepts 10 records per request, and writes are paced at 4 requests a second by default against a ceiling of 5 - roughly 2,400 records a minute. That is comfortable for thousands of rows and worth planning around for hundreds of thousands.
Is the Stripe connector free to use?
You can connect Stripe and start syncing on the free plan.
Other sources into Airtable
Related reading
Airtable upsert: stop creating duplicate records
Appending on every run turns a tidy base into six copies of every row. Here is how upsert works in Airtable, and how to choose a merge key that holds up.
Export Stripe data to Google Sheets
Stripe's dashboard exports are manual and stale the moment you download them. Here is how to keep customers, invoices and charges fresh in a sheet instead.
Import a CSV from a URL into Airtable
Point a job at a CSV link and it re-reads it on your schedule — no download, no manual import. Here is the setup, and the field-type trap to avoid first.