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.
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 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
events Events
Choose events that start the workflow. An empty selection accepts all received events. Configure these events in the Stripe destination too.
mode Event mode
Filter events by their livemode flag. This does not change your Stripe account mode.
testPayload 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.
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.
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 credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide 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.
rateLimitEnabledbooleanrateLimitMaxnumberrateLimitWindowMsnumberallowedIpsarrayblockedIpsarraycredentialIdstring""eventsarray[]modeenum"all"all,test,livetestPayloadstring""Configuration help
eventsEvents
modeEvent mode
testPayloadTest event
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "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, Executions, Node catalog.