Create a Freshdesk ticket intake
Approval-gated Freshdesk ticket intake workflow. It reads agent, group, ticket-field, and solution context, then creates exactly one ticket with caller-supplied subject, requester email, description, status, priority, source, type, and tags through recued-core.freshdesk. It does not update existing tickets, reply, delete, bulk update, attach files, mutate contacts or companies, change automations/admin settings, or call arbitrary Freshdesk endpoints.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (16 steps)
subject
trim
Trim whitespace from setting subject
requester_email
trim
Trim whitespace from setting requester email
description
trim
Trim whitespace from setting description
article_term
trim
Trim whitespace from setting article term
has_subject
compare
Check if subject has data
has_email
compare
Check if requester email has data
has_description
compare
Check if description has data
agent
?
groups
?
fields
?
skip_articles
compare
Check if article term is empty
articles
?
skip: step.skip_articles equal true
skip_create
any
Check if any of the conditions are true
created_ticket
?
skip: step.skip_create equal true
skipped
compare
Check if skip create equals true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
tags
setting
=
recued
source
setting
=
2
status
setting
=
2
subject
setting
=
priority
setting
=
2
freshdesk
setting
=
description
setting
=
ticket type
setting
=
Question
article term
setting
=
requester email
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.