Turn contact form messages into help desk tickets
Every message from your contact form arrives in Freshdesk as a ticket with the requester already attached.
New submission on your "Contact support" form
Create a Freshdesk ticket with the requester email from the form, the subject line mapped from the form's subject field, the message in the description, and Source set to a custom contact form value
One-directional. A submission triggers the action — nothing is written back into your form.
A shared inbox works until two agents reply to the same person. Moving the contact form into Freshdesk fixes that: the submission becomes a ticket the moment it is sent, the requester is matched on their email address, and the reply goes out from the help desk with a ticket number attached.
Support teams that have just moved off email reach for this first, because it retires the forwarding chain without changing anything visible on the website. The form keeps its own URL and its embed code; only the destination changes.
Setting it up
- 1
Publish your "Contact support" form with the Subject field required — Freshdesk will not create a ticket without a subject, and a blank one fails the Zap rather than falling back to a default.
- 2
In Zapier, set the trigger to formformform's "New Submission" and pick the contact form specifically, not another published form on the same account.
- 3
Add the Freshdesk "Create Ticket" action and connect your help desk domain and API key.
- 4
Map Email Address to the requester email field. Freshdesk matches it against existing contacts and creates a new one when it has not seen the address before.
- 5
Map Full Name to the requester name so first-time senders arrive with a name rather than a bare address.
- 6
Map Subject to the ticket subject and Message to the description. Switch the description to HTML if you want line breaks in a long message to survive.
- 7
Set Source to the custom contact form value you added under Freshdesk admin settings, so web form volume can be reported on separately from email.
- 8
Send a test submission, confirm the ticket lands with the requester attached, then turn the Zap on.
What maps where
Using the Contact Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Freshdesk |
|---|---|
| Full Name | Requester name on the ticket |
| Email Address | Requester email — Freshdesk matches or creates the contact |
| Subject | Ticket subject line |
| Message | Ticket description |
| Phone Number | Phone number on the requester's contact record |
Variations worth knowing
The Create Ticket action accepts a fixed group and priority. Setting them to your general queue and Low keeps contact form traffic out of the escalation view, and an agent can raise a single ticket by hand when a message turns out to be urgent.
Add a dropdown asking which area the message concerns, then use Zapier paths to send billing questions to one Freshdesk group and everything else to another. The trigger stays the same for both; only the action step differs per path.
If something isn't arriving
The subject box in the Freshdesk action is still holding Zapier's placeholder text. Open the action step, clear it, and insert the Subject field from the trigger sample. Re-test before turning the Zap back on.
The requester email is mapped to a static address, usually the one you tested with. Point it at the form's Email Address field instead and Freshdesk will match or create a contact per sender.
Frequently asked questions
Does replying to the ticket in Freshdesk update the form submission?
No. The connection runs one way: a submission creates a ticket. Replies, notes and status changes stay in Freshdesk and are never written back to the form response, which keeps its original values as a record of what was actually submitted.
What happens if someone submits the form twice?
Two tickets are created, both under the same requester if the email matches. Freshdesk does not merge them for you. Agents can merge duplicates from the ticket list, or you can add a Zapier filter that skips a repeat from the same address within a few minutes.
Can I keep collecting responses in formformform as well?
Yes. Every submission is stored in formformform whatever the Zap does, so you can still filter, search and export responses there. The ticket is a copy created for the agent's workflow, not a move of the data out of the form.
Related automations
- Capture feature requests as labelled tickets
Product ideas from your feedback form land in Freshdesk as Feature Request tickets the team can group and revisit.
- Log order and refund requests as tagged tickets
Refund and order issue forms arrive in Freshdesk tagged "order", with the order number already in the subject line.
- Open high-priority tickets for new customer onboarding
New customer onboarding requests become High priority tickets in the Onboarding group with the company name on a custom field.
- Route bug reports to the engineering group
Bug report submissions become Incident tickets in the Technical Support group with priority already set from the severity field.
- Send demo requests to the sales support queue
Every demo request becomes a Freshdesk ticket in the Sales group that a rep can claim and track to resolution.
- Capture webinar questions as tagged tickets
Questions from webinar registrations open as tickets tagged with the event, ready for the host to answer from one view.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free