Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation retrieves a specific expense category by its unique identifier within a given account. It is useful in scenarios where you need to fetch detailed information about a particular expense category, for example, to display its details in a dashboard, validate category data before processing transactions, or synchronize category information with other systems.
Practical examples:
- Fetching the details of an expense category to show its name and description in a financial report.
- Validating that an expense category exists before assigning expenses to it.
- Integrating with accounting software to update or verify expense categories.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the expense category belongs. |
| Category Id | Identifier of the specific expense category to retrieve. |
Output
The output contains a JSON object representing the expense category identified by the provided Category Id within the specified Account Id. This JSON typically includes fields such as the category's name, description, ID, and possibly metadata related to the category.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the expense category, but this operation primarily returns structured JSON data.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to access the external service managing expense categories.
- The node depends on a REST API endpoint that provides expense category data based on account and category identifiers.
- Proper base URL configuration for the API is necessary, typically set via credentials or environment variables.
Troubleshooting
Common issues:
- Invalid or missing Account Id or Category Id will result in errors or empty responses.
- Authentication failures due to incorrect or expired API keys.
- Network connectivity problems preventing access to the external API.
- The specified category might not exist, leading to "not found" errors.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Verify that the API key or authentication token is correctly configured and valid.
- "Category not found": Confirm that the Category Id is correct and exists under the specified Account Id.
- "Network error": Check internet connection and API endpoint availability.
- "Missing required parameters": Ensure both Account Id and Category Id are provided and non-empty.
Links and References
- Refer to the external API documentation for expense categories to understand the full schema and available fields.
- n8n documentation on how to configure API credentials and use HTTP request nodes for custom integrations.