Automura for Gravity Forms – Webhooks & REST API for Automation

Yes. The plugin is 100% free and open source under the GPLv2 license. There is no paid tier, no locked features, and no license key required.

Yes. Gravity Forms is a separate, commercial plugin sold by Rocketgenius and is not included with Automura. You need an active, licensed copy of Gravity Forms installed for this plugin to send webhooks or expose the REST API.

Yes. Paste your n8n Webhook node's Production URL into a webhook in Automura, and every time your chosen Gravity Forms event fires, the data is sent to that URL. The API page also includes ready-made n8n HTTP Request settings for pulling data back out through the REST API.

Yes. Use a Make webhook trigger module's URL as the webhook destination, the same way you would with any other platform.

Yes, through Zapier's "Webhooks by Zapier" trigger, using the URL Zapier provides.

Yes. Any URL that can receive an HTTP POST, PUT, or PATCH request works as a webhook destination, including your own custom script or endpoint.

Create a webhook in Automura, choose the Gravity Forms form and event, paste in your n8n webhook URL, and save. Submitting that form sends the entry data to n8n in real time.

Each webhook can use no authentication, a custom header and value (which covers bearer tokens), Basic Auth with a username and password, or an HMAC signature that the receiving app can verify using the secret you generate in the plugin.

Automura retries a failed delivery automatically, using the retry settings you configure for that webhook. Every attempt is recorded in the Delivery Logs screen along with a plain-language reason for the failure, so you can see exactly what went wrong and resend it if needed.

Yes. The Delivery Logs screen lists every delivery with its status, the event that triggered it, the response received, and the exact failure reason for anything that did not succeed.

Yes. Automura adds a REST API that can list forms, read a form's fields, read and search entries, submit a new entry through the normal Gravity Forms validation and notification process, update an entry, or delete an entry.

Yes, provided the API key used has the matching scope and the relevant endpoint group is turned on in Settings. Each endpoint group can be enabled or disabled independently.

API keys are stored hashed, never shown again after creation, and can be scoped to specific permissions and specific forms with an optional expiry date. Requests are rate-limited against repeated failed attempts, and every API request can be logged.

By default, webhook destinations on private or local network addresses are blocked for security. If you run n8n or another tool locally or on a private network, you can allow private destination URLs from the plugin's Settings screen.

No. Webhooks can be sent in the background, so a visitor's form submission completes normally even if the destination automation is slow to respond. You can choose instant delivery per webhook if you need it to complete before the page confirms submission.

No. Automura does not send any data to the plugin author or to any third party. It only sends data to the webhook URLs and API clients that you configure yourself.

Yes, Automura for Gravity Forms supports WordPress multisite installations.

A webhook is Automura pushing data out to your automation platform the moment something happens in Gravity Forms. The REST API works the other way: your automation platform (or any authorized client) pulls data from WordPress, or pushes data into it, whenever it needs to.

Not directly, since Google Sheets does not accept webhooks on its own. You can get there in one extra step by sending a webhook to n8n, Make, or Zapier, and letting that platform write the row into Google Sheets.

Automura for Gravity Forms is developed by Munir Ahmed (hellomunir.com), a WordPress developer and AI automation specialist, through his agency Vak Web (vakweb.nl).