Short answer: Drop the "Front → Update Front Conversation" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | — |
{"conversation_id": "{{trigger.conversation_id}}","assignee_id": "{{trigger.assignee_id}}","status": "{{trigger.status}}","tag_ids": "{{trigger.tag_ids}}"}
{"id": "cnv_abc","status": "archived"}
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.
Triggered by anything in the catalog. Free tier available. No credit card.