Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts 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 custom fields associated with a specific account. It is useful when you need to fetch metadata or additional configurable data tied to an account in your system. For example, if you manage customer accounts and have custom attributes defined for each, this operation allows you to programmatically access those custom attributes for reporting, integration, or automation purposes.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account whose custom fields you want to retrieve |
Output
The output JSON contains the custom fields data related to the specified account. This typically includes key-value pairs or structured objects representing each custom field's name, value, and possibly metadata about the field. The exact structure depends on the API response but generally provides all custom attributes configured for that account.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests.
- Depends on connectivity to the external service managing accounts and their custom fields.
- The base URL for API requests must be set in the node credentials or environment variables.
Troubleshooting
- Missing or invalid Account Id: Ensure the "Account Id" property is provided and correctly matches an existing account; otherwise, the API may return errors or empty results.
- Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to read custom fields.
- Network issues: Check network connectivity and endpoint availability if requests time out or fail.
- Unexpected response format: If the output does not contain expected custom fields, confirm that the account actually has custom fields defined and that the API version matches the node’s expectations.
Links and References
- Refer to the external API documentation for details on the custom fields endpoint and its response schema.
- Consult n8n documentation on how to configure API credentials and handle HTTP request nodes for further customization.