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.
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 | – |
{"conversation_id": "{{trigger.conversation_id}}","channel": "{{trigger.channel}}","body": "e.g. Hi there, thanks for reaching out.","direction": "{{trigger.direction}}"}
{"data": {"id": "msg_abc","attributes": {"body": "Hi","direction": "out"}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.