Do you want to add (and process) data from an incoming webhook to your Gravity Form? You can use the Incoming Webhook Add-on from Gravity Flow to do that. We explain where to get the Add-on and give you a real example how we use it.
How to configure the incoming webhook?
To get it working, you’ll need to add to your WordPress site Gravity Forms, Gravity Flow and the Incoming Webhook Add-on. Once you’ve done that, you can go to your Gravity Form settings (settings of one specific form) and click on Incoming Webhook:
Click Add New and fill in your Webhook name (required):
Once you save the settings, Gravity Flow Incoming Webhooks will automatically generate a Webhook URL for you to use for connecting Webhooks from other sites to your site, like GitHub, Moodle or Paddle:
Example GitHub webhooks
In GitHub you have within the Settings page of one of your repositories a menu link to Webhooks:
When you click Add webhook or Edit an existing one, you can paste the Webhook URL generated by Gravity Flow inside the Payload URL. Important is to select ‘application/json’ as Content type:
We leave SSL verification enabled (this checks if your site has a valid SSL certificate).
You can select on which triggers GitHub should post information to your Gravity Flow Incoming Webhook. You can select to send everything, but in this example we only want to get information on a specific individual event, namely the Releases event.
By selecting Releases, we’ll get an update from GitHub whenever a release is created, edited, published, unpublished or deleted. This way we can easily update information on our site about our own Add-ons, to keep it in sync with what’s happening on GitHub (where we manage all of our plugins):
Once some Release action is triggered, you can check in the tab ‘Recent Deliveries’ what was send to your Incoming Webook (all fake data for this example, but it should more or less look like this):
We see that the Response gave back ‘200’ (in green), which means our WordPress website accepted our GitHub data. The most important to do in your Gravity Form Incoming Webhook settings is mapping the Payload to specific fields.
Here is our example to process the above GitHub data:
You see that when we want to map data from within an array inside the JSON, we have to us \ to target it specifically. For example we see that the release “url” is inside “release”. You can map that value by using release\url as your Key.
In our Gravity Form we have several Single Line fields, that we named exactly like the Key, but this is not necessary, you can use any label you want.
Once this is set-up, we receive specific information on our site after we create, publish or delete releases on GitHub. Based on the values you can create follow up Workflow steps like processing this information on other places on your site or sending an automatic Twitter message or e-mail update to interested users.
Read tutorials about
How to Replace Zapier with n8n (Using the GravityWP n8n Connector)
Tired of burning Zapier tasks on every Gravity Forms submission? This guide shows you how to replace Zapier with n8n using the GravityWP n8n Connector. You’ll learn how to move an existing Zap step-by-step into n8n, cut automation costs, and keep full control over where your data lives.
n8n vs Zapier: Which Automation Tool Actually Fits Your Work?
Trying to decide between n8n vs Zapier? This article breaks down pricing, hosting, integrations, AI features, and where self-hosted n8n on a cheap VPS can beat Zapier’s task-based plans. You’ll also see how Gravity Forms users can plug in the GravityWP n8n Connector and move key workflows off Zapier without rebuilding their forms.
Cloudflare Tunnel + n8n: Expose Local n8n for Webhook Testing (Dev Only)
This guide shows how to use Cloudflare Tunnel Quick Tunnels to put a local n8n instance on the internet for real webhook testing. It’s a dev-only recipe that lets tools like GravityWP’s n8n Connector call your local n8n over HTTPS, without renting a VPS or opening ports.
Self-Host n8n with Docker on a VPS
Learn how to self-host n8n with Docker on a VPS using a production-ready setup. This step-by-step guide walks you through configuring Docker Compose, Postgres, HTTPS, and WEBHOOK_URL so you can run reliable, secure n8n workflows on your own server.
