Gravity Flow Incoming Webhook

Name: Gravity Flow Incoming Webhook 1.6
SKU: 8650
Price: 3.99 USD
Availability: InStock

Version 1.6

SKU: 8650

$3.99$59.00Save 93%

One-time payment · lifetime access to this file

Instant download after purchase
100% original, unmodified GPL file
Free lifetime updates on request
Secure Razorpay / PayPal checkout

Want the whole library?Get a membership and download any theme or plugin on the site.

Product details

Version on file: 1.6
Type: plugin
Released: 17-09-2021
File size: 62.97 KB
License: GPL

About Gravity Flow Incoming Webhook 1.6

Gravity Flow Incoming Webhook is an extension for Gravity Flow, the workflow plugin that runs on Gravity Forms. It adds a workflow step that waits for an incoming webhook request, so an outside service can start or continue a workflow when something happens elsewhere.

It does nothing alone. You need Gravity Forms and Gravity Flow installed. The file on record is version 1.6, released September 17, 2021, and is about 63 KB. The listing doesn't give setup details, so check the documentation in the package, and test with your current Gravity Forms and Gravity Flow versions.

Requirements

Gravity Forms
Gravity Flow (the parent plugin)

Key features

Incoming webhook step: Adds a step that waits for a request from an external service.
Gravity Flow integration: Works inside Gravity Flow's workflow steps and statuses.
Built on Gravity Forms: Applies to workflows attached to Gravity Forms forms.
Small add-on: The package is about 63 KB.

Is it right for you?

A good fit for

Teams that already use Gravity Flow and want other apps to move a workflow forward
Developers connecting a payment, signing or CRM service to an approval process

Look elsewhere if

Sites without Gravity Forms and Gravity Flow
Buyers who want a no-code connector, since the other service still has to send the request

How to install Gravity Flow Incoming Webhook 1.6

1
Download the file
Open My Account → Downloads and download the product. If the archive contains several zips (documentation, child theme, licensing files), you need the one named after the product.
2
Upload it to WordPress
In your dashboard go to Plugins → Add New Plugin → Upload Plugin and choose the zip.
3
Install and activate
Click Install Now, then Activate. If an older or free copy is already installed, WordPress offers to replace it with the uploaded version.

Notes for this product

Install and activate Gravity Forms and Gravity Flow first, then add this extension.

Setup: using Gravity Flow Incoming Webhook 1.6

Install the parents. Make sure Gravity Forms and Gravity Flow are active.
Add the add-on. Install and activate Gravity Flow Incoming Webhook.
Add a step to a workflow. In the form's workflow settings, add the incoming webhook step where the workflow should wait.
Copy the URL and test. Use the step's URL in the other service, send a test request and check the entry advances.

Common problems and fixes

The workflow stays on the webhook step

Why it happens: The external service never sent a request, or sent it to the wrong URL.
How to fix it: Re-check the URL in the sending service and look at that service's delivery log to confirm the request went out.

“The link you followed has expired.” when uploading

Why it happens: The zip is larger than your server's PHP upload limit (upload_max_filesize / post_max_size).
How to fix it: Raise the upload limit in your hosting control panel, or unzip the file and upload the folder to wp-content/plugins with your host's file manager or SFTP.

“The package could not be installed. No valid plugins were found.”

Why it happens: The uploaded zip is a bundle (or a theme), not the plugin itself.
How to fix it: Unzip the download once and upload the inner zip named after the plugin.

“Plugin could not be activated because it triggered a fatal error.”

Why it happens: Usually a PHP version older than the plugin needs, or a second copy of the same plugin (for example the free version) still active.
How to fix it: Check your PHP version under Tools → Site Health → Info, deactivate any other copy of the plugin, and enable WP_DEBUG_LOG to see the exact error.

Licence or “updates unavailable” notices

Why it happens: The developer's licence key isn't included. Features that call the developer's servers (template libraries, cloud APIs, automatic updates) need it.
How to fix it: Everything that runs locally works without it. For a newer file, use Request an update from your account.