Appearance
Flutterwave
undefined
| Detail | Value |
|---|---|
| Category | Finance |
| Base URL | https://api.flutterwave.com/v3 |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | flutterwave |
Using Flutterwave in a workflow
- Go to Connections and click New Connection.
- Pick Flutterwave 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 |
|---|---|
GET | Payments |
GET | Transactions |
GET | Transfers |
GET | Subaccounts |
GET | Payment Plans |
GET | Chargebacks |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Payments
| Detail | Value |
|---|---|
| Operation ID | payments_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Flutterwave connection from the Connection dropdown.
- In the Operation dropdown, select
payments_0. - 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 Flutterwave API reference.
GET
Transactions
| Detail | Value |
|---|---|
| Operation ID | transactions_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Flutterwave connection from the Connection dropdown.
- In the Operation dropdown, select
transactions_1. - 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 Flutterwave API reference.
GET
Transfers
| Detail | Value |
|---|---|
| Operation ID | transfers_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Flutterwave connection from the Connection dropdown.
- In the Operation dropdown, select
transfers_2. - 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 Flutterwave API reference.
GET
Subaccounts
| Detail | Value |
|---|---|
| Operation ID | subaccounts_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Flutterwave connection from the Connection dropdown.
- In the Operation dropdown, select
subaccounts_3. - 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 Flutterwave API reference.
GET
Payment Plans
| Detail | Value |
|---|---|
| Operation ID | payment_plans_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Flutterwave connection from the Connection dropdown.
- In the Operation dropdown, select
payment_plans_4. - 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 Flutterwave API reference.
GET
Chargebacks
| Detail | Value |
|---|---|
| Operation ID | chargebacks_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Flutterwave connection from the Connection dropdown.
- In the Operation dropdown, select
chargebacks_5. - 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 Flutterwave API reference.