Provides integration with Stripe using the public GA Stripe REST API.
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. |
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.
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. |
| Return |
Type |
Description |
Response |
Array |
One normalized row for each object returned by Stripe. List and search responses emit one row per item in data[] and copy supported paging metadata onto each row. |
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 |
Normalized response rows with Stripe response fields and mutation status fields under Flowgear. |
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 |
Normalized response rows with Stripe response fields and mutation status fields under Flowgear. |
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 |
Normalized response rows with Stripe response fields and mutation status fields under Flowgear. |
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 |
Normalized response rows with Stripe response fields and mutation status fields under Flowgear. |
- 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 list and search operations page internally. 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.Create, Update, Delete, and Action execute one Stripe request per top-level Items object and emit rows in input order.- Mutation response rows include
Flowgear.IsSuccess and Flowgear.Message. Query failures expose a normalized message field.
- 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.
- 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.