Skip to main content
Helpdesk Imports

List the source's custom fields, and where each goes

After the pull: the custom fields of conversations, contacts and companies, how many records use each (used), a few example values, and where each goes (mapsTo: the choice, else the suggestion, with reason). Also your attributes a field can map to (attributes) and how many more attributes you can create (room). Change them with PATCH /v2/helpdesk_imports/{id} and fieldMapping.

GET
/v2/helpdesk_imports/{id}/fields

Suggestions skip fields of other tools, secrets, ids and rarely used fields. Fields that duplicate a Featurebase field (builtin) need nothing.

Big accounts have hundreds of fields: ask one object at a time (object=contact).

Authorizationstringheaderrequired

API key as Bearer token. Use: Authorization: Bearer sk_...

idstringrequired

The import id (from POST /v2/helpdesk_imports or GET /v2/helpdesk_imports).

Pattern: ^[a-f0-9]{24}$
Example: 6720b1c2d3e4f5a6b7c8d9e0
objectenum<string>query

Only the fields (and attributes) of conversation, contact or company. Big accounts have hundreds of fields: ask one object at a time.

Available options: conversation, contact, company
Example: contact
Featurebase-Versionenum<string>header

API version for this request. Defaults to your organization's configured API version if not specified.

Available options: 2026-08-19.orbit, 2026-01-01.nova, 2025-12-12.clover
Example: 2026-08-19.orbit

Response

application/json

Success

attributesobjectrequired

Your attributes a field can map to (kind: attribute).

countedobjectrequired

Records counted per object for used.

editablebooleanrequired

The mapping can still change (the import has not started adding data).

fieldsobjectrequired
importIdstringrequired
objectenum<string>required
Available options: helpdesk_import_fields
Example: helpdesk_import_fields
roomobjectrequired

How many more attributes the workspace can create, per object (conversationText: text conversation attributes).