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 allows users to create a new custom field value within an account. It is useful in scenarios where you want to extend the data model by adding additional metadata or attributes that are not part of the standard fields. For example, if you manage customer accounts and want to add a custom tag or category to each account, this operation lets you define those custom values programmatically.
Practical examples include:
- Adding a custom label to categorize accounts by region or priority.
- Creating external identifiers for integration with other systems.
- Defining custom attributes that can be used later for filtering or reporting.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the custom field value will be added. |
| Custom Field Id | Identifier of the specific custom field for which the value is being created. |
| Label | The display label or name of the custom field value. |
| External Id | A unique identifier for the custom field value in an external system (optional). |
Output
The output JSON contains the details of the newly created custom field value. This typically includes the assigned ID, label, external ID (if provided), and any metadata returned by the API confirming the creation.
If the node supports binary data output, it would represent associated files or attachments related to the custom field value, but based on the provided code and properties, this operation focuses on JSON data only.
Dependencies
- Requires an API key credential to authenticate requests against the external service managing custom fields.
- The base URL for the API must be configured in the node credentials.
- The node depends on an OpenAPI-based client library for request construction and response parsing.
Troubleshooting
- Missing Required Fields: Ensure that
Account Id,Custom Field Id, andLabelare provided; otherwise, the API will reject the request. - Authentication Errors: Verify that the API key or authentication token is correctly set up in the node credentials.
- Invalid Identifiers: Double-check that the
Account IdandCustom Field Idcorrespond to existing entities in the external system. - Network Issues: Confirm network connectivity and that the base URL is reachable.
- API Limitations: If the API enforces rate limits or quotas, handle errors accordingly and consider retry mechanisms.
Links and References
- Refer to the external API documentation for custom fields management for detailed schema and constraints.
- n8n documentation on creating and using custom nodes with OpenAPI specifications.