Short answer: You can reply to front conversation in Front by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Front Reply to Front 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.
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 | The Conversation ID assigned by Front. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Channel ID channel_id | string | Required | – |
Body body | string | Required | Message body content. Plain text unless the API specifies HTML/markdown. |
Archive after options_archive | options | Optional | – |
{"conversation_id": "{{trigger.conversation_id}}","channel_id": "{{trigger.channel_id}}","body": "e.g. Hi there, thanks for reaching out.","options_archive": "{{trigger.options_archive}}"}
{"id": "msg_abc","status": "succeeded"}
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.