Actions15
Overview
This node integrates with the YNAB (You Need A Budget) API to create a new transaction within a specified budget. It is useful for automating the addition of financial transactions into your budgeting system, enabling seamless synchronization between external data sources or workflows and your YNAB account.
Common scenarios include:
- Automatically logging expenses or income from other financial tools.
- Importing transaction data from bank exports or other accounting software.
- Creating transactions based on triggers such as invoice payments or sales.
For example, you could use this node to add a transaction representing a recent purchase by specifying the budget, account, date, amount, payee, memo, and cleared status.
Properties
| Name | Meaning |
|---|---|
| Budget ID | The ID of the budget where the transaction will be created. |
| Account ID | The ID of the account associated with the transaction. |
| Date | The transaction date in ISO format (YYYY-MM-DD). |
| Amount | The transaction amount in milliunits format (e.g., $10.00 is represented as 10000). |
| Payee Name | The name of the payee involved in the transaction (optional). |
| Memo | Additional notes or description for the transaction (optional). |
| Cleared | The cleared status of the transaction. Options: Cleared, Uncleared, Reconciled. Default is Uncleared. |
Output
The node outputs a JSON object representing the newly created transaction as returned by the YNAB API. The structure includes details such as transaction ID, account ID, date, amount, payee name, memo, and cleared status.
No binary data output is produced by this node.
Example output snippet (simplified):
{
"transaction": {
"id": "string",
"account_id": "string",
"date": "YYYY-MM-DD",
"amount": 12345,
"payee_name": "string",
"memo": "string",
"cleared": "cleared"
}
}
Dependencies
- Requires an API key credential for authenticating with the YNAB API.
- The node uses the base URL
https://api.ynab.com/v1. - Proper configuration of the API key credential in n8n is necessary for successful requests.
Troubleshooting
- Invalid Budget or Account ID: Ensure that the provided Budget ID and Account ID exist and are accessible with the authenticated API key.
- Incorrect Date Format: The date must be in ISO format (
YYYY-MM-DD). Invalid formats may cause request failures. - Amount Format: Amounts must be specified in milliunits (integer). For example, $10.00 should be input as 10000.
- API Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Cleared Status Values: Only "cleared", "uncleared", or "reconciled" are accepted. Using other values will result in errors.
If errors occur, check the error message returned by the API for specific details and verify all input parameters accordingly.