Skip to content

HighLevel: Create Custom Field — custom Fields create Custom Field

HighLevel customFields.createCustomField: arguments, response, policy and SDK examples.

← Custom fields operations · Get started

Operation gohighlevel.custom_fields_create_custom_field

Provider route: POST /custom-fields/. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/gohighlevel with npm, or alter-sdk-gohighlevel with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { HighLevelIntegration } from "@alter-ai/gohighlevel";
async function execute(input: Parameters<HighLevelIntegration["customFields"]["createCustomField"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new HighLevelIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.customFields.createCustomField(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_gohighlevel import HighLevelIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = HighLevelIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.custom_fields.create_custom_field(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
bodyModelRequired within parentExpand Create Custom Field — custom Fields create Custom Field — request body — body

Referenced models: Create Custom Field — custom Fields create Custom Field — request body — body

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Update Custom Field By Id — response body

Referenced models: Update Custom Field By Id — response body

Create Custom Field — custom Fields create Custom Field — request body — body
FieldTypePresenceDescription and constraints
$objectRoot
acceptedFormatsstringOptionalAllowed file formats for uploads. Options include: .pdf, .docx, .doc, .jpg, .jpeg, .png, .gif, .csv, .xlsx, .xls, all
One of: .pdf, .docx, .doc, .jpg, .jpeg, .png, .gif, .csv, .xlsx, .xls, all
allowCustomOptionbooleanOptionalDetermines if users can add a custom option value different from the predefined options in records for RADIO type fields. A custom value added in one record does not automatically become an option and will not appear as an option for other records.
dataTypestringRequired within parentType of field that you are trying to create
One of: TEXT, LARGE_TEXT, NUMERICAL, PHONE, MONETORY, CHECKBOX, SINGLE_OPTIONS, MULTIPLE_OPTIONS, DATE, TEXTBOX_LIST, FILE_UPLOAD, RADIO, EMAIL
descriptionstringOptionalDescription of the field
fieldKeystringRequired within parentField key. For Custom Object it's formatted as "custom_object.{objectKey}.{fieldKey}". "custom_object" is a fixed prefix, "{objectKey}" is your custom object's identifier, and "{fieldKey}" is the unique field name within that object. Example: "custom_object.pet.name" for a "name" field in a "pet" custom object.
locationIdstringRequired within parentLocation Id
maxFileLimitnumberOptionalMaximum file limit for uploads. Applicable only for fields with a data type of FILE_UPLOAD.
namestringOptionalField name
objectKeystringRequired within parentThe key for your custom object. This key uniquely identifies the custom object. Example: "custom_object.pet" for a custom object related to pets.
optionsarrayOptionalOptions for the field (Optional, valid only for SINGLE_OPTIONS, MULTIPLE_OPTIONS, RADIO, CHECKBOX, TEXTBOX_LIST type)
options[]ModelEach itemExpand Update Custom Field By Id — request body — body options item
parentIdstringRequired within parentID of the parent folder
placeholderstringOptionalPlaceholder text for the field
showInFormsbooleanRequired within parentWhether the field should be shown in forms

Referenced models: Update Custom Field By Id — request body — body options item

Update Custom Field By Id — response body
FieldTypePresenceDescription and constraints
$objectRoot
fieldModelOptionalExpand Update Custom Field By Id — response body — field

Referenced models: Update Custom Field By Id — response body — field

Update Custom Field By Id — request body — body options item
FieldTypePresenceDescription and constraints
$objectRoot
keystringRequired within parentKey of the option (Included in Create and Response, excluded in Update)
labelstringRequired within parentValue of the option
urlstringOptionalURL associated with the option (Optional, valid only for RADIO type)
Update Custom Field By Id — response body — field
FieldTypePresenceDescription and constraints
$objectRoot
acceptedFormatsstringOptionalAllowed file formats for uploads. Options include: .pdf, .docx, .doc, .jpg, .jpeg, .png, .gif, .csv, .xlsx, .xls, all
Known values: .pdf, .docx, .doc, .jpg, .jpeg, .png, .gif, .csv, .xlsx, .xls, all
allowCustomOptionbooleanOptionalDetermines if users can add a custom option value different from the predefined options in records for RADIO type fields. A custom value added in one record does not automatically become an option and will not appear as an option for other records.
dataTypestringRequired within parentType of field that you are trying to create
Known values: TEXT, LARGE_TEXT, NUMERICAL, PHONE, MONETORY, CHECKBOX, SINGLE_OPTIONS, MULTIPLE_OPTIONS, DATE, TEXTBOX_LIST, FILE_UPLOAD, RADIO
dateAddedstringRequired within parentDate and time when the object was added
Format: date-time
dateUpdatedstringRequired within parentDate and time when the object was last updated
Format: date-time
descriptionstringOptionalDescription of the field
fieldKeystringRequired within parentField key. For Custom Object it's formatted as "custom_object.{objectKey}.{fieldKey}". "custom_object" is a fixed prefix, "{objectKey}" is your custom object's identifier, and "{fieldName}" is the unique field name within that object. Example: "custom_object.pet.name" for a "name" field in a "pet" custom object.
idstringRequired within parentUnique identifier of the object
locationIdstringRequired within parentLocation Id
maxFileLimitJSONOptional
maxFileLimit (anyOf 1)numberAlternativeMaximum file limit for uploads
maxFileLimit (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
namestringOptionalField name
objectKeystringRequired within parentThe key for your custom / standard object. This key uniquely identifies the custom object. Example: "custom_object.pet" for a custom object related to pets.
optionsarrayOptionalOptions for the field (Optional, valid only for SINGLE_OPTIONS, MULTIPLE_OPTIONS, RADIO, CHECKBOX, TEXTBOX_LIST type)
options[]ModelEach itemExpand Update Custom Field By Id — request body — body options item
parentIdstringRequired within parentID of the parent folder
placeholderstringOptionalPlaceholder text for the field
showInFormsbooleanRequired within parentWhether the field should be shown in forms

Referenced models: Update Custom Field By Id — request body — body options item

SDK function policy ID: gohighlevel.custom_fields_create_custom_field. Catalog operation: custom-fields.create-custom-field. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Required provider scopes: ["locations/customFields.write"]

Pinned headers: {"Version": "v3"}

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.