ActionKustomerUpdated September 2026

How do I send a Kustomer message?

Short answer: You can send kustomer message in Kustomer by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Kustomer Send Kustomer Message 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.

Send Kustomer Message in Kustomer — start free All 4 Kustomer actions

Send Kustomer Message 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
Conversation ID conversation_id	string	Required	–
Channel channel	string	Optional	–
Body body	string	Required	Message body content. Plain text unless the API specifies HTML/markdown.
Direction direction	options	Optional	–

Sample request

{
  "conversation_id": "{{trigger.conversation_id}}",
  "channel": "{{trigger.channel}}",
  "body": "e.g. Hi there, thanks for reaching out.",
  "direction": "{{trigger.direction}}"
}

Returns

{
  "data": {
    "id": "msg_abc",
    "attributes": {
      "body": "Hi",
      "direction": "out"
    }
  }
}

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

Triggered by

Apps that pair well as the trigger for Send Kustomer Message.

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 Send Kustomer Message.

What does the Send Kustomer Message action do in Kustomer?

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.

What inputs does Send Kustomer Message require?

Required: Conversation ID, Body. 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 Send Kustomer Message support batch operations?

Run Send Kustomer Message 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 Conversation

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.

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

Search Kustomer Customers

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

Send Kustomer Message in Kustomer — start free