Wake an agent from Stripe events

A Stripe trigger wakes an agent when something happens in your Stripe account: an invoice payment fails, a subscription is cancelled, a charge is refunded. The agent can chase the failed payment, update your records, or brief you on who left.

For how triggers work in general (rules, Act or Propose only, the delivery log), see let an event wake your agent.

Before you start#

• An agent that has finished setting up.
• Access to the Developers area of your Stripe Dashboard.

1. Add the endpoint in Stripe#

Stripe's own guide is receive Stripe events in your webhook endpoint, and every event is described in types of events.

1. In the Stripe Dashboard, open the webhooks area under Developers and add a new endpoint (Stripe may call it an event destination).
2. Select the events you want, for example invoice.payment_failed.
3. For the endpoint URL, enter a temporary address for now, such as your own website. You replace it in step 3.
4. Save, then reveal and copy the endpoint's Signing secret (whsec_…).

2. Create the trigger in Qoren#

1. Open the agent, click Settings, then Connections, scroll to Triggers and click Add a trigger.
2. Name it in What is this for?, for example "Failed invoices".
3. Under Where does it come from?, pick Stripe (1).
4. Under Which events?, pick the same events you chose in Stripe (2).
5. Write the rules: what the agent should do with each event.
6. Paste Stripe's whsec_… secret into Already have a signing secret? (3).

123

7. Click Create trigger, and copy the Webhook URL from the card that appears. It is shown only once. The Signing secret on the card is the Stripe secret you pasted.

The events offered for Stripe are checkout.session.completed, payment_intent.succeeded, payment_intent.payment_failed, invoice.paid, invoice.payment_failed, customer.subscription.created, customer.subscription.updated, customer.subscription.deleted and charge.refunded. You can type any other Stripe event type and press Enter.

3. Point Stripe at the trigger#

1. Back in Stripe, open the endpoint you created and edit its URL.
2. Replace the temporary address with the Webhook URL from Qoren and save.

Check that it works#

• Cause a real event in Stripe's test mode, or send one with the Stripe CLI's stripe trigger command (see trigger webhook events with the Stripe CLI). It should appear in the trigger's Deliveries.
• Send a test event in the Qoren trigger sends a made-up Stripe-shaped sample straight to the agent, so you can check your rules without touching Stripe.
• Nothing in Deliveries? Stripe shows the response for each attempt on the endpoint. A refused signature means the secret in Qoren is not this endpoint's secret: create the trigger again with the right one.

What the agent receives#

Stripe puts the event type in the body, so the trigger matches on names like invoice.payment_failed. The agent gets your rules and the full event object Stripe sent, labelled as data from outside, and replies with a short summary for the delivery log.

Qoren checks Stripe's signed timestamp and refuses anything older than five minutes, so an old delivery replayed by someone else is rejected. When Stripe retries an event, Qoren recognises its event id and does not run the agent twice.