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.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Access Token access_token | string | Required | – |
Start Date (YYYY-MM-DD) start_date | string | Required | – |
End Date (YYYY-MM-DD) end_date | string | Required | – |
Count count | string | Optional | – |
{"access_token": "{{trigger.access_token}}","start_date": "{{trigger.start_date}}","end_date": "{{trigger.end_date}}","count": "{{trigger.count}}"}
{"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.
Any of these apps can fire this action as part of a workflow.