Create a Gravity Forms Entry When a Webhook Is Received

You want submissions from another site, a call centre tool, or any service that can send a webhook to show up as Gravity Forms entries — in the same place your team already reviews submissions, instead of getting lost in a run log nobody checks. Zapify does this with the A webhook is received trigger and the Create an entry action. Both are free.

What this automation does

The automation is one trigger plus one action:

• Trigger: A webhook is received (WEBHOOK_RECEIVED, Webhooks)
• Action: Create an entry (GRAVITYFORMS_CREATE_ENTRY, Gravity Forms)

When a request reaches the endpoint for this trigger, Zapify creates a new entry on the Gravity Forms form you choose, using values you map from the incoming payload.

This imports the entry — it does not submit the form. Creating an entry this way skips Gravity Forms' own validation and conditional logic, and it does not trigger the form's own notifications or feeds, so it won't email anyone or send data to a connected service on its own. It also does not re-fire Zapify's A form is submitted trigger, so it's safe to use even when the entry lands on a form this same automation also watches. Add a Send an email action after it if you also want a notification.

Before you start

• Gravity Forms must be installed and active, with the form you want to receive entries already created.
• You need the form's field IDs. A simple field uses a plain number, for example 1. Part of a compound field uses a dot, for example 1.3 for a first name or 1.6 for a last name. Check each field's ID under Gravity Forms → Forms → (your form) → Edit.
• The service sending the data must be able to send a webhook (an HTTP POST request).

For how incoming webhooks, sources, and deduplication work in general, see Zapify Webhooks.

How to build the automation

Step 1: Create a new automation

1. In the WordPress admin, go to Zapify → Automations.
2. Click Add New to open the builder.
3. Name it clearly, such as Log website leads as Gravity Forms entries.

Step 2: Add the "A webhook is received" trigger

1. Click Add Trigger.

2. Choose Webhooks as the app.

3. Select A webhook is received.

Step 3: Get the endpoint URL and capture a sample

The builder shows the endpoint for this trigger, in the shape:

POST|GET https://your-site.com/wp-json/zapify/v1/hook/{key}

The {key} is a long random string. Treat the URL as a credential — anyone who has it can send data to this automation. Copy it into the sending service's webhook settings.

Use Listen mode so Zapify captures the next delivery and builds the token list from the payload it actually receives — you then map real field names instead of guessing at the service's documentation. Send one test delivery while Listen is active.

Step 4: Add the "Create an entry" action

1. Click Add Action.

2. Choose Gravity Forms as the app.

3. Select Create an entry.

Step 5: Configure the action

Field	Required	What it does
Form	Yes	The Gravity Forms form the entry should be created on.
Field values	Yes	A list of Gravity Forms field IDs, each mapped to a value from the webhook payload using the {} token button.
Attribute to user	No	Leave empty unless the entry should be attributed to a specific WordPress user.

For example, mapping a webhook's email field to Gravity Forms field 2:

• Form: Leads
• Field values: 2 → {{trigger:email}}

Step 6: Set the steps Live and save

1. Set both the trigger and the action to Live.
2. Click Save.

How to test it

1. Send a test webhook request to the endpoint URL with the fields you plan to map.
2. Open the Gravity Forms form's entries list and confirm a new entry appears with the mapped values.
3. If nothing appears, open Zapify → Logs to see whether the delivery reached the endpoint and what the action reported.

Conclusion

The A webhook is received trigger turns any service that can post JSON into a Gravity Forms entry source, free for up to three webhook sources. Add a Send an email action alongside it if you also want a notification, since importing an entry this way skips Gravity Forms' own notifications. See Zapify Webhooks for sources and deduplication, or send an email when a Gravity Forms form is submitted for the regular submission-based trigger.

FAQs

Will this send Gravity Forms' own notification emails?

No. Creating an entry this way does not trigger the form's notifications or feeds. Add a Zapify Send an email action after it if you want a notification.

Will this re-trigger Zapify's "a form is submitted" trigger?

No. Creating an entry this way does not fire the submission event, so it's safe even when the entry is created on a form this automation also watches.

Is this feature free?

Yes. Both the A webhook is received trigger (up to three sources) and the Create an entry action are free.

How do I know which field ID to use?

Open the form under Gravity Forms → Forms, edit it, and check each field's ID. Compound fields, like a Name field, use a dot for each part — for example 1.3 for the first-name part of field 1.

Can I create entries from more than one source onto the same form?

Yes. Create a separate automation — with its own webhook trigger — for each source, and point them all at the same Create an entry action and form.

Do I need to write any code?

No. Everything is configured in the Zapify visual builder, using Listen mode to capture real payload fields.