Skip to main content

Getting started

If you have not yet set up Trigger.dev in your project, go to the quick start guide.

Installation

Authentication

The Stripe integration supports secret API Keys

Triggers

The Stripe integration exposes a number of triggers that can be used on a job, powered by Stripe webhooks. We recommend testing Stripe payloads using Stripe Shell, Stripe’s browser-based shell with the Stripe CLI pre-installed.
As you can see above, the job will be triggered on the price.created event. If you’d like to trigger a job on multiple events, you can use the aggregate version of the trigger:
“Aggregate” triggers also give you the ability to filter on specific events:
Available triggers are listed below: If there are any triggers missing that you’d like to see added, please open a new GitHub Issue

Filtering

All the Stripe triggers take an optional filter parameter that allows you to only run the job when the filter matches the event payload:
Check out our Event Filter docs for more information on how to use the filter.

Tasks

You can make reliable calls to the Stripe API inside of jobs using the exposed stripe tasks:
We automatically fill in the idempotencyKey for you, so we can gaurentee that the API call will only be executed once. Available tasks are listed below: If there are any tasks missing that you’d like to see added, please open a new GitHub Issue

Using the underlying Stripe client

You can use the underlying client to do anything the stripe-node client supports by using runTask on the integration:
Make sure to pass the idempotencyKey to the underlying client to ensure that the API call is only executed once. This is only needed for mutating API calls.

Example jobs

Code examples

Check out pre-built jobs using Stripe in our API section.