Recued
Menu
← Back to recipes

Reply to Freshdesk ticket with closure

by recued-core v2 30 views

Use “Reply to Freshdesk ticket with closure” in Recued. It carries out the named workflow using the connections and settings you choose.

Complete workflow

Use Freshdesk Ticket Reply Closure Loop in Recued for support, helpdesk, closed loop, and state freshdesk ticket reply closure watcher. It includes 3 ready-to-run workflows and 1 related pack in one install.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Use “Reply to Freshdesk ticket with closure” in Recued. It carries out the named workflow using the connections and settings you choose.

freshdesksupporthelpdeskticket
by recued-core pinned v2

Use “Freshdesk ticket reply closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

freshdesksupporthelpdeskticket
by recued-core pinned v3

Use “Freshdesk ticket review brief” in Recued. It provides a read-only AI-assisted review brief for one Freshdesk ticket.

freshdesksupporthelpdeskticket
by recued-core pinned v4

Use “Freshdesk ticket reply closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

freshdeskwatchertimeoutowner-review
by recued-core pinned v2
View pack details, dependencies, and permissions →
How it works 37 steps

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

Process (37 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 recued-core.freshdesk.ticket.read
Read ticket on freshdesk
◆ conversations recued-core.freshdesk.ticket.conversation.search
Search ticket conversation on freshdesk
■ skip_public_reply compare
Check if has reply does not equal true
◆ public_reply recued-core.freshdesk.ticket.reply.create
Create ticket reply on freshdesk
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 recued-core.freshdesk.ticket.update
Update ticket on freshdesk
skip: step.skip_status_update equal true
■ defaults defaults
Apply defaults
■ 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 core.storage.shared.write
Write storage shared
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
▼
Output
summary card
json seed_freshdesk_reply_closure_watch
Settings 5 configurable

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

reason setting =
ticket id setting =
reply body setting =
status after reply setting = 3
no response timeout days setting = 30

Uses (5 operations)

Pack operation Read ticket on freshdesk recued-core.freshdesk.ticket.read
Pack operation Search ticket conversation on freshdesk recued-core.freshdesk.ticket.conversation.search
Pack operation Create ticket reply on freshdesk recued-core.freshdesk.ticket.reply.create
Pack operation Update ticket on freshdesk recued-core.freshdesk.ticket.update
Shared store Write storage shared core.storage.shared.write

Trust & control

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

Permissions it requires

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

What it's allowed to do

Write Shared store core.storage.shared.write external change

4 more aren't listed here. You'll see them at install.

Data it touches

SurfacesShared store
Warehousedata.shared

About

Tags

freshdesk freshdesksupporthelpdeskticketreplyapprovalcustomer-serviceclosed-loopstate:freshdesk-ticket-reply-closure-watcherpack:freshdesk-ticket-reply-closure

Details

37 steps 5 configurable settings recipe_id: reply-ticket-with-closure-freshdesk