Appearance
Paystack
undefined
| Detail | Value |
|---|---|
| Category | Finance |
| Base URL | https://api.paystack.co |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | paystack |
Using Paystack in a workflow
- Go to Connections and click New Connection.
- Pick Paystack 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 | Transactions |
GET | Customers |
GET | Refunds |
GET | Transfers |
GET | Plans |
GET | Subscriptions |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Transactions
| Detail | Value |
|---|---|
| Operation ID | transactions_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Paystack connection from the Connection dropdown.
- In the Operation dropdown, select
transactions_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 Paystack API reference.
GET
Customers
| Detail | Value |
|---|---|
| Operation ID | customers_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Paystack connection from the Connection dropdown.
- In the Operation dropdown, select
customers_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 Paystack API reference.
GET
Refunds
| Detail | Value |
|---|---|
| Operation ID | refunds_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Paystack connection from the Connection dropdown.
- In the Operation dropdown, select
refunds_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 Paystack API reference.
GET
Transfers
| Detail | Value |
|---|---|
| Operation ID | transfers_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Paystack connection from the Connection dropdown.
- In the Operation dropdown, select
transfers_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 Paystack API reference.
GET
Plans
| Detail | Value |
|---|---|
| Operation ID | plans_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Paystack connection from the Connection dropdown.
- In the Operation dropdown, select
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 Paystack API reference.
GET
Subscriptions
| Detail | Value |
|---|---|
| Operation ID | subscriptions_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Paystack connection from the Connection dropdown.
- In the Operation dropdown, select
subscriptions_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 Paystack API reference.