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 within an account in an external system. Custom fields are user-defined data points that can be added to records to capture additional information not covered by default fields. This operation is useful when you want to extend the data model dynamically, for example, adding a "Customer Loyalty Level" or "Preferred Contact Time" field to customer profiles.
Practical examples:
- Adding a required "Membership ID" custom field to track loyalty program members.
- Creating a date-type custom field to record important dates like contract renewal.
- Defining a dynamic list custom field to allow selection from options fetched at runtime.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account where the custom field will be created. |
| Label | The display label/name of the custom field. |
| Is Required | Boolean flag indicating if this custom field must always have a value (true/false). |
| Description | A textual description explaining the purpose or usage of the custom field. |
| External Id | Unique identifier of the custom field in the external system, used for integration purposes. |
| External Source | Unique identifier of the external system where this custom field originates. |
| Type | The type of the custom field. Options include: |
| - Dynamic List: Options are fetched dynamically. | |
| - Predefined List: Options are fixed and predefined. | |
| - Free Text Input: Allows arbitrary text input. | |
| - Date: Field accepts date values. |
Output
The node outputs JSON data representing the newly created custom field object as returned by the external API. This typically includes all properties of the custom field such as its unique ID, label, type, whether it is required, description, and any external identifiers.
If the node supports binary data output, it would represent associated files or attachments related to the custom field, but based on the provided code and properties, this node focuses on JSON data only.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to connect to the external system's API.
- The node uses a base URL and headers preset for JSON communication with the external service.
- Depends on the external system supporting custom field creation via its API.
Troubleshooting
- Missing Required Fields: If "Account Id" or "Label" is not provided, the API call will likely fail. Ensure these mandatory inputs are set.
- Invalid Field Type: Selecting an unsupported type may cause errors. Use one of the defined types: dynamic_list, predefined_list, free_text_input, or date.
- Authentication Errors: If the API key or credentials are invalid or missing, the request will be rejected. Verify credentials configuration.
- API Endpoint Issues: Network problems or incorrect base URL settings can cause connection failures. Confirm the endpoint URL and network access.
- Duplicate External Ids: Using an externalId already present in the system might cause conflicts. Use unique identifiers.
Links and References
- Custom Fields Concept Documentation (replace with actual relevant link)
- External System API Reference for Custom Fields (replace with actual relevant link)