Actions45
- General Actions
- About API Actions
- Accounts API Actions
- Transactions API Actions
- Categories API Actions
- Tags API Actions
- Rules & Groups API Actions
Overview
The "Update Transaction" operation in the Transactions API node allows users to modify existing financial transactions within the FireFly III system. This includes updating details such as transaction type, date, amount, accounts involved, categories, tags, and other metadata. It supports updating single or multiple transactions at once, including complex transactions with splits.
This operation is beneficial for automating bookkeeping workflows where transaction data needs correction or enrichment after initial entry. For example, you might update a transaction's category or add notes based on external data sources, or adjust amounts and accounts after reconciliation.
Practical examples:
- Correcting the amount or date of a previously recorded withdrawal.
- Adding tags or notes to transactions imported from bank statements.
- Updating split transactions by specifying individual split entries.
- Applying rules or triggering webhooks automatically when transactions are updated.
Properties
| Name | Meaning |
|---|---|
| X-Trace-ID | A unique UUID identifier for the request, used for debugging and tracing. Example: 123e4567-e89b-12d3-a456-426614174000. |
| Transaction ID | The unique identifier of the transaction to update. This is required. |
| Transactions Call Settings | Collection of options controlling how the update behaves: • Error If Duplicate Hash: Whether to throw an error if a duplicate hash is detected (true/false). • Apply Rules: Whether to apply rules to the transaction (true/false). • Fire Webhooks: Whether to trigger webhooks for the transaction (true/false). • Group Title: Title of the transaction if it has been split into multiple parts; empty otherwise. |
| Transaction(s) | One or more transactions to update, each with detailed fields: • Tsx Journal ID (if Update): ID of the transaction journal for split transactions (do not use when creating new). • Type: Type of transaction — Withdrawal, Deposit, Transfer, Reconciliation, Opening Balance. • Date: Date of the transaction (YYYY-MM-DD or ISO 8601). • Amount: Amount of the transaction. • Description: Description text. • Order: Order index for this entry. • Currency ID / Code: Currency identifiers. • Foreign Amount / Currency: Amount and currency info if foreign. • Budget ID: Associated budget. • Category ID / Name: Category info; name creates category if unknown. • Source Account ID / Name: Source account details. • Destination Account ID / Name: Destination account details. • Reconciled: Boolean indicating if reconciled. • Piggy Bank ID / Name: Optional piggy bank association. • Bill ID / Name: Optional bill association. • Tags: Comma-separated tags. • Notes: Additional notes. • Internal Reference: Internal system reference. • External ID: External system reference. • External URL: Custom external URL for the transaction. |
Output
The output JSON contains the response from the FireFly III API after updating the transaction(s). Typically, this will include the updated transaction data structure reflecting all changes made.
If multiple transactions were updated, the output will contain an array of updated transaction objects.
No binary data output is produced by this operation.
Dependencies
- Requires an authenticated connection to the FireFly III API using OAuth2 or another supported authentication method.
- The node depends on the FireFly III API being accessible and properly configured.
- No additional environment variables beyond standard API credentials are needed.
Troubleshooting
- Invalid Transaction ID: If the provided transaction ID does not exist, the API will return an error. Verify the ID before updating.
- Duplicate Hash Error: If "Error If Duplicate Hash" is enabled and a duplicate transaction hash is detected, the API will reject the update. Disable this option or ensure uniqueness.
- Missing Required Fields: Some fields like transaction type or amount may be required depending on the context. Ensure all necessary fields are provided.
- Foreign Currency Issues: When specifying foreign amounts, either the foreign currency ID or code must be provided. Omitting these leads to errors.
- Account Type Mismatch: Source and destination accounts must match expected types for the transaction type (e.g., source must be asset for withdrawals). Incorrect types cause validation errors.
- API Rate Limits or Connectivity: Network issues or API rate limits can cause failures. Check connectivity and API usage quotas.