Approval-gated Freshdesk reply workflow. It reads the target ticket and conversation history for context, then adds exactly one public reply or private note through recued-core.freshdesk and can optionally update the ticket status after the note/reply. It does not create tickets, delete, bulk update, attach files, mutate contacts or companies, change automations/admin settings, or call arbitrary Freshdesk endpoints.

How it works 13 steps

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

Process (13 steps)

■ body_text trim

Trim whitespace from setting body text

■ has_body compare

Check if body text has data

■ has_status compare

Check if setting status is greater than 0

■ ticket ?

■ conversations ?

■ skip_public_reply any

Check if any of the conditions are true

■ skip_private_note any

Check if any of the conditions are true

■ public_reply ?

skip: step.skip_public_reply equal true

■ private_note ?

skip: step.skip_private_note equal true

■ status_update ?

skip: step.has_status not_equal true

■ created_conversation ternary

Apply ternary

■ skipped compare

Check if has body does not equal true

■ card to_summary

Format results as a summary card

Settings 5 configurable

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

status setting = 0

body text setting =

freshdesk setting =

ticket id setting =

public reply setting = true