ActionKustomerUpdated June 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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Kustomer Conversation support batch operations?

Yes. Run Create Kustomer Conversation inside a Loop node to process arrays. TinyCommand handles Kustomer's rate limits automatically so you don't have to throttle manually.

How do I create a Kustomer conversation?

The fields this action accepts.

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

Questions about Create Kustomer Conversation.

Other Kustomer actions.