Actions15
Overview
This node integrates with the YNAB (You Need A Budget) API to retrieve detailed information about a specific transaction within a budget. It is useful for scenarios where you need to fetch data about a particular financial transaction, such as reviewing or processing individual expenses or income entries programmatically.
Practical examples include:
- Automatically retrieving transaction details for reconciliation or reporting.
- Fetching transaction data to trigger further workflows based on specific transaction attributes.
- Integrating YNAB transaction data into other financial tools or dashboards.
Properties
| Name | Meaning |
|---|---|
| Budget ID | The unique identifier of the budget that contains the transaction. |
| Transaction ID | The unique identifier of the transaction to retrieve within the specified budget. |
Output
The node outputs a JSON object representing the requested transaction's details. The structure corresponds to the YNAB API's transaction object and includes fields such as transaction date, amount, payee name, memo, cleared status, account ID, and other relevant transaction metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the YNAB API.
- The node makes HTTP GET requests to the YNAB API endpoint:
https://api.ynab.com/v1/budgets/{budgetId}/transactions/{transactionId}. - Proper configuration of the API key credential in n8n is necessary for successful authentication.
Troubleshooting
Common Issues:
- Invalid or missing Budget ID or Transaction ID parameters will cause the request to fail.
- Incorrect or expired API key credentials will result in authentication errors.
- Network connectivity issues can prevent communication with the YNAB API.
Error Messages:
- 401 Unauthorized: Indicates invalid or missing API authentication token. Verify the API key credential setup.
- 404 Not Found: The specified budget or transaction ID does not exist. Confirm the IDs are correct.
- 400 Bad Request: Parameters may be malformed or missing. Ensure all required fields are provided and correctly formatted.
Resolving these typically involves verifying input parameters, checking API key validity, and ensuring network access to the YNAB API.