Skip to content
Recued
Menu
← Back to recipes

Update a Front conversation status

by recued-core v1

Approval-gated Front conversation status workflow. It reads the target conversation for context, updates exactly one conversation status through recued-core.front.conversation.update, and can add one internal note when note text is present. It does not send a customer reply, delete data, upload attachments, create tags, alter rules, mutate inbox settings, or call arbitrary Front API routes.

How it works 6 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (6 steps)
note trim
Trim whitespace from setting note
has_note compare
Check if note has data
conversation ?
updated_conversation ?
note_comment ?
skip: step.has_note not_equal true
card to_summary
Format results as a summary card
Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

note setting =
front setting =
status setting = archived
conversation id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Front connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

front frontconversationstatustriageapprovalcustomer-servicepack:front

Details

6 steps 4 configurable settings recipe_id: update-front-conversation-status