account stream into
analytics.stripe_account. The same workflow applies to the other supported
streams.
1. Create the connections
- Create a Stripe Source connection with a secret or restricted read key.
- Test and save the connection.
- Create a PostgreSQL Destination connection.
- Test and save the destination.
2. Discover the Stripe catalog
- Create a pipeline with the Stripe source.
- Open Source and click Discover catalog.
- Enable
account. - Preview the stream, review its typed fields, and click Save stream settings.
3. Prepare the destination
Open Destinations, add the PostgreSQL connection, and save it. After the SQL revision is published, open this destination’s Published output targets, enteranalytics.stripe_account, use the stable account identifier as its
Upsert key, and use the explicit table setup action when needed.
The final table must exist before the run starts.
4. Add and publish a stable model
Open Transformations, select the PostgreSQL destination, create a transformation usingstripe.account as input, and use:
SELECT *; Stripe responses can include optional
fields that are not part of your destination contract.
5. Validate and run
- Set the final table to
analytics.stripe_account. - Set the Upsert key.
- Save draft, Validate draft, and Preview output.
- Publish revision.
- Validate the pipeline from Overview.
- Click Run all.
- Confirm success, rows written, revision, and target in Runs.
6. Expand to more streams
Repeat the destination/model setup for every additional stream you intend to deliver. Streams with acreated cursor can use Incremental sync after a
successful first run. Cursorless streams remain Full Table.
See Stripe source for the complete
34-stream inventory and current limitations.