Paystack — recent payments
List recent successful, failed or abandoned transactions.
What it does
Lists recent payments — successful, failed or abandoned. Useful for a daily reconciliation or for spotting a run of failures that suggests something is broken at checkout.
What you need
Secret key from Paystack. Paystack → Settings → API Keys & Webhooks. The secret key, not the public one — the public key cannot read transactions.
Connecting it
Credentials belong to one project, not to your workspace and not to you. A system built for one client never runs on another client's account, and a package handed to a business runs on theirs.
- Open the project and stay on the Visual Editor tab.
- Open the Tools & Integrations rail on the right.
- Find this tool, open it, and paste the credential.
To change it later, open the same panel — you can leave the key blank to keep the stored one and change only the other field.
Using it in a step
An Action step runs one tool with the arguments you type, exactly as written, with no model involved — so it costs nothing per run and behaves the same every time. Add one from the canvas toolbar, choose Paystack — recent payments, and fill in:
| Field | Required | What goes in it |
|---|---|---|
status |
no | success, failed or abandoned. Blank for all of them. |
count |
no | How many to return. Keep it small — a summary, not an export. |
Values can carry results forward: {{previous}} is the step before, and {{row:column}}
is a column from the row this run is about when the trigger fans out.
Press Try it to run the step on its own before committing to a whole sequence.
Using it with an agent
Tick Paystack — recent payments on any agent that should be able to call it, and the agent decides when to. Use an agent when the judgement matters and an Action step when the certainty does.
A worked example
A business gets a 6pm summary: what came in today, what failed, and what was abandoned at checkout. Three numbers and a short list, emailed to the owner.
When it goes wrong
Abandoned transactions look alarming. They are normal — a customer opening checkout and leaving creates one. Watch the trend rather than the count.
See also
- Action steps — the step kind this is used in
- Sequences — how steps fit together
- Triggers — running it on a schedule

