Run in Enrichment Spreadsheet
Use this function as a column step in
deepline enrich.deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=intercom_update_ticket_type_attribute:{"ticket_type_id":"{{ticket_type_id}}","attribute_id":"{{attribute_id}}"}' --json
Map payload values to spreadsheet columns with
{{column_name}} placeholders.Input Schema
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
payload.ticket_type_id | string | Yes | The unique identifier for the ticket type which is given by Intercom. | |
payload.attribute_id | string | Yes | The unique identifier for the ticket type attribute which is given by Intercom. | |
payload.name | string | No | The name of the ticket type attribute | |
payload.description | string | No | The description of the attribute presented to the teammate or contact | |
payload.required_to_create | boolean | No | false | Whether the attribute is required to be filled in when teammates are creating the ticket in Inbox. |
payload.required_to_create_for_contacts | boolean | No | false | Whether the attribute is required to be filled in when contacts are creating the ticket in Messenger. |
payload.visible_on_create | boolean | No | true | Whether the attribute is visible to teammates when creating a ticket in Inbox. |
payload.visible_to_contacts | boolean | No | true | Whether the attribute is visible to contacts when creating a ticket in Messenger. |
payload.multiline | boolean | No | Whether the attribute allows multiple lines of text (only applicable to string attributes) | |
payload.list_items | string | No | A comma delimited list of items for the attribute value (only applicable to list attributes) | |
payload.allow_multiple_values | boolean | No | Whether the attribute allows multiple files to be attached to it (only applicable to file attributes) | |
payload.archived | boolean | No | Whether the attribute should be archived and not shown during creation of the ticket (it will still be present on previously created tickets) |
Output Schema
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
result.data | object | Yes | Ticket type attribute, used to define each data field to be captured in a ticket. | |
result.meta | object | No | Additional response metadata (status, paging). |
Advanced: Direct CLI
Use direct execution for single payload debugging.
deepline tools execute intercom_update_ticket_type_attribute --payload '{
"ticket_type_id": "string",
"attribute_id": "string"
}' --json
CLI flags
| Flag | Description |
|---|---|
--json | Print machine-readable output. |
--wait | Wait for terminal provider status when supported. |
--debug | Enable wait mode with additional status/log output. |
--wait-timeout SECONDS | Max seconds to wait in wait mode. |
--poll-interval SECONDS | Polling interval in seconds during wait mode. |
--timeout SECONDS | Request timeout in seconds. |
--connect-timeout SECONDS | Connection timeout in seconds. |
Cost
- Pricing model:
fixed(per call). - Estimated Deepline credits:
0per pricing unit. - Provider-native pricing may still exist outside Deepline credit billing.
- Billing mode:
no_bill.