Approval-gated Front customer reply workflow. It reads the target conversation for context, then sends exactly one reply through recued-core.front.conversation.reply when reply text is present. It does not delete messages, upload attachments, change conversation status, assign teammates, mutate contacts, create tags, 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)

■ body trim

Trim whitespace from setting body

■ has_body compare

Check if body has data

■ conversation ?

■ reply ?

skip: step.has_body not_equal true

■ skipped compare

Check if has body does not equal true

■ card to_summary

Format results as a summary card

Settings 3 configurable

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

body setting =

front setting =

conversation id setting =