Incoming Webhook Extension

The Incoming Webhook extension allows you to create workflow steps that wait for input from external systems or trigger new entries via an incoming webhook. This provides a flexible way to connect Gravity Flow processes with third-party applications, automation platforms, or custom integrations.

Key Capabilities

Hold Entries in a Workflow:
After form submission, an entry can pause on a workflow step until a trigger is received from an external system. This supports asynchronous processes such as payment verification, external approval systems, and delayed status updates.

Create New Entries via Webhook:
External systems can send data to a dedicated webhook URL to create a new entry in a form. Once received, the associated workflow begins automatically using the submitted data.

Integrate Third-Party Services:
Use webhooks to connect Gravity Flow workflows with remote APIs, custom applications, or integration services without needing a dedicated add-on.

View Actions and Filters docs for this extension.

Articles

License Key Constants

The constant for main Gravity Flow plugin is GRAVITY_FLOW_LICENSE_KEY Each extension has a license key constant that allows the license to be set via code instead of the database:.

Incoming Webhook – Introduction

The Incoming Webhook Extension can be used in two ways:
After form submission at any point in the workflow, to hold entries on a step until a trigger is received from an external system.

Incoming Webhook – Create an Entry

Incoming Webhooks are a feature of the Incoming Webhook Extension, and allow entries to be created for forms by external systems.

Incoming WebHook – Field Mapping

The Incoming Webhook step supports mapping of incoming data into form fields. The system which is sending data to the incoming webhook in one of 3 formats:     - POST with form-data in the body of the request     - POST with form-data in the body of the request with a Content-Type header = application/json     - POST with raw JSON in the body of the request with a Content-Type header = application/json.

Incoming Webhook – Workflow Step

The Incoming Webhook Step is a feature of the Incoming Webhook Extension which allows workflows to wait until receiving the input of an external system.