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 the value of a specific custom field associated with an account. It is useful when you need to fetch detailed or user-defined metadata stored as custom fields in an external system, allowing workflows to dynamically access and use these values for further processing or decision-making.
Practical examples include:
- Fetching a customer-specific attribute like "Preferred Contact Method" before sending notifications.
- Retrieving a custom status or tag assigned to an entity to control workflow branching.
- Accessing additional data points that are not part of standard fields but are important for business logic.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account from which to retrieve the custom field value. |
| Custom Field Id | Identifier of the custom field whose value you want to get. |
| Custom Field Value Id | Identifier of the specific value instance of the custom field to retrieve. |
Output
The node outputs JSON data containing the details of the requested custom field value. This typically includes the value itself along with any associated metadata returned by the external API. The exact structure depends on the external service's response but generally provides all relevant information about the custom field value.
No binary data output is indicated.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to connect to the external service managing custom fields.
- The node uses a base URL and headers preset for JSON communication with the external API.
- The bundled code references an OpenAPI specification and a custom operation parser, indicating it relies on an OpenAPI-based client internally.
Troubleshooting
- Missing or invalid identifiers: Ensure that the Account Id, Custom Field Id, and Custom Field Value Id are correctly provided and correspond to existing entities in the external system.
- Authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions to read custom field values.
- Network or API errors: Check connectivity and API availability; transient errors may require retries.
- Unexpected response structure: If the output JSON does not contain expected fields, confirm that the custom field and its value exist and are accessible.
Links and References
- Refer to the external service’s API documentation for details on custom fields and their values.
- Consult n8n documentation on setting up API credentials and using HTTP request nodes for similar integrations.