ActionKustomerUpdated September 2026

How do I create a Kustomer conversation?

Short answer: You can create kustomer conversation in Kustomer by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Kustomer Create Kustomer Conversation action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Kustomer Conversation in Kustomer — start free All 4 Kustomer actions

Create Kustomer Conversation in Kustomer — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Customer ID customer_id	string	Required	The Customer ID assigned by Kustomer. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Subject name	string	Required	–
Channel channel	options	Optional	–
Priority priority	options	Optional	–

Sample request

{
  "customer_id": "{{trigger.customer_id}}",
  "name": "{{trigger.name}}",
  "channel": "{{trigger.channel}}",
  "priority": "{{trigger.priority}}"
}

Returns

{
  "data": {
    "id": "cnv_abc",
    "attributes": {
      "name": "Help",
      "status": "open",
      "priority": 3
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create Kustomer Conversation.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Kustomer

2 Google Sheets triggers

HubSpot → Kustomer

18 HubSpot triggers

FAQ

Questions about Create Kustomer Conversation.

What does the Create Kustomer Conversation action do in Kustomer?

Opens a new conversation for a customer on a specified channel (email, chat, SMS). For "external support channel → file in Kustomer" or proactive-outreach workflows.

What inputs does Create Kustomer Conversation require?

Required: Customer ID, Subject. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Kustomer returns an error?

The run history shows the failed step with its input and the error message Kustomer returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Kustomer Conversation support batch operations?

Run Create Kustomer Conversation inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Kustomer's rate limits.

More actions

Other Kustomer actions.

Action

Create Kustomer Customer

Inserts a new customer with email, phone, name, custom attributes. For "new lead → push to Kustomer so they're primed when they next contact us" sync workflows.

Action

Send Kustomer Message

Posts a customer-facing message (out) or internal note. For "AI-summarised context → log as internal note" or "automated reply on routine ticket types" workflows.

Action

Search Kustomer Customers

Full-text search across customer attributes. For "find customer by email" lookups or for "all customers in this segment" queries.

Create Kustomer Conversation in Kustomer — start free