Stripe Trigger

Overview

The Stripe trigger fires your procedure when a Stripe event occurs in your account — for example when a payment succeeds, a customer is created, or a charge is refunded.

Setup

1. Go to Connections in the Rapidfolio dashboard and connect your Stripe account.
2. Open the procedure you want to trigger and add a Stripe trigger.
3. Select the event types you want to listen for, then save the trigger.
4. Copy the generated webhook URL and register it in your Stripe Dashboard under Developers → Webhooks → Add endpoint.

Webhook URL

https://run.rapidfolio.com/triggers/:triggerId/stripe

Replace :triggerId with the trigger ID shown in the Rapidfolio dashboard.

Signature Verification

Rapidfolio verifies the Stripe-Signature header on every inbound request using your Stripe webhook signing secret. Requests with an invalid or missing signature are rejected with a 400 response.

You do not need to configure this yourself — Rapidfolio handles it automatically when you connect your Stripe account.

Configuration

Field	Description
Connection	The Stripe connection to listen on
Event types	One or more Stripe event types to subscribe to (see below)

Supported Event Types

Event type	Description
payment_intent.succeeded	A PaymentIntent was successfully completed
payment_intent.payment_failed	A PaymentIntent failed
payment_intent.created	A PaymentIntent was created
payment_intent.canceled	A PaymentIntent was canceled
customer.created	A new customer was created
customer.updated	An existing customer was updated
customer.deleted	A customer was deleted
charge.succeeded	A charge succeeded
charge.failed	A charge failed
charge.refunded	A charge was fully or partially refunded
charge.dispute.created	A dispute was opened on a charge
invoice.paid	An invoice was paid
invoice.payment_failed	An invoice payment attempt failed
subscription.created	A subscription was created
subscription.updated	A subscription was updated
subscription.deleted	A subscription was canceled

Any valid Stripe event type can be entered if it is not listed above.

Payload

The trigger payload is the raw Stripe event object. Access it in your procedure via the trigger input.

{
  "id": "evt_3OqXYZ2eZvKYlo2C1234abcd",
  "object": "event",
  "type": "payment_intent.succeeded",
  "created": 1710000000,
  "livemode": false,
  "data": {
    "object": {
      "id": "pi_3OqXYZ2eZvKYlo2C1234abcd",
      "object": "payment_intent",
      "amount": 5000,
      "currency": "gbp",
      "status": "succeeded",
      "customer": "cus_PqRsT1234567890",
      "metadata": {
        "order_id": "ord_001"
      }
    }
  }
}

The data.object field contains the Stripe resource that the event relates to (a PaymentIntent, Customer, Charge, etc.).

Example Use Cases

• Automatically onboard a customer in your internal system when customer.created fires.
• Trigger a KYC verification workflow when a first payment_intent.succeeded is received.
• Send an internal alert and open a case when charge.dispute.created fires.
• Reconcile ledger entries whenever invoice.paid occurs.