- Integrations
- /
- Kustomer
- /
- Actions
- /
- Create Kustomer Conversation
ActionKustomerUpdated May 2026
How do I create a Kustomer conversation?
Short answer: Drop the "Kustomer → Create Kustomer Conversation" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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. Tiny Command handles Kustomer's rate limits automatically so you don't have to throttle manually.
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.
ActionSend 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.
ActionSearch Kustomer Customers
Full-text search across customer attributes. For "find customer by email" lookups or for "all customers in this segment" queries.
Send create kustomer conversation from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.