Hooks

Actions

Learn about the different action hooks available within Gravity Forms. Action hooks allow you to perform additional actions when an event takes place.

Filters

Discover the different filter hooks available within Gravity Forms. You can use filters to modify data to better match your particular needs.

JavaScript

Find explanations of the various JavaScript hooks used by Gravity Forms and its add-ons.

Deprecated

Here you will find a listing of the action hooks in Gravity Forms which have been deprecated.

Articles

gform/ajax/post_page_change

The gform/ajax/post_page_change event allows developers to to execute custom JavaScript logic after a form submission is processed via AJAX.

gform/ajax/post_submission_request

The gform/ajax/post_submission_request filter is used to modify the AJAX response after a form is submitted via AJAX, but before the markup is reloaded.

gform/ajax/pre_display_confirmation

The gform/ajax/pre_display_confirmation filter allows add-ons to override the default confirmation display behavior after an AJAX form submission.

The gform/ajax/pre_display_error filter is triggered right before an Ajax error message is displayed. It allows developers to customize the error message shown when an Ajax form submission request fails.

gform/conditionalLogic/applyRules/end

The gform/conditionalLogic/applyRules/end event allows you to react after conditional logic is applied. Use it to trigger animations, restore inputs, or handle field visibility updates in conversational forms.

gform/conditionalLogic/applyRules/start

The gform/conditionalLogic/applyRules/start event allows you to run custom logic right before conditional rules are applied. It’s useful for prepping UI changes, showing loaders, or managing field state in conversational forms.

gform/datepicker/pre_init

This article explains how to use the gform/datepicker/pre_init filter to modify the options used to initialize a field’s datepicker before it is rendered.

gform/form_editor/initialized

The gform/form_editor/initialized event is triggered after the form editor has been initialized. It allows developers to perform actions once the editor is ready.

gform/gfcf/hide_conditions

This gform/gfcf/hide_conditions filter allows developers to add custom visibility rules for fields in conversational forms.

gform/gfcf/visibility_field_classes

The gform/gfcf/visibility_field_classes filter allows customization of which field CSS classes should be monitored for visibility changes. The field observer system uses it to watch for changes to the style.display property of fields.