Gravity Forms n8n Add-On

Many sites end up with a separate WordPress integration for every service a form needs to reach. This plugin takes a different route: the form hands each submission to n8n, and the workflow decides what happens next. One connection from Gravity Forms can reach whatever your workflows already connect to, so you do not add and maintain a new integration for each destination.

Because n8n handles the workflow logic, changes to the automation happen there rather than in WordPress. Feeds work with n8n Cloud and self-hosted instances, and you set them up in your dashboard next to your other Gravity Forms feeds. For teams already using n8n for internal processes, website forms simply become another trigger in the same system.

Features

• Submissions trigger workflows: Each form submission is passed to n8n webhooks, so workflows you have already built can act on the entry as soon as it arrives.
• One connection, many destinations: n8n routes the data onward to the services your workflow reaches, so you avoid installing a separate WordPress integration for each one.
• Per-form feeds: Connect only the forms that should feed n8n and leave the rest untouched. Feeds are managed alongside your other Gravity Forms feeds.
• Conditional logic per feed: Set conditions on a feed so only the submissions that match your rules are sent to n8n.
• JSON or form-encoded payloads: Send entry data as JSON by default or as form-encoded data, in a stable shape that your n8n workflow can use directly.
• Asynchronous sending: Submissions are processed in the background, so webhook latency does not block the redirect that visitors see after sending a form.
• Retries and delivery tracking: Failed deliveries are retried with exponential backoff using WP-Cron. Each entry shows its delivery status, with entry notes recorded for every attempt.
• Resend and test tools: Use the n8n Delivery column, single-entry Resend or the bulk Resend to n8n action. A Send Test button on the feed settings page checks your setup.

Best for

• Teams already running n8n for internal processes
• Sites using self-hosted or n8n Cloud workflows
• Gravity Forms users routing entries to many services