Intercom: Update Data Attribute

Update an Intercom data attribute’s description, archive it, or change whether Messenger can write it.

Tool ID: intercom_update_data_attribute

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'intercom_update_data_attribute',
  {
    "data_attribute_id": 123
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute intercom_update_data_attribute --input '{
  "data_attribute_id": 123
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "type": "data_attribute",
    "id": 123,
    "model": "contact"
  }
}

Use deepline describe intercom_update_data_attribute --json for the latest machine-readable contract.

Input reference

You can update a data attribute. > 🚧 Updating the data type is not possible > > It is currently a dangerous action to execute changing a data attribute’s type via the API. You will need to update the type via the UI instead.

Name	Type	Required	Default	Details
`payload.data_attribute_id`	`integer`	Yes	—	The data attribute id
`payload.archived`	`boolean`	No	—	Whether the attribute is to be archived or not.
`payload.description`	`string`	No	—	The readable description you see in the UI for the attribute.
`payload.messenger_writable`	`boolean`	No	—	Can this attribute be updated by the Messenger

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Data Attributes are metadata used to describe your contact, company and conversation models. These include standard and custom attributes. By using the data attributes endpoint, you can get the global list of attributes for your workspace, as well as create and archive custom attributes.
`result.data.type`	`"data_attribute"`	No	—	Value is `data_attribute`. Allowed: `data_attribute`.
`result.data.id`	`integer`	No	—	The unique identifier for the data attribute which is given by Intercom. Only available for custom attributes.
`result.data.model`	`"contact" \| "company"`	No	—	Value is `contact` for user/lead attributes and `company` for company attributes. Allowed: `contact`, `company`.
`result.data.name`	`string`	No	—	Name of the attribute.
`result.data.full_name`	`string`	No	—	Full name of the attribute. Should match the name unless it’s a nested attribute. We can split full_name on `.` to access nested user object values.
`result.data.label`	`string`	No	—	Readable name of the attribute (i.e. name you see in the UI)
`result.data.description`	`string`	No	—	Readable description of the attribute.
`result.data.data_type`	`"string" \| "integer" \| "float" \| "boolean" \| "date"`	No	—	The data type of the attribute. Allowed: `string`, `integer`, `float`, `boolean`, `date`.
`result.data.options`	`array`	No	—	List of predefined options for attribute value.
`result.data.api_writable`	`boolean`	No	—	Can this attribute be updated through API
`result.data.messenger_writable`	`boolean`	No	—	Can this attribute be updated by the Messenger
`result.data.ui_writable`	`boolean`	No	—	Can this attribute be updated in the UI
`result.data.custom`	`boolean`	No	—	Set to true if this is a CDA
`result.data.archived`	`boolean`	No	—	Is this attribute archived. (Only applicable to CDAs)
`result.data.created_at`	`integer`	No	—	The time the attribute was created as a UTC Unix timestamp Format: `date-time`.
`result.data.updated_at`	`integer`	No	—	The time the attribute was last updated as a UTC Unix timestamp Format: `date-time`.
`result.data.admin_id`	`string`	No	—	Teammate who created the attribute. Only applicable to CDAs
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation