ActionPlaidUpdated September 2026

How do I get bank transactions via Plaid?

Short answer: You can get plaid transactions in Plaid by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Plaid Get Plaid Transactions action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Plaid Transactions in Plaid — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Access Token
access_token
stringRequired
Start Date (YYYY-MM-DD)
start_date
stringRequired
End Date (YYYY-MM-DD)
end_date
stringRequired
Count
count
stringOptional
Sample request
{
"access_token": "{{trigger.access_token}}",
"start_date": "{{trigger.start_date}}",
"end_date": "{{trigger.end_date}}",
"count": "{{trigger.count}}"
}
Returns
{
"transactions": [
{
"date": "2026-05-10",
"name": "Coffee Shop",
"amount": 50,
"category": [
"Food and Drink",
"Coffee Shop"
],
"account_id": "acc_abc",
"transaction_id": "txn_abc"
}
],
"total_transactions": 1
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Plaid Transactions.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Get Plaid Transactions.

What does the Get Plaid Transactions action do in Plaid?
Returns paginated transactions with category enrichment (Plaid auto-classifies into Food, Travel, etc.). For PFM apps, expense-tracking workflows, business-banking reconciliation.
What inputs does Get Plaid Transactions require?
Required: Access Token, Start Date (YYYY-MM-DD), End Date (YYYY-MM-DD). Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Plaid returns an error?
The run history shows the failed step with its input and the error message Plaid returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Plaid Transactions support batch operations?
Run Get Plaid Transactions inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Plaid's rate limits.
More actions

Other Plaid actions.

Get Plaid Transactions in Plaid — start free