nodulz

Stripe

Node catalog Actions
On this page

Guided Stripe actions: customers, payments, invoices and subscriptions.

Usage and specifics

Stripe amounts use the currency’s minor unit. Keep test and live keys separate. idempotencyKey identifies repeated requests; the key permissions must cover the operation.

Technical type : stripe. 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.

Parameter Type Default Values / limits
credentialId string "" -
operation string "customers_list" -
parameters record {} -
idempotencyKey string "" -

Configuration help

idempotencyKey
Idempotency key
Optional. Use a unique business reference to prevent duplicates across runs. Otherwise, a key is generated per run, node and request. Reusing a key with different parameters causes a Stripe error.

Available operations

ID HTTP Path / parameters
customers_list GET /v1/customers - limit (integer), starting_after, ending_before, email
customers_retrieve GET /v1/customers/{id} - id *
customers_create POST /v1/customers - email, name, phone, description
customers_update POST /v1/customers/{id} - id *, email, name, phone, description
customers_delete DELETE /v1/customers/{id} - id *
payment_intents_list GET /v1/payment_intents - limit (integer), starting_after, ending_before, customer
payment_intents_retrieve GET /v1/payment_intents/{id} - id *
payment_intents_create POST /v1/payment_intents - amount * (integer), currency *, customer, payment_method, description
payment_intents_capture POST /v1/payment_intents/{id}/capture - id *, amount_to_capture (integer)
payment_intents_cancel POST /v1/payment_intents/{id}/cancel - id *
checkout_sessions_list GET /v1/checkout/sessions - limit (integer), starting_after, ending_before, customer
checkout_sessions_retrieve GET /v1/checkout/sessions/{id} - id *
checkout_sessions_create POST /v1/checkout/sessions - mode * [payment, subscription], line_items[0][price] *, line_items[0][quantity] * (integer), success_url *, cancel_url, customer, client_reference_id
checkout_sessions_expire POST /v1/checkout/sessions/{id}/expire - id *
subscriptions_list GET /v1/subscriptions - limit (integer), starting_after, ending_before, customer
subscriptions_retrieve GET /v1/subscriptions/{id} - id *
subscriptions_create POST /v1/subscriptions - customer *, items[0][price] *, items[0][quantity] (integer), payment_behavior [default_incomplete, allow_incomplete, error_if_incomplete]
subscriptions_update POST /v1/subscriptions/{id} - id *, cancel_at_period_end (boolean)
subscriptions_cancel DELETE /v1/subscriptions/{id} - id *
invoices_list GET /v1/invoices - limit (integer), starting_after, ending_before, customer, status [draft, open, paid, uncollectible, void]
invoices_retrieve GET /v1/invoices/{id} - id *
invoices_create POST /v1/invoices - customer *, collection_method [charge_automatically, send_invoice], days_until_due (integer)
invoices_finalize POST /v1/invoices/{id}/finalize - id *
invoices_send POST /v1/invoices/{id}/send - id *
invoices_void POST /v1/invoices/{id}/void - id *
refunds_list GET /v1/refunds - limit (integer), starting_after, ending_before, payment_intent
refunds_retrieve GET /v1/refunds/{id} - id *
refunds_create POST /v1/refunds - payment_intent *, amount (integer), reason [duplicate, fraudulent, requested_by_customer]
products_list GET /v1/products - limit (integer), starting_after, ending_before
products_retrieve GET /v1/products/{id} - id *
products_create POST /v1/products - name *, description
prices_list GET /v1/prices - limit (integer), starting_after, ending_before, product
prices_retrieve GET /v1/prices/{id} - id *
prices_create POST /v1/prices - product *, unit_amount * (integer), currency *, recurring[interval] [day, week, month, year]
balance_retrieve GET /v1/balance

An asterisk marks an operation-required parameter. Body fields and permissions depend on the selected operation; use its guided form and the provider’s official reference.

Initial configuration

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

json
{
  "credentialId": "",
  "operation": "customers_list",
  "parameters": {},
  "idempotencyKey": ""
}

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.

Explore further