Provides integration with Stripe for template-driven commerce operations and authenticated webhook events.
0.1.0.4 - Added authenticated webhook verification with replay-tolerance checks.
0.1.0.2 - Preserved inherited fields in designer templates when OpenAPI schemas use constraints-only allOf overlays.
0.1.0.1 - Split operations into Query, Create, Update, Delete, and Action methods.
0.1.0.0 - Added explicit eager first-page and first-item handling with lazy continuation.
0.0.1.5 - Published the previous Stripe surface.
0.0.0.5 - Initial release.
Use this Connection to store the Stripe API key and request settings used by the Node.
| Property |
Type |
Description |
Secret Key |
Masked |
Stripe secret or restricted key used as the Basic authentication username. |
Webhook Signing Secret |
Masked |
Endpoint signing secret beginning with whsec_ used to verify Stripe webhook deliveries. |
Stripe API Version |
String |
Stripe API version used for requests. The default is 2026-05-27.dahlia. |
Stripe Context |
String |
Optional Stripe-Context header value for related-account execution. Use this instead of Stripe Account when required by your Stripe integration. |
Stripe Account |
String |
Optional Stripe-Account header value. Leave this blank when Stripe Context is set. |
Financial Connections Endpoint Family |
String |
Selects which Stripe Financial Connections account endpoint family to use. The default is Financial Connections. Use Linked Accounts (Legacy) only when your Stripe integration still requires it. |
Timeout (seconds) |
Integer |
Timeout used for Stripe Connection validation and runtime API calls. The default is 30. |
- Create or locate a Stripe secret or restricted key that has access to the operations you want to run.
- Create a Flowgear Connection and enter the key in
Secret Key.
- Leave
Stripe API Version at the default value unless your Stripe integration requires a different pinned API version.
- For related-account execution, set either
Stripe Context or Stripe Account. Do not set both values on the same Connection.
- Leave
Financial Connections Endpoint Family set to Financial Connections unless your Stripe integration still uses the legacy linked-accounts routes.
- Run the Connection test. Flowgear calls
GET /v1/account with the configured Stripe API version and account context.
For webhook Workflows, copy the endpoint-specific signing secret from Stripe into Webhook Signing Secret.
The Stripe Node exposes template-driven methods backed by the embedded Stripe OpenAPI schema. Select a template so Flowgear fills in the correct OperationId, Options, and, when applicable, Items contract.
Use Query to execute supported Stripe read operations.
| Parameter |
Type |
Description |
Connection |
Connection |
Stripe Connection profile. |
OperationId |
String |
Identifier of the query operation selected by the template. |
Options |
Object |
Route and query values required by the selected operation. |
CustomParameters |
Object |
Custom placeholder values referenced from Options by names such as @name. |
| Return |
Type |
Description |
Response |
Array |
Provider-shaped Stripe response rows. List and search responses emit one row per item in data[], copy supported paging metadata onto each row, return zero rows for valid no-match outcomes, and surface first-call provider failures instead of returning empty success rows. |
Use Create to execute supported Stripe create operations.
| Parameter |
Type |
Description |
Connection |
Connection |
Stripe Connection profile. |
OperationId |
String |
Identifier of the create operation selected by the template. |
Options |
Object |
Route and query values required by the selected operation. |
Items |
Array |
Structured request body for the selected create template. Each top-level item is sent as a separate Stripe request. |
| Return |
Type |
Description |
Response |
Array |
Mutation response rows that preserve Stripe response fields and add the Flowgear mutation object with IsSuccess, Message, and Request. Rows also include httpStatus and requestId when Stripe returns those values. |
Use Update to execute supported Stripe update operations.
| Parameter |
Type |
Description |
Connection |
Connection |
Stripe Connection profile. |
OperationId |
String |
Identifier of the update operation selected by the template. |
Options |
Object |
Route and query values required by the selected operation. |
Items |
Array |
Structured request body for the selected update template. Each top-level item is sent as a separate Stripe request. |
| Return |
Type |
Description |
Response |
Array |
Mutation response rows that preserve Stripe response fields and add the Flowgear mutation object with IsSuccess, Message, and Request. Rows also include httpStatus and requestId when Stripe returns those values. |
Use Delete to execute supported Stripe delete operations.
| Parameter |
Type |
Description |
Connection |
Connection |
Stripe Connection profile. |
OperationId |
String |
Identifier of the delete operation selected by the template. |
Options |
Object |
Route and query values required by the selected operation. |
Items |
Array |
Optional structured request body when Stripe documents one for the selected delete template. Each top-level item is sent as a separate Stripe request. |
| Return |
Type |
Description |
Response |
Array |
Mutation response rows that preserve Stripe response fields and add the Flowgear mutation object with IsSuccess, Message, and Request. Rows also include httpStatus and requestId when Stripe returns those values. |
Use Action to execute supported Stripe non-CRUD operations, e.g. cancel, confirm, capture, refund, attach, detach, disconnect, refresh, or finalize operations.
| Parameter |
Type |
Description |
Connection |
Connection |
Stripe Connection profile. |
OperationId |
String |
Identifier of the action operation selected by the template. |
Options |
Object |
Route and query values required by the selected operation. |
Items |
Array |
Structured request body for the selected action template. Each top-level item is sent as a separate Stripe request. |
| Return |
Type |
Description |
Response |
Array |
Mutation response rows that preserve Stripe response fields and add the Flowgear mutation object with IsSuccess, Message, and Request. Rows also include httpStatus and requestId when Stripe returns those values. |
Verifies a Stripe webhook signature before parsing and returning the authenticated event.
| Parameter |
Type |
Description |
Connection |
Connection |
Stripe Connection containing the endpoint-specific webhook signing secret. |
Stripe-Signature |
String |
Exact Stripe-Signature HTTP header value received from Stripe. |
Payload |
Stream |
Untouched request-body stream returned by HTTP Receive Stream. |
Tolerance (seconds) |
Integer |
Maximum allowed difference between the signed timestamp and current UTC time. The default is 300. |
| Return |
Type |
Description |
Event |
Object |
Verified, provider-shaped Stripe event JSON. |
- Use the template picker to select a supported Stripe operation. Templates set
OperationId and expose the matching typed Options and Items fields.
- The Node validates required route and query values in
Options before sending a request to Stripe. Missing values such as Options.account return a normalized error row.
Query fetches its first provider page while the Node invoke is awaited. List and search operations then request later pages only as the output is consumed. Raw Stripe paging controls such as limit, starting_after, ending_before, and page are removed from templates where the Node manages them.Query responses keep Stripe response fields where possible. List and search wrappers are unwrapped so each data[] item becomes a separate Response row, and valid no-match outcomes return zero rows.Create, Update, Delete, and Action execute the first Items object while the Node invoke is awaited. Later objects are read and sent only as the output is consumed, and an empty connected Items stream performs no work.- Mutation response rows include
Flowgear.IsSuccess, Flowgear.Message, and Flowgear.Request.
- When Stripe response fields would conflict with Flowgear status fields, the provider values are returned as fields such as
providerStatus, providerStatusMessage, or providerErrorMessage.
- Rows include
httpStatus and requestId when those values are available from the Stripe response.
- The
Linked Accounts (Legacy) endpoint family remaps only the equivalent Financial Connections account operations: list account, retrieve account, disconnect account, list account owners, and refresh account. Other selected Financial Connections operations return a normalized error row in legacy mode.
- Start webhook Workflows with HTTP Receive Stream and map its untouched body stream to
Payload. Parsed JSON receive variants cannot be used because Stripe signs the exact request body.
- Map the HTTP
Stripe-Signature header to the matching method parameter. Invalid signatures, stale timestamps, malformed UTF-8, and non-object JSON fail the Step before event data is returned.
- The Node does not expose
/v1/files* endpoints or GET /v1/quotes/{quote}/pdf.
- The Node does not add automatic Stripe idempotency keys or automatic backoff for
429 responses.