Actions89
- General Actions
- About API Actions
- Accounts API Actions
- Available Budgets API Actions
- Bills API Actions
- Budgets API Actions
- Transactions API Actions
- Categories API Actions
- Tags API Actions
- Rules & Groups API Actions
- Piggy Banks API Actions
- Object Groups API Actions
- Recurrences API Actions
Transactions API → Create Transaction
AI-generatedOverview
This node operation creates one or more financial transactions in the FireFly III system using the Transactions API. It is useful for automating the entry of transaction data such as withdrawals, deposits, transfers, and reconciliations into FireFly III. For example, it can be used to batch import transactions from external sources or to programmatically add transactions based on other workflow events.
Use Case Examples
- Creating a withdrawal transaction with specified date, amount, and description.
- Creating multiple transactions at once with detailed fields including currency, category, source and destination accounts, tags, and notes.
Properties
| Name | Meaning |
|---|---|
| X-Trace-ID | A unique UUID identifier for the request, used for debugging and tracing. |
| Transactions Call Settings | Settings that control transaction creation behavior such as error on duplicate hash, applying rules, firing webhooks, and group title for split transactions. |
| Transaction(s) | The details of the transaction(s) to create. Required fields include Type, Date, Amount, and Description. Additional optional fields allow specifying currency, accounts, categories, tags, notes, references, and more. |
Output
JSON
json- The response from the FireFly III API containing details of the created transaction(s).
Dependencies
- FireFly III API with OAuth2 authentication
Troubleshooting
- Ensure required fields (Type, Date, Amount, Description) are provided for each transaction to avoid validation errors.
- If a duplicate transaction hash error occurs, check the 'Error If Duplicate Hash' setting or adjust transaction data to avoid duplicates.
- Verify that account IDs and currency codes are valid and exist in FireFly III to prevent API errors.
- Use the X-Trace-ID for debugging and tracing requests if issues arise.
Links
- FireFly III API Documentation - Create Transaction - Official API documentation for creating transactions in FireFly III.