Appearance
Stripe
Accept payments, manage subscriptions, and handle payouts with the Stripe API.
| Detail | Value |
|---|---|
| Category | Payments |
| Base URL | https://api.stripe.com/ |
| Authentication | Bearer Token |
| Endpoints | 8 |
| Connector key | stripe |
Using Stripe in a workflow
- Go to Connections and click New Connection.
- Pick Stripe from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /charges | Create a new charge |
GET /charges/{charge_id} | Retrieve a charge by ID |
POST /payment_intents | Create a payment intent |
GET /customers | List all customers |
POST /customers | Create a new customer |
POST /refunds | Create a refund |
GET /invoices | List all invoices |
POST /subscriptions | Create a subscription |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /charges
Create a new charge
| Detail | Value |
|---|---|
| Operation ID | payments.createCharge |
| Method | POST |
| Path | /charges |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stripe connection from the Connection dropdown.
- In the Operation dropdown, select
payments.createCharge. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stripe API reference.
GET /charges/{charge_id}
Retrieve a charge by ID
| Detail | Value |
|---|---|
| Operation ID | payments.getCharge |
| Method | GET |
| Path | /charges/{charge_id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
charge_id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stripe connection from the Connection dropdown.
- In the Operation dropdown, select
payments.getCharge. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stripe API reference.
POST /payment_intents
Create a payment intent
| Detail | Value |
|---|---|
| Operation ID | payments.createPaymentIntent |
| Method | POST |
| Path | /payment_intents |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
amount | integer |
currency | string |
payment_method_types | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stripe connection from the Connection dropdown.
- In the Operation dropdown, select
payments.createPaymentIntent. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stripe API reference.
GET /customers
List all customers
| Detail | Value |
|---|---|
| Operation ID | payments.listCustomers |
| Method | GET |
| Path | /customers |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
limit | query | integer | No |
starting_after | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stripe connection from the Connection dropdown.
- In the Operation dropdown, select
payments.listCustomers. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stripe API reference.
POST /customers
Create a new customer
| Detail | Value |
|---|---|
| Operation ID | payments.createCustomer |
| Method | POST |
| Path | /customers |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
email | string |
name | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stripe connection from the Connection dropdown.
- In the Operation dropdown, select
payments.createCustomer. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stripe API reference.
POST /refunds
Create a refund
| Detail | Value |
|---|---|
| Operation ID | payments.createRefund |
| Method | POST |
| Path | /refunds |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
charge | string |
amount | integer |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stripe connection from the Connection dropdown.
- In the Operation dropdown, select
payments.createRefund. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stripe API reference.
GET /invoices
List all invoices
| Detail | Value |
|---|---|
| Operation ID | payments.listInvoices |
| Method | GET |
| Path | /invoices |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
customer | query | string | No |
status | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stripe connection from the Connection dropdown.
- In the Operation dropdown, select
payments.listInvoices. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stripe API reference.
POST /subscriptions
Create a subscription
| Detail | Value |
|---|---|
| Operation ID | payments.createSubscription |
| Method | POST |
| Path | /subscriptions |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
customer | string |
items | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Stripe connection from the Connection dropdown.
- In the Operation dropdown, select
payments.createSubscription. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Stripe API reference.