Reply to a Freshdesk ticket
Use “Reply to a Freshdesk ticket” in Recued. It runs the Freshdesk reply workflow with approval before changes are made.
How it works
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
recued-core.freshdesk.ticket.read
Read ticket on freshdesk
conversations
recued-core.freshdesk.ticket.conversation.search
Search ticket conversation on freshdesk
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
recued-core.freshdesk.ticket.reply.create
Create ticket reply on freshdesk
skip: step.skip_public_reply equal true
private_note
recued-core.freshdesk.ticket.note.create
Create ticket note on freshdesk
skip: step.skip_private_note equal true
status_update
recued-core.freshdesk.ticket.update
Update ticket on freshdesk
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
▼
Output
summary
card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
status
setting
=
0
body text
setting
=
ticket id
setting
=
[object Object]
public reply
setting
=
true
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
Create ticket note on freshdesk
recued-core.freshdesk.ticket.note.create
Pack operation
Update ticket on freshdesk
recued-core.freshdesk.ticket.update
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.