🎉 Celebrate with 10% OFF on All Products! Use Code: GFEX10 Or Buy Any 2+ Items for 30% OFF with Code: GFEX30!

Gravity Forms Freshservice Premium Add-on Setup Guide

Updated 9 min read Gravity Forms Integrations A–Z
On this page
  1. Video walkthrough
  2. What you need
  3. Step 1: install and connect
  4. The other settings
  5. Step 2: add a feed to a form
  6. Subject
  7. Description
  8. Requester email
  9. Priority, status and source
  10. Create the requester first
  11. Custom fields
  12. Condition
  13. What happens after a submission
  14. The Freshservice box on the entry
  15. Reliability: never a second ticket by accident
  16. Merge tags and notifications
  17. Entry list actions
  18. Use with payments
  19. For developers
  20. Privacy and security
  21. Troubleshooting
  22. Questions
  23. Do I pay GravityExtra for the tickets?
  24. Can one form create more than one ticket?
  25. Does my data pass through GravityExtra?
  26. Will a timeout create two tickets?

Video walkthrough

Gravity Forms Freshservice Add-On Setup Guide: Help Desk Tickets from Forms (WordPress Side)
Video setup guide: Gravity Forms Freshservice Watch on YouTube

The Gravity Forms Freshservice Premium Add-on creates a support ticket in your own Freshservice account when a Gravity Forms form is submitted. A feed decides what the ticket says (with merge tags), who the requester is, how it is prioritised and when it is created (conditional logic). The ticket is created in the background, so the visitor never waits, and the result is written to the entry as a note. Nothing goes through GravityExtra: the add-on talks only to your own Freshservice domain, using the Freshservice API v2.

What you need

  • WordPress 5.8 or newer, PHP 7.4 or newer and Gravity Forms 2.5 or newer.
  • A Freshservice account. You need the account domain, which looks like yourcompany.freshservice.com, and an API key.
  • Your API key from the Freshservice portal. Open your profile in Freshservice and look under Profile settings for Your API key. The same key the portal shows you is the one you paste into the add-on.
  • Your GravityExtra licence key. Without an active licence nothing is created and the entry gets a note that says so.

The add-on uses the Freshservice API v2 on your own account domain. Your API key is stored encrypted and is only ever sent to your own Freshservice domain, in the authorisation header, so it can never reach anyone else.

Step 1: install and connect

  1. Upload and activate the add-on in Plugins.
  2. Open Forms → Settings → Freshservice and activate your licence key.
  3. Enter the Account domain exactly as Freshservice shows it, for example yourcompany.freshservice.com, and the API key. Press Save.
  4. Press Check the connection. The add-on reads one ticket from your account and creates nothing. If it succeeds, your domain and key are right.
The Freshservice settings screen in Gravity Forms
The settings: your own Freshservice domain and API key, stored encrypted, plus the defaults for every feed.

The API key is encrypted before it is saved, with a key made from your site’s own security salts, and it is never shown again. Leave the box empty to keep the stored key, or tick Remove the stored API key when saving to delete it. Because the add-on only ever sends the key to your own account domain, it can never be sent anywhere else.

The other settings

  • Default priority: used by a feed that does not set its own. Choose Account default, low, medium, high or urgent.
  • Default status: Account default, open, pending, resolved or closed. New tickets usually start as open.
  • Default source: Account default, portal, email, phone, chat and so on. This records how the ticket reached your helpdesk.
  • Daily cap of tickets: after this many tickets in one day (UTC), across all feeds, the add-on stops and writes a note. Empty or 0 means no cap.

Step 2: add a feed to a form

The Freshservice add-on is a feed add-on. A form can have several feeds, and each feed creates one ticket. That lets a single form raise, say, a sales enquiry ticket for one team and a support ticket for another, each with its own wording and conditions.

  1. Open the form, go to Settings → Freshservice and press Add New.
  2. Give the feed a name that says what it does, for example Support enquiry.
  3. Fill in the Subject, the Description and the Requester email.
  4. Set the Priority, Status and Source, or leave them on Account default to use the settings.
  5. Turn on the Condition if the ticket is only for some entries, then save.
A Freshservice feed in the Gravity Forms editor
A feed: the subject and description with merge tags, the requester email field, the priority, status and source, the create-requester option and the condition.

Subject

The one-line title of the ticket. Use merge tags so each ticket names itself, for example New enquiry from {Name:1}. The subject is what your agents see first in their ticket list, so put the useful words at the start.

Description

The body of the ticket. Write it with merge tags, and use {all_fields} to include every answer the visitor gave, laid out as a label and value for each field. You can mix free text and tags, for example a greeting line followed by {all_fields}, so your agent reads the whole submission inside the ticket without opening the entry in WordPress.

Requester email

Put the merge tag of an Email field here, for example {Email:3}. Freshservice links the ticket to this requester by their e-mail address, so replies and history stay with the right person. If the person is not yet a requester in your account, Freshservice can still attach the ticket to the address.

Priority, status and source

Each feed can set its own Priority (Account default, low, medium, high or urgent), Status (Account default, open, pending, resolved or closed) and Source (Account default, portal, email, phone, chat and more). Leave any of them on Account default to fall back to the settings, so you only override what this particular feed needs.

Create the requester first

Tick Create the requester first if they do not exist yet and give a Requester name (a merge tag works, for example {Name:1}). When this is on, the add-on creates the requester in Freshservice before the ticket, so a brand-new contact already has a name and e-mail on file. Leave it off to let Freshservice attach the ticket to the e-mail address on its own.

Custom fields

The Custom fields map sends extra values into the custom fields of your Freshservice tickets. On each row, type the Freshservice custom field key, then choose a form field or type a value (merge tags work). This is how a dropdown answer on the form becomes, say, a category or a product on the ticket.

Condition

The same conditional logic as Gravity Forms notifications: create the ticket only for the Premium plan, only when the Urgent box is ticked, only for one country, and so on. A form can have as many feeds as you like, each with its own subject, requester, priority and condition, so the right ticket is created only for the entries that match.

What happens after a submission

The entry is saved and the confirmation is shown at once. A background job then creates the ticket of each matching feed in your Freshservice account and writes a note on the entry: the ticket number it created, or the reason it could not. The visitor never waits for Freshservice to answer.

The Freshservice box on a Gravity Forms entry
Every feed on the entry: its status and an Open ticket link straight into the Freshservice portal.

The Freshservice box on the entry

Each entry has a Freshservice box that shows every feed’s status and, when a ticket was created, an Open ticket #N link that takes you to that ticket in the Freshservice portal. You can see at a glance which feeds ran and jump to the ticket without searching for it.

Reliability: never a second ticket by accident

A duplicate ticket wastes an agent’s time and confuses the requester. The add-on is built so that a network wobble can never create the same ticket twice.

  • Idempotency: before a request is sent, the add-on records that it is about to send it. If the job then crashes or times out, the restart sees that record and does not send a second request, so one submission makes at most one ticket per feed.
  • Safe retries: when Freshservice cannot be reached before anything was sent, or answers HTTP 429 (too many requests), nothing was created, so the job tries again later with a growing wait between attempts.
  • Unsure results: when a request may already have arrived (a timeout, an HTTP 5xx answer, or a reply the add-on cannot read), it is marked unsure and never repeated automatically. The note tells you to check your tickets in Freshservice before you create another.

Merge tags and notifications

Once a ticket is created, these merge tags carry its details into notifications and confirmations. Add a feed id to read one feed, for example {freshservice_ticket_id_7}; without it the newest result of the entry is used.

  • {freshservice_ticket_id}: the number of the ticket that was created.
  • {freshservice_status}: the status the add-on recorded for the ticket.

Forms with a Freshservice feed also get two notification events: Freshservice: the ticket was created and Freshservice: the ticket could not be created. Use the first to send the requester their ticket number, and the second to warn your team when something needs a hand.

Entry list actions

Select one or more entries in the entry list and use the bulk actions to create tickets after the fact, for example for entries that came in before you added the feed.

  • Create Freshservice ticket (skip done): creates tickets for the selected entries that do not have one yet, and skips entries that are already done.
  • Create Freshservice ticket again (creates another): creates a fresh ticket on purpose, for example after you checked an unsure result and found no ticket was ever created.

Use with payments

The feeds follow the Gravity Forms add-on framework, so they work with payment add-ons that delay feeds until the payment is complete. Turn on Create the Freshservice ticket only when payment is completed so an order ticket is created only for paid orders, not for an abandoned checkout.

For developers

  • gform_freshservice_ticket (filter): change the ticket before it is created, or cancel it altogether for an entry. It receives the ticket data along with the entry, feed and form.
  • gffs_ticket_created (action): fires when a ticket is created. Arguments: the result, the entry, the feed and the form.
  • gffs_ticket_failed (action): fires when a ticket cannot be created. Arguments: the entry, the feed, the form and the reason.

Privacy and security

The answers you put in the subject, description, requester and custom fields are sent to your own Freshservice account to create the ticket, and Freshservice processes them under its own terms. Mention your helpdesk in your privacy policy and collect consent where the law asks for it. The API key is encrypted at rest, is only ever sent in the authorisation header to your own account domain, and is never written to an entry note.

Troubleshooting

  • Nothing is created: read the entry notes. Every reason is written there: no licence, no account domain or key, a condition that did not match, the daily cap, or Freshservice’s own answer.
  • The connection check fails: copy the account domain and the API key again from Freshservice. The domain should be the full host, for example yourcompany.freshservice.com, with no extra path.
  • The entry says unsure: a reply was lost in transit. Check your tickets in Freshservice before you use Create again, so you do not raise a second one.
  • Tickets stop part-way through a busy day: you may have hit the daily cap. Raise it or clear it in the settings.

Questions

Do I pay GravityExtra for the tickets?

No. The tickets are created in your own Freshservice account and count against your own plan there. The add-on is a licence for the software, updates and support.

Can one form create more than one ticket?

Yes. Add a feed for each ticket you want. Each feed has its own subject, requester, priority and condition.

Does my data pass through GravityExtra?

No. The add-on sends the ticket straight from your site to your own Freshservice domain, with nobody in the middle.

Will a timeout create two tickets?

No. The add-on records a request before it sends it, so a crash or timeout cannot create a second ticket. A result it cannot confirm is marked unsure and never repeated on its own.

Still need help?

Our support team answers tickets every day, usually within a few hours.

0
0
Your Cart
Your cart is emptyReturn to Shop
🔥 FREQUENTLY BOUGHT TOGETHER
Complete Combo & Save 40%!
ITEM IN YOUR CART
Gravity Forms Klaviyo Add-on
$39.00/yr
+
🎁 RECOMMENDED ADD-ON SAVE 40% OFF
Original Price: $39.00/yr
Bundle Special Price: $23.40/yr