Never opened

Stripe


Stripe


Stripe

Stripe

Beta version

The configuration and connection might need a bit of fine-tuning to get things running smoothly. Let us know if you hit any snags at team@tably.com.

Once created, a connection can be reused or copy-pasted in all other pages within same workspace without additional setup. The setup can be complex and, if in doubt, ask your developer for help. They will have all needed details and will be able to assist with possible errors.

Your Stripe account ID (starts with 'acct_', find yours here).
Stripe API key (usually starts with 'sk_live_'; find yours here).
When set, the connector will always re-export data from the past N days, where N is the value set here. This is useful if your data is frequently updated after creation. The Lookback Window only applies to streams that do not support event-based incremental syncs: Events, SetupAttempts, ShippingRates, BalanceTransactions, Files, FileLinks, Refunds. More info here
The time increment used by the connector when requesting data from the Stripe API. The bigger the value is, the less requests will be made and faster the sync will be. On the other hand, the more seldom the state is persisted.
The number of worker thread to use for the sync. The performance upper boundary depends on call_rate_limit setting and type of account.
Select streams where cursor age is validated against the Stripe API 30-day event retention period. When a selected stream's cursor is older than 30 days, the connector performs a full refresh to avoid missing data. Streams not selected here will always use incremental sync regardless of cursor age.
The number of API calls per second that you allow connector to make. This value can not be bigger than real API call rate limit (https://stripe.com/docs/rate-limits). If not specified the default maximum is 25 calls per second for test/sandbox tokens and 100 for production tokens.
Loadingโ€ฆ