This is a dashboard integration, not an SDK call. There is no
/v1/stripe endpoint. Use it for the initial backfill, then keep the SDK for ongoing product-usage events Stripe can’t see.What gets imported
Vibefollow reads your Stripe Customers, Subscriptions, and Invoices and maps them to canonical lifecycle events:Welcome emails are suppressed for imported users, so long-standing customers don’t get a “welcome” email months after they actually signed up. Product-usage events (
feature_used, onboarding_step, usage_threshold_reached) aren’t in Stripe — keep sending those with the SDK.Create a restricted key
Vibefollow only ever needs read access, and never accepts a live secret key (sk_live_…).
1
Open the Stripe Dashboard
2
Grant read-only Billing access
Set Read on Customers (Core), and switch the entire Billing section to Read — that covers Subscriptions and Invoices in one click. No write scopes and no Account scope are required.
3
Copy the key
Create the key and copy it. A restricted key starts with
rk_. (A test-mode key works too, so you can try the import against sandbox data first.)Connect and import
1
Paste the key
In Vibefollow, open Import → Stripe, paste the restricted key, and click Connect Stripe. The key is validated live against Stripe, encrypted at rest, and never shown again.
2
Pick an import window
Choose how far back to import — all time, or the last 3 / 6 / 12 / 24 months.
3
Run the backfill
Click Import my customers. The backfill runs in the background; progress shows live and you can cancel between batches.
After the import
The import is one-time, not a live sync. You can re-run it later to pull in newer billing history, but ongoing real-time signals should come through the SDK:- Keep emitting product-usage events (
feature_used,onboarding_step,usage_threshold_reached) from your backend. - New billing events can continue to arrive via the SDK, or via a fresh Stripe import.