Stripe source

The Stripe source enables you to receive Stripe webhook events directly in Knock. Stripe sends webhook callbacks when events occur in your account, such as a successful payment, a subscription change, or a customer update. Knock verifies each payload using your Stripe webhook signing secret, identifies the event type, and executes the actions you configure.

This integration is useful for building notifications around payment lifecycle events: alerting customers about successful charges, notifying your team about failed payments, or triggering onboarding workflows when new customers are created.

• A Knock account with at least one environment configured.
• A Stripe account with access to the Webhooks settings in the Stripe dashboard.

Once configured, Stripe sends webhook events to Knock in real time. You can verify that events are arriving by checking the event logs on the source environment page.

Stripe sends a wide range of event types. Below are common events you might map to actions in Knock. You can enable or disable individual event types from the source environment configuration.

Event type	Description
invoice.paid	An invoice payment succeeded
invoice.payment_failed	An invoice payment attempt failed
customer.subscription.created	A new subscription was created
customer.subscription.updated	A subscription was updated (plan change, renewal, etc.)
customer.subscription.deleted	A subscription was canceled
customer.created	A new customer was created
customer.updated	Customer details were updated
charge.succeeded	A charge completed
charge.failed	A charge attempt failed
payment_intent.succeeded	A payment intent was confirmed and paid

See the Stripe event types documentation for the full list of available events.

You can modify the default action mappings or add new ones for any event type Knock receives from Stripe. For details on how field mapping works with dot-notation paths, see the HTTP source page.

If you need to map Stripe events to actions beyond triggering workflows, see the full list of available actions in the sources overview.

Knock automatically configures idempotency for the Stripe source so duplicate events are not processed twice. By default, Knock uses [IDEMPOTENCY_KEY_PATH] from the Stripe webhook payload as the idempotency key.

You can change the idempotency key field or disable idempotency checks from the Settings tab in your source environment configuration. Events without an idempotency key attribute are processed normally.

For details on how Knock handles idempotent events, key validation rules, and the default 24-hour idempotency window, see the source event idempotency section of the sources overview.