Send Kustomer Message: Kustomer action

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.

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 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 Send Kustomer Message support batch operations?

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