Bulk Create Properties: Troubleshooting

This page covers the most common issues encountered during bulk property creation, along with their causes and solutions.

Validation Errors (Before Submission)

These errors appear in the wizard before you submit the task. They prevent submission until resolved.

Duplicate Internal Name

Error: “Duplicate internal name: property_name”

Cause: Two or more properties in your batch share the same internal name.

Solution: Each property must have a unique internal name within the batch. Rename one of the duplicates. Internal names must also be unique within the target object type in HubSpot — if a property with that name already exists in the portal, it will fail during creation (see “Property Already Exists” below).

Missing Required Fields

Error: “Internal name is required” or “Display name is required”

Cause: A property row is missing its internal name or display name.

Solution: Fill in both fields for every property. If you uploaded a CSV, check that the internalName and displayName columns are populated for all rows.

No Options Defined for Select Type

Error: “Options are required for type select”

Cause: A property with type dropdown select, radio select, or multiple checkboxes has no options defined.

Solution: Add at least one option with both a value and a label. Click the Options editor for that property row and define your choices.

Invalid Internal Name Characters

Error: “Internal name contains invalid characters”

Cause: The internal name includes spaces, uppercase letters, special characters, or starts with a number.

Solution: Use only lowercase letters, numbers, and underscores. The name must start with a letter. For example: lead_score_v2 is valid; Lead-Score is not.

API Errors (During Task Execution)

These errors appear in the Activity Log after the task has been submitted. They are returned by the HubSpot API during property creation.

Property Already Exists

Error: “Property property_name already exists on object type contact”

Cause: A property with the same internal name is already defined in the target portal for that object type.

Solution: This is not a JetStack AI error — HubSpot rejects duplicate property names. Either rename the property in your batch or remove it if the existing property is sufficient. Other properties in the batch continue to process normally; this error only affects the conflicting property.

Property Group Creation Failed

Error: “Failed to create property group group_name”

Cause: The property group could not be created in HubSpot. Common reasons include insufficient permissions, an invalid group name, or the portal reaching its group limit.

Solution: Verify that the connected portal’s OAuth token has property write permissions. Check that the group name uses valid characters. If the group already exists, JetStack AI will use it — this error typically indicates a permissions or naming issue.

Insufficient Permissions

Error: “The access token does not have the required scopes”

Cause: The OAuth connection for the target portal lacks the scopes needed to create properties.

Solution: Reconnect the portal in Settings > Connected Portals. During reconnection, ensure you approve all requested permission scopes. The required scope for property creation depends on the object type — crm.schemas.contacts.write for contacts, crm.schemas.companies.write for companies, and so on.

Rate Limit Exceeded

Error: “429 Too Many Requests” or task appears stuck in Processing

Cause: The HubSpot API rate limit was hit during property creation. This is more likely with very large batches (50+ properties) or when other JetStack AI operations are running concurrently against the same portal.

Solution: JetStack AI automatically retries rate-limited requests with backoff. In most cases, the task completes after a brief delay. If the task remains stuck for more than 10 minutes, check the Activity Log for a detailed error. You can safely re-submit the task — properties that were already created will return “already exists” errors, and the remaining properties will be created.

Invalid Property Type

Error: “Invalid property type type_name”

Cause: The property type value does not match HubSpot’s accepted type identifiers. This can happen with manual CSV uploads where the type column contains freeform text.

Solution: Use one of the supported type identifiers: string, number, date, datetime, enumeration, bool, phone_number. When using the wizard’s dropdown selector, valid types are enforced automatically. This issue only arises with CSV uploads that contain non-standard type values.

CSV Upload Issues

CSV Parse Error

Error: “Unable to parse CSV file”

Cause: The file is malformed, uses an unsupported encoding, or has mismatched column counts.

Solution: Ensure the CSV is UTF-8 encoded, uses commas as delimiters, and has a consistent number of columns per row. The header row must be present and must include at minimum internalName, displayName, and type.

Options Format Error

Error: “Invalid options format in row N”

Cause: The options column for a select-type property is not formatted correctly.

Solution: Options must be formatted as semicolon-separated value:label pairs. For example: new:New;in_progress:In Progress;closed:Closed. Do not include spaces around the separators.

Partial Success

When some properties succeed and others fail, the task status shows Partial. The task detail view lists each property individually with its result. You do not need to re-create the successful properties. To retry the failed ones, create a new batch containing only the properties that failed, with the issues corrected.

Next Steps

• How It Works — Technical overview of the creation pipeline
• Step-by-Step Guide — Walkthrough of the wizard