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.
New submission on your "Order issue" form
Create a Freshdesk ticket tagged "order", with the order number in the subject, the customer's email as requester, and the issue details in the description
One-directional. A submission triggers the action — nothing is written back into your form.
Post-purchase questions are the ones that need a paper trail. A refund request that arrives as a chat message has to be re-typed somewhere before anyone can act on it; the same request as a Freshdesk ticket already carries the order number, the product and the date of purchase.
Ecommerce teams set this up so refunds can be handled as a group rather than one at a time. The "order" tag gives them a saved view, the order number in the subject makes search work, and the requester email ties every request from a returning customer to one contact record.
Setting it up
- 1
Publish the "Order issue" form with Order Number required — the subject line and every later search depend on that value being present.
- 2
Create the Zap with formformform's "New Submission" trigger pointed at that form, then pull a sample submission so the field names populate the action step.
- 3
Add Freshdesk "Create Ticket" and compose the subject as a fixed prefix plus the Order Number field, giving you subjects like "Order 10482 — refund request".
- 4
Map Email Address to requester email so the ticket attaches to the customer's existing Freshdesk contact instead of creating a stray one.
- 5
Build the description from Reason for Refund and Additional Explanation, with Product Name and Date of Purchase on their own lines above them.
- 6
Add "order" as a static tag on the action step, and add a second tag from Preferred Refund Method if you want card reversals separated from store credit.
- 7
Set Group to whichever queue handles returns and leave Priority at Medium, so an agent raising a genuinely urgent case still stands out.
- 8
Run a test submission with a real order number, check the tag and subject in Freshdesk, then enable the Zap.
What maps where
Using the Refund Request Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Freshdesk |
|---|---|
| Order Number | Ticket subject, after the order prefix |
| Customer Name | Requester name |
| Email Address | Requester email |
| Reason for Refund | Ticket description |
| Product Name | Description, above the stated reason |
| Preferred Refund Method | Second ticket tag |
Variations worth knowing
The template asks "Has the item been returned or will it be returned?". Use that answer in a Zapier path so a ticket about goods already sent back reaches the warehouse group while a refund on an undelivered order goes to billing. Both keep the "order" tag.
The form captures the request; it does not move funds. Agents issue the refund in your payment provider or store admin and note the reference on the ticket. Hosted checkout can collect new payments through a form, but refunds still belong to the original transaction.
If something isn't arriving
Those submissions left the field blank. Make Order Number required in the form and add a Zapier filter that continues only when the field is not empty, so an incomplete request is caught before it becomes an untraceable ticket.
Freshdesk's tag field takes a list, and a single value typed with a trailing comma reads as empty. Enter the tag with no punctuation around it, and check that the agent account behind the API key is allowed to edit tags.
Frequently asked questions
Can the ticket update the order in my store?
Not through this connection. The Zap runs one way: a submission creates a Freshdesk ticket. To touch the store you would add a further action step to the same Zap. Nothing Freshdesk does afterwards is written back to the form or the order.
How do I keep refund requests from returning customers together?
Map the form's Email Address to the requester field. Freshdesk files every ticket under the matching contact, so an agent opening one request sees that customer's earlier tickets in the sidebar without any extra configuration on your side.
Should refunds and exchanges share one form?
One form is easier to maintain. Ask which outcome the customer wants, then branch with conditional logic so only the relevant follow-up questions appear. The Zap can read that answer and set a different Freshdesk group for each case.
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.
- 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.
- 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.
- 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