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_create_ticket:{"ticket_type_id":"{{ticket_type_id}}","contacts":"{{contacts}}"}' --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 ID of the type of ticket you want to create | |
payload.contacts | array | Yes | The list of contacts (users or leads) affected by this ticket. Currently only one is allowed | |
payload.conversation_to_link_id | string | No | The ID of the conversation you want to link to the ticket. Here are the valid ways of linking two tickets: - conversation | back-office ticket - customer tickets | non-shared back-office ticket - conversation | tracker ticket - customer ticket | tracker ticket | |
payload.company_id | string | No | The ID of the company that the ticket is associated with. The unique identifier for the company which is given by Intercom | |
payload.created_at | integer | No | The time the ticket was created. If not provided, the current time will be used. | |
payload.ticket_attributes | record | No | The attributes set on the ticket. When setting the default title and description attributes, the attribute keys that should be used are _default_title_ and _default_description_. When setting ticket type attributes of the list attribute type, the key should be the attribute name and the value of the attribute should be the list item id, obtainable by listing the ticket type. For example, if the ticket type has an attribute called priority of type list, the key should be priority and the value of the attribute should be the guid of the list item (e.g. de1825a0-0164-4070-8ca6-13e22462fa7e). | |
payload.assignment | object | No |
Output Schema
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
result.data | object | Yes | Tickets are how you track requests from your users. | |
result.meta | object | No | Additional response metadata (status, paging). |
Advanced: Direct CLI
Use direct execution for single payload debugging.
deepline tools execute intercom_create_ticket --payload '{
"ticket_type_id": "string",
"contacts": "array"
}' --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.