Plaid icon

Plaid

Access the Plaid API - No Dependencies

Actions10

Transaction → Get Range

AI-generated

Overview

This node integrates with the Plaid API to retrieve financial transaction data within a specified date range for a user’s account. It is particularly useful for applications that need to analyze or display bank transactions, such as personal finance management tools, accounting software, or expense tracking systems.

The "Get Range" operation fetches transactions between a start and end date, allowing users to specify how many transactions to return or to retrieve all available transactions in that period. This enables detailed historical transaction analysis or reporting.

Example use cases:

  • Fetching all transactions from the last month to generate a spending report.
  • Retrieving recent transactions to update a budgeting app.
  • Extracting transaction data for reconciliation in accounting workflows.

Properties

Name Meaning
Access Token The Plaid access token associated with the user's bank account, required for authentication.
Start Date The beginning date (YYYY-MM-DD) of the transaction range to retrieve.
End Date The ending date (YYYY-MM-DD) of the transaction range to retrieve.
Return All Boolean flag indicating whether to return all matching transactions or limit the results.
Limit Maximum number of transactions to return if "Return All" is false; value between 1 and 500.

Output

The output consists of individual transaction objects returned in the json field, each representing a single financial transaction retrieved from the Plaid API. Each transaction includes details such as amount, date, merchant name, category, and other metadata provided by Plaid.

If multiple transactions are returned, each is output as a separate item in the node's output array, paired with the input item it originated from.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Plaid API (client ID and secret).
  • The node uses the Plaid API endpoints corresponding to the environment configured in the credentials (sandbox, development, production).
  • No additional external dependencies beyond HTTP requests to the Plaid API.

Troubleshooting

  • Common issues:

    • Invalid or expired access tokens will cause authentication errors.
    • Date formats must be valid and in YYYY-MM-DD format; invalid dates may cause request failures.
    • Requesting too many transactions without enabling "Return All" may truncate results.
    • Network or API downtime can cause request failures.

  • Error messages:

    • Plaid API Error (error_code): error_message — Indicates a specific Plaid API error; check the error code and message for details.
    • Plaid API Request Failed: message — General failure in making the API request; verify network connectivity and credentials.

  • Resolution tips:

    • Ensure the access token is current and has permissions for transactions.
    • Validate date inputs before running the node.
    • Use "Return All" carefully to avoid large data loads.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion