Developers

Gravity Flow Actions and Filters

Understand what hooks Gravity Flow provides, which parameters are available to them and examples of how they can be used to customize the default plugin behaviour to suit your use case / needs.

Extension Actions and Filters

Understand what hooks each Gravity Flow extension provides, which parameters are available to them and how they can be used to customize the default behaviours to suit your use case / needs.

Articles

Gravity_Flow_Step

The Gravity_Flow_Step class is a base class that each step type will extend/override such as the Approval, User Input and Notification step types.

The Gravity_Flow_Assignee object can be based on either a WP user, role, entry email field or one of the Gravity Flow related field types. For interactive steps, the assignee(s) connect the entry and the step for who should action.

gravityflow_step_assignees

The gravityflow_step_assignees filter allows for the assignees of a step to be filtered.

Developing with Gravity Flow

Gravity Flow was written to make it as easy as possible for developers to interact with installations and extend the base functionality.

The Workflow Orchestration API

The Workflow Orchestration API provided by the Gravity_Flow_API class is the starting point for interaction with a local installation.

gravityflow_inbox_fields

The gravityflow_inbox_fields filter is used to customize the field columns displayed in the inbox page in the admin UI (use the block settings or shortcode parameters to do the same in front-end).

The Workflow Web/REST API

The following endpoints are currently available for the Gravity Flow Web/REST API. More will be added - if you need one for your project, please get in touch with Gravity Flow Support.

gravityflow_columns_status_table

The gravityflow_columns_status_table filter allows the columns to be modified for the status page.