Krom Automation Pro connects to Gravity Forms, giving you four triggers and three actions that cover form submissions, entry management, and payment events.

Combined with Krom Automation’s other integrations, Gravity Forms becomes the starting point for automations that span CRM sync, email marketing, Slack notifications, Google Sheets logging, and more.

No API key or configuration is required. Krom Automation detects Gravity Forms automatically when the plugin is active.

Requirements #

• Krom Automation Pro installed and activated
• Gravity Forms installed and active
• For the Payment Completed trigger: a Gravity Forms payment add-on (Stripe, PayPal, Square, or similar)

Available triggers #

Form Submitted

Fires after a Gravity Forms submission passes all validation and the entry is saved to the database. This is the primary trigger for lead capture, contact, and application form automations.

Data field	Description
form_id	The Gravity Forms form ID
form_title	The form title
entry_id	The unique ID of the submission entry
created_by	User ID of the logged-in user who submitted (empty if guest)
source_url	URL of the page where the form was submitted
All entry fields	Every form field value is available using the field label or field ID as the merge tag key

About form field merge tags: Gravity Forms field values are available as merge tags using the field’s label (lowercased, with spaces replaced by underscores) or the field ID. For example, a field labelled “First Name” is available as {{first_name}}. Check the execution log after the first real submission to see exactly how field names are formatted in the trigger data.

Entry Updated

Fires when an admin opens a Gravity Forms entry in the back end and saves changes to it. This does not fire on initial submission, only on subsequent edits.

Data field	Description
form_id	The Gravity Forms form ID
entry_id	The entry ID that was updated
Changed fields	The specific field values that were changed

Common use: Triggering a notification or a follow-up action when an admin updates the status or notes on a specific entry, such as marking a job application as reviewed.

Entry Status Changed

Fires when a Gravity Forms entry status changes. Common status transitions include active to spam, active to trash, or spam to active.

Data field	Description
form_id	The Gravity Forms form ID
entry_id	The entry ID whose status changed
old_status	The status before the change
new_status	The status after the change

Common use: Alerting an admin when entries are being marked as spam at an unusual rate, or triggering a follow-up when a flagged entry is restored to active status.

Payment Completed

Fires when a Gravity Forms payment completes successfully. Requires a Gravity Forms payment add-on such as Gravity Forms Stripe, Gravity Forms PayPal Checkout, or another supported payment integration.

Data field	Description
form_id	The Gravity Forms form ID
entry_id	The payment entry ID
payment_amount	The amount paid
payment_status	The payment status (should be paid on this trigger)
transaction_id	The transaction ID from the payment gateway

Common use: Sending a payment confirmation email, notifying the team via Slack when a payment arrives, logging payments to Google Sheets, or triggering a fulfillment workflow.

Available actions #

Add Entry Note

Appends a note to a Gravity Forms entry. The note is visible in the entry detail view in the Gravity Forms admin, under the Notes section.

Field	Description
entry_id	The entry to add the note to. Use {{entry_id}} when working with the submission from the triggering event.
note_text	The text of the note. Merge tags are supported.

Common use: Adding a timestamp note when an auto-responder is sent, logging CRM sync status on the entry, or recording when a follow-up email was triggered.

Send Notification

Re-sends a saved Gravity Forms notification for a specific entry. Gravity Forms notifications are the email notifications you configure inside the GF form editor (Admin Notification, User Confirmation, etc.).

Field	Description
form_id	The form ID. Use {{form_id}} from the trigger.
entry_id	The entry ID. Use {{entry_id}} from the trigger.
notification_id	The ID of the specific GF notification to resend. Find this in the form’s notification settings.

Common use: Resending a user confirmation email if the original failed, triggering a delayed follow-up notification after a set period, or sending a notification to a different recipient based on a condition.

Update Entry

Updates a field value or the status of an existing Gravity Forms entry.

Field	Description
entry_id	The entry to update. Use {{entry_id}} from the trigger.
field_id	The numeric ID of the GF form field to update. Find field IDs in the GF form editor.
field_value	The new value to write to the field. Merge tags are supported.

Common use: Writing a CRM contact ID back to the entry after creating a CRM contact, updating a status field on the entry, or recording AI-generated output into a specific entry field.

Setting up your first Gravity Forms workflow #

1. Go to Krom Automation > Workflows and click Add New Workflow.
2. Click Add Trigger and select Form Submitted under the Gravity Forms category.
3. Add a Condition node if you want the workflow to run only for a specific form. Set the field to form_id, operator to equals, and value to your specific form ID.
4. Add your actions below the trigger or condition node.
5. Use {{entry_id}}, {{form_title}}, and your form field names as merge tags in action fields.
6. Simulate the workflow, then activate it.

Screenshot: Gravity Forms Form Submitted trigger node on the canvas with a condition node below it filtering by form_id.

Screenshot: Send Email action configured with form field merge tags in the message body.

Real-world automation examples #

Instant auto-responder email to the submitter Trigger:

Form Submitted (filtered by form_id) Action: Send Email to the submitter’s email field with a personalised thank-you message using their name merge tag.

Lead routing by company size Trigger:

Form Submitted (filtered by form_id) Condition: Form field company_size contains Enterprise Yes branch: Slack Send Message to #enterprise-leads No branch: Slack Send Message to #smb-leads

Payment confirmation and team notification Trigger:

Payment Completed (filtered by form_id) Action 1: Send Email to the customer using {{payment_amount}} and {{transaction_id}} in the body Action 2: Slack Send Message to #payments with the amount and transaction details

Log all submissions to Google Sheets Trigger:

Form Submitted Action: Google Sheets Append Row with columns for {{form_title}}, {{entry_id}}, the submitter’s name and email fields, and {{source_url}}

Multi-step follow-up sequence Trigger:

Form Submitted (filtered by form_id) Action 1: Send Email (immediate auto-responder) Action 2: Delay 3 days, then Send Email (follow-up check-in) Action 3: Add Entry Note recording that the follow-up was sent

Pre-built templates #

Install these from Krom Automation > Templates:

Template	What it does
gf-auto-responder	Sends an instant auto-responder email on form submission
gf-lead-notification	Sends an admin or team notification for new leads
gf-lead-routing	Routes leads to different Slack channels based on a form field value
gf-multi-step-followup	A timed multi-step follow-up sequence after submission
gf-payment-confirmation	Sends a payment confirmation email when a GF payment completes
gf-spam-alert	Sends an admin alert when a spam entry is detected

Troubleshooting #

Form field merge tags aren’t resolving correctly.

Field names in Gravity Forms can vary depending on how the field is configured. After the first real submission, open Krom Automation > Logs and click into the execution detail. Look at the input data for the trigger step to see the exact field keys as they were captured. Copy those keys exactly into your action field merge tags.

The Payment Completed trigger isn’t firing.

Confirm you have a Gravity Forms payment add-on installed and that the payment was processed through it. The trigger requires a GF payment add-on — it doesn’t fire for standard form submissions that happen to collect payment information in a text field.

The workflow runs for forms I didn’t intend.

Add a condition on form_id to restrict the trigger to a specific form. Without this, the Form Submitted trigger fires for every submission across all your Gravity Forms.