Quickstart · 5 minutes
Five steps from sign-up to your first synced Airtable row. No video needed — text + screenshots, with Pro tips and the pitfalls we see most often.
Video tutorials are great for first impressions but bad for the person who is trying to onboard at 11pm with autoplay disabled. This page is the source of truth for the five steps; the video lands when it earns its place in the flow.
Three things to have ready before you start the clock.
Read top-to-bottom, or jump to a step using the in-page links.
Open airsource.io and join the waitlist. During the private beta window the waitlist auto-converts to a 14-day private beta access invite — private beta — June 2026.
You will receive a magic-link email. Clicking it signs you in and drops you straight into the dashboard with a 'Create your first sync' empty state.
Pro tip: Magic links are single-use and expire after 15 minutes. If it expires, request a fresh one — emails arrive in under a minute.
In the Stripe Dashboard, open Developers > API keys, scroll to the Restricted keys section, and click '+ Create restricted key'. Name it 'airsource SaaS - Read Only'.
Under Permissions, set Customers / Subscriptions / Invoices / Charges / Products / Prices / Balance to Read only — leave everything else as None. Click Create key, copy the rk_test_... (or rk_live_...) string, and paste it into airsource.
Pro tip: Start in Stripe test mode for your first connection. Test keys start with rk_test_... and let you verify the mapping against fake data before pointing at production. airsource never writes back to Stripe — but verifying in test mode is a habit worth keeping.
Open airtable.com/create/tokens, click 'Create new token', and call it 'airsource SaaS'. Tick exactly three scopes: data.records:read, data.records:write, schema.bases:read.
Under Access, click 'Add a base' and pick the destination base. Click Create token, copy the pat... string. Then grab the Base ID (the app... string from your Airtable URL) and Table ID (the tbl... string). Paste all three into airsource.
Pro tip: airsource never needs data.records:delete or schema.bases:write. If a third-party setup guide ever asks for either, that is a flag — stick to the minimum three scopes above.
airsource pings Claude with a sample of your Stripe schema and your Airtable column list. Claude returns a proposed field-to-column mapping with a confidence level and one-sentence reason per row.
High-confidence mappings auto-apply. Low-confidence ones (typically custom metadata fields) ask for explicit approval. You can override any suggestion in one click. Once approved, the mapping is stored — and the next time you (or any other customer) connect the same schema pair, the AI uses your decisions as context.
Pro tip: Take 30 seconds to scan the table before approving. The AI is right about 95% of the time on standard e-commerce schemas, but the 5% are the cases you most want to catch — usually a metadata field that means something specific to your business.
Click 'Run first sync now' in the airsource dashboard. The job pulls every Stripe customer, subscription, invoice, and charge that matches your filter and upserts them into the target Airtable table. For a fresh account with a few dozen customers, the first sync finishes in 15-45 seconds.
Switch back to Airtable. New rows appear in your table, each with a Last Synced timestamp so you can confirm freshness at a glance. From this point on, the sync runs automatically every 15 minutes on Starter, or in near-realtime via webhooks on Pro and Business.
Pro tip: Pin the auto-created Sync Logs table to see which jobs ran when and how many records were touched. If a job ever fails, airsource retries with exponential backoff and writes the failure to a sync_errors table so nothing is silently lost.
Five symptoms we see in support tickets most often, each with the one-line fix.
You synced one source. Here are the three things most teams do next.
14-day private beta access, private beta — June 2026.
