# Stripe - events - Workflow trigger | Docs - nodulz

Source: https://nodulz.com/docs/nodes/stripe_trigger

Language: en

Starts on a Stripe event received through a signed webhook.

## Usage and specifics

Create a Stripe webhook endpoint using the URL shown by nodulz. The whsec_ signing secret differs from the API key. Select events and test or live mode.

Technical type : `stripe_trigger`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Create and configure the credential : stripe-webhook](/docs/credentials/stripe-webhook)

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the [credentials guide](/docs/credentials) for access and rotation.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `rateLimitEnabled` | `boolean` | - | - |
| `rateLimitMax` | `number` | - | -; > 0 |
| `rateLimitWindowMs` | `number` | - | -; > 0 |
| `allowedIps` | `array` | - | -; max 256 |
| `blockedIps` | `array` | - | -; max 256 |
| `credentialId` | `string` | `""` | - |
| `events` | `array` | `[]` | - |
| `mode` | `enum` | `"all"` | `all`, `test`, `live` |
| `testPayload` | `string` | `""` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `events`<br>Events | Choose events that start the workflow. An empty selection accepts all received events. Configure these events in the Stripe destination too. |
| `mode`<br>Event mode | Filter events by their livemode flag. This does not change your Stripe account mode. |
| `testPayload`<br>Test event | Optional: paste a complete Stripe event as JSON. If empty, the test uses a sample Checkout session. This local test does not verify webhook delivery or signatures. |

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "credentialId": "",
  "events": [],
  "mode": "all",
  "testPayload": ""
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)