Online payment processing for internet businesses
Stripe currently provides 13 triggers that can start a workflow and 19 actions a workflow can run. Use those building blocks to connect customer and order activity to the relationship record behind it.
New Payment
Triggers when a new payment is made
New Customer
Triggers when a new customer is created
Payment Failed
Triggers when a payment fails
New Subscription
Triggers when a new subscription is made
New Charge
Fires when a charge is successfully completed.
New Invoice
Fires when an invoice is created. Supports filters like status, customer, subscription.
Invoice Payment Failed
Fires when a payment against an invoice fails.
Canceled Subscription
Fires when a subscription is canceled.
New Refund
Fires when a charge is refunded (full or partial).
New Dispute
Fires when a customer disputes a charge.
New Payment Link
Fires when a new Payment Link is created.
Updated Subscription
Fires when an existing subscription is changed.
Checkout Session Completed
Fires when a Stripe Checkout Session is successfully completed.
Create Customer
Create a customer in stripe
Create Invoice
Create an Invoice in stripe
Search Customer
Search for a customer in stripe by email
Search Subscriptions
Search for subscriptions by price ID, status, customer ID and other filters, including customer details
Retrieve Customer
Retrieve a customer in stripe by id
Update Customer
Modify an existing customer’s details.
Create Payment (Payment Intent)
Creates a new payment intent to start a payment flow.
Create Product
Create a new product object in Stripe.
Create Price
Create a price (one-time or recurring), associated with a product.
Create Subscription
Start a subscription for a customer with specified items/prices.
Cancel Subscription
Cancel an existing subscription, either immediately or at the end of the current billing period.
Retrieve an Invoice
Retrieves the details of an existing invoice by its ID.
Retrieve a Payout
Retrieves the details of an existing payout by its ID.
Create a Refund
Create a full or partial refund for a payment.
Create Payment Link
Creates a shareable, Stripe-hosted payment link for one-time purchases or subscriptions.
Deactivate Payment Link
Disable or deactivate a Payment Link so it can no longer be used.
Find Payment (by Payment Intent ID)
Retrieves the details of a payment by its unique Payment Intent ID.
Find Invoice
Finds an invoice by its unique ID.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Stripe event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Payment
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Stripe action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Customer
Combine Stripe with another integration and Coherence records to connect customer and order activity to the relationship record behind it.
Starts with
New Payment
Finishes with
Create Customer, then preserve the outcome in Coherence
The exact authentication fields depend on Stripe. The workflow structure stays straightforward:
Authorize the Stripe account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Stripe or provide a complementary trigger or action.
Stripe currently provides 13 triggers that can start a workflow and 19 actions a workflow can run. Use those building blocks to connect customer and order activity to the relationship record behind it.
Stripe currently lists 13 triggers and 19 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Stripe triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
