Workflow origin for the Freshdesk ticket reply closure loop. It reads one ticket and its conversation context, creates exactly one owner-provided public reply through recued-core.freshdesk.ticket.reply.create, optionally updates that same ticket to a user-configured Freshdesk numeric status, and when the reply succeeds it seeds durable data.shared closure state for freshdesk-ticket-reply-closure-watcher. It uses user-configured deterministic copy rather than AI and does not create tickets, create private notes, delete, bulk update, attach files, mutate contacts or companies, change automations/dispatch rules/SLA/admin settings, or call arbitrary Freshdesk endpoints.
Reply to Freshdesk ticket with closure
Workflow origin for the Freshdesk ticket reply closure loop. It reads one ticket and its conversation context, creates exactly one owner-provided public reply through recued-core.freshdesk.ticket.reply.create, optionally updates that same ticket to a user-configured Freshdesk numeric status, and when the reply succeeds it seeds durable data.shared closure state for freshdesk-ticket-reply-closure-watcher. It uses user-configured deterministic copy rather than AI and does not create tickets, create private notes, delete, bulk update, attach files, mutate contacts or companies, change automations/dispatch rules/SLA/admin settings, or call arbitrary Freshdesk endpoints.
Complete workflow
Freshdesk Ticket Reply Closure Loop
5 pinned recipes
Workflow pack for Recued-sent Freshdesk public replies. It composes the Freshdesk capability pack with a closure ledger: send one public ticket reply through the existing Freshdesk approval gate, optionally set a configured Freshdesk numeric status such as Pending, persist only the connection/ticket reply-watch linkage in data.shared, and let a scheduled watcher re-read that exact ticket until Freshdesk reports Resolved/Closed or an owner-actionable status such as Open. This pack does not replace Freshdesk automations, dispatch rules, Observer/Supervisor rules, SLA policy, ticket views, native notifications, or helpdesk queue rules; it adds Recued-visible closure state for tickets Recued replied to.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Scheduled adopter for Freshdesk ticket reply closure rows seeded by reply-freshdesk-ticket-with-closure. It lists only Recued-originated public-reply watches, re-reads a bounded batch of ticket from Freshdesk, and closes or flags the shared row when Freshdesk reports a configured closure or owner-actionable status. It can notify the owner on closure or customer-return states, but it never updates tickets, replies to customers, creates private notes, creates or edits automations/dispatch rules/SLA/admin settings, deletes records, or calls arbitrary Freshdesk endpoints.
Read-only AI-assisted review brief for one Freshdesk ticket. It reads the ticket, full conversation list, requester contact when available, company when available, time entries, and matching solution articles through recued-core.freshdesk, then summarizes the customer ask, urgency, history, support risk, and next response. It never replies, updates, deletes, bulk-mutates, attaches files, changes automations/admin settings, or calls arbitrary Freshdesk endpoints.
Low-frequency timeout role for recued-core/freshdesk-ticket-reply-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.
Owner-visible list/close role for recued-core/freshdesk-ticket-reply-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (38 steps)
ticket_id_value
trim
Trim whitespace from setting ticket id
reply_text
trim
Trim whitespace from setting reply body
reason_text
trim
Trim whitespace from setting reason
has_reply
compare
Check if reply text has data
has_status
compare
Check if setting status after reply is greater than 0
ticket
?
conversations
?
skip_public_reply
compare
Check if has reply does not equal true
public_reply
?
skip: step.skip_public_reply equal true
created_conversation_id
default
Apply default
has_created_conversation
compare
Check if created conversation id has data
reply_ticket_id_primary
default
Apply default
replied_ticket_id
default
Apply default
has_replied_ticket
compare
Check if replied ticket id has data
skip_status_update
any
Check if any of the conditions are true
status_update
?
skip: step.skip_status_update equal true
previous_status
default
Apply default
requested_status_from_update
default
Apply default
requested_status_configured
ternary
Apply ternary
requested_status
default
Apply default
replied_at
date_add
Add 0 days to
ticket_key_seed
default
Apply default
raw_ticket_key
join
Join items with ":"
ticket_key_colon
replace
Replace text in raw ticket key
ticket_key_slash
replace
Replace text in ticket key colon
ticket_key_dot
replace
Replace text in ticket key slash
ticket_key_at
replace
Replace text in ticket key dot
ticket_key_space
replace
Replace text in ticket key at
ticket_key_left_angle
replace
Replace text in ticket key space
ticket_key_right_angle
replace
Replace text in ticket key left angle
ticket_key_plus
replace
Replace text in ticket key right angle
ticket_key_equals
replace
Replace text in ticket key plus
ticket_key_question
replace
Replace text in ticket key equals
skip_closure_seed
any
Check if any of the conditions are true
closure_timeout_at
date_add
Add setting no response timeout days days to
seed_freshdesk_reply_closure_watch
?
skip: step.skip_closure_seed equal true
skipped
compare
Check if has reply does not equal true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
reason
setting
=
freshdesk
setting
=
ticket id
setting
=
reply body
setting
=
status after reply
setting
=
3
no response timeout days
setting
=
30
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.