Gravity Forms Bridge

Create completely custom ticket forms using the leading form builder for WordPress.

The Gravity Forms add-on for Awesome Support allows you to create just about any version of a new ticket screen or reply screen that you can imagine.  You can then submit all or a portion of the data back to a new or existing Awesome Support ticket!

The best way to get a good idea of how this plugin works is to check out the documentation.

Map Multiple Forms

Most plugins that interface with Gravity Forms only allow you to map one form – we allow you to map as many as you like.


User Friendly

We show you the actual field names from the Gravity Forms form so you don’t have to go looking up Gravity Forms field ID numbers!



This is the MOST COMPLETE Gravity Forms interface you will find among any WordPress Help Desk plugins – nothing else even comes close!

  • Supports all key fields in Awesome Support including any custom fields you define.
  • Store all data you collect in a form inside the ticket – either in separate standard and custom fields – or as text inside of a ticket or reply.
  • Store form meta data inside a ticket (such as ip address)
  • Send data BACK into a Gravity Forms form – this is useful when you want to show a list of department or products or even a list of ticket numbers!
  • Update the STATUS or STATE of a ticket
  • Set the AGENT assigned to a form – this allows you to use logic in a Gravity Forms form to determine which agent gets a ticket!
  • Comprehensive documentation with links to SAMPLE FORMS – you get 6+ sample forms
  • Much more!

What  Kind Of Ticket Forms Can You Build With This?

  • Create forms that allow you to be paid for support and automatically open a ticket when payment is complete
  • Create a different form for each department
  • Create forms that collect additional data for technical support
  • Create forms that walk users through troubleshooting steps before creating a ticket
  • Create forms that dynamically change the information requested depending on which department gets the ticket
  • Create forms that dynamically routes the ticket to different agents based on your custom logic

Purchase options

  • Billed once per year until cancelled

  • Billed once per year until cancelled

  • Billed once per year until cancelled

Add to Cart


  • Your cart is empty.

Basic System Requirements

  • WordPress Version 4.9 or later
  • Awesome Support Version 5.8.0 or later
  • PHP 7.1 (7.3 or later recommended)

Additional Requirements

  • The Gravity Forms plugin which you can obtain from the Gravity Forms website (minimum required version is 2.2.3).


Purchase options

  • Billed once per year until cancelled

  • Billed once per year until cancelled

  • Billed once per year until cancelled

Add to Cart


The items below are great complements to this product!


Recurring Subscription Notification

The pricing for this (and most other add-ons) is set as a subscription by default. However, you are free to cancel the recurring subscription at any time – you will still be entitled to the one year of free updates and support from the time of your last payment. The software will generally continue to work without additional payments. However, you should be aware that, as with all software, a future update of any of WordPress / Awesome Support Free Core could include a breaking change. At that time, if you are not on a subscription plan, you will need to purchase a new license to obtain the compatibility updates necessary for the product to continue to work.

To cancel your subscription:

  • Credit card or stripe users- just go to your MY ACCOUNT page on our website.
  • Paypal users - cancel from directly inside your Paypal account.

This notice does not apply to service products such as custom programming or to free plugins.


Version 1.5.4

  • Fix: It was not possible to assign tickets when submitting a form and Using the Smart Agent Assignment add-on.

Version 1.5.3

  • New: Now the user with no capability to create a ticket when the option for new users to submit a form, will see a warning message when tries to submit a form.
  • FIX: Make the drop-down of Gravity Forms on the settings screen work with the new Titan Framework introduced in 6.0 of core Awesome Support

Version 1.5.1

  • FIX: Reply forms were not updating the ticket status/state if provided.

Version 1.5.0

  • NEW: Added option to hide the gravity form field ids of unmapped items added to the body of the ticket.

Version 1.4.0

  • NEW: Added option to hide blank fields in ticket body.

Version 1.3.0

****Warning: Please test this version in a staging site BEFORE updating!***
  • NEW: Revamped entire process of adding tickets so that other add-ons have an easier time accessing and using the data.

Version 1.2.0

  • New: Added options in the ticket mapping screen to control new user emails that are sent out by when a new user is created.

Version 1.1.2

  • New: Add a filter so developers can hook into unmapped fields as the fields are being processed. The filter name is gf_unmapped_field.
  • Fix: A potential PHP notice could be thrown if an email tag didn't have a value and we're trying to log that value to our log files.

Version 1.1.1

  • Fix: When mapping an agent directly, email assignment alerts were sent to the incorrect agent.

Version 1.1.0

  • New: Register a new custom field called gf_close_ticket. If a value of "1" is mapped to this field when submitting a ticket-reply form, the ticket will be closed.
  • New: Added action hook gf_wpas_after_custom_fields_update
  • New: Added action hook gf_wpas_after_attachments_update
  • New: Added filter gf_wpas_save_form
  • Tweak: Modified filter gf_mapped_field_data to include additional parameters
  • Fix: When using a ticket id (reply) and the option to validate an email address was unchecked and the user was not logged in, the email
    address was ignored completely, always resulting in an "invalid ticket id" message.
  • Fix: Some strings were not being translated
  • Fix: An attempt was made to access an object element without checking to see if the object was valid.
  • Fix: When an attachment was added to a REPLY TICKET form, it was attached to the TICKET instead of the REPLY.
  • Fix: Check to make sure that there is a value set on a field before attempting to write it to the database to prevent an array index error (issue only showed up with ticket reply forms).
  • Fix: If the Ticket State field is mapped but mapped value is empty do not attempt to update the ticket state
  • Fix: If the Ticket Status field is mapped but mapped value is empty do not attempt to update the ticket status

Version 1.0.7

  • Tweak: Prevent scripts from loading on pages that are not related to Awesome Support.
  •  Fix: Taxonomy Term IDs were not being set on tickets properly

 Version 1.0.6

  • Tweak: Show the term name instead of the id
  • Tweak: Added two do_action hooks when a ticket is created
    • do_action( 'gf_wpas_after_ticket_insert_success', $this->ticket_id, $this->data, $args );
    • do_action( 'gf_wpas_after_ticket_insert_failed', $this->data, $args );
  • Tweak: Updated language string file

Version 1.0.5 - May 14th 2017

  • Enh: All taxonomy fields can now be "populated"
  • Enh: Separate log files for each form
  • Enh: Option to auto-populate email mapped field if user is logged in
  • Fix: Various bug fixes
  • Tweak: Code refactoring
  • Tweak: Minimum version of AS is now 4.0.0
  • Tweak: Minimum version of PHP is now 5.6

Version 1.0.4 - Internal Release Only

  • Tweak: Update language files
  • Tweak: Lots of code clean up
  • Fix: Incorrect object reference causing nulls to be saved to user-defined custom fields

Version 1.0.3 - December 27th 2016

  • Tweak: Enforce core AS file upload settings.

Version 1.0.2 - December 2nd 2016

  • Add: Support File uploads.

Version 1.0.1 - November 28th 2016

  • 2nd beta release to customers
  • Fix: Custom fields mapping logic
  • Fix: Custom fields not updating postmeta

Version 1.0.0 Beta 1 - November 2016

  • Initial release to customers