ActionFrontUpdated September 2026
How do I update a Front conversation?
Short answer: You can update front conversation in Front by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Front Update 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.
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 | 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. |
Assignee Teammate ID assignee_id | string | Optional | – |
Status status | options | Optional | – |
Tag IDs tag_ids | array | Optional | – |
Sample request
{"conversation_id": "{{trigger.conversation_id}}","assignee_id": "{{trigger.assignee_id}}","status": "{{trigger.status}}","tag_ids": "{{trigger.tag_ids}}"}
Returns
{"id": "cnv_abc","status": "archived"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Update Front Conversation.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Update Front Conversation.
What does the Update Front Conversation action do in Front?
Changes conversation state — status, assignee, inbox, tags. For "auto-route by content category" workflows or for "auto-close idle conversations" maintenance.
What inputs does Update Front Conversation require?
Required: Conversation ID. 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 Front returns an error?
The run history shows the failed step with its input and the error message Front 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 Update Front Conversation support batch operations?
Run Update Front Conversation 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 Front's rate limits.
More actions
Other Front actions.
Action
Add Front Internal Comment
Posts an internal team note on a conversation thread — visible to teammates only, not the customer. For "AI-summarised CRM context → log as internal note before the agent replies" workflows.
ActionReply to Front Conversation
Posts a customer-facing reply via the conversation's original channel (email, SMS, social DM). For "approved auto-response from a Slack thumbs-up → reply to the customer" patterns.