Overview
This node triggers an n8n workflow when new entries are submitted to Gravity Forms, a popular WordPress form plugin. It periodically polls the Gravity Forms API to check for new form submissions and starts the workflow with the new entry data.
Common scenarios where this node is useful include:
- Automating follow-up emails or notifications when a user submits a form.
- Syncing form submission data to external CRMs, spreadsheets, or databases.
- Triggering downstream processes based on user input collected via forms.
For example, you could use this node to start a workflow that sends a thank-you email whenever someone fills out a contact form, or to add new leads from a registration form into your marketing platform.
Properties
| Name | Meaning |
|---|---|
| Form ID | If set, the trigger only listens for submissions on the specified form ID (string). |
| Results Per Poll | Number of entries to fetch on each poll cycle (number between 1 and 200). |
Output
The node outputs an array of JSON objects representing new Gravity Forms entries detected since the last poll. Each object contains all the fields returned by the Gravity Forms API for an entry, including at least:
id: The numeric ID of the entry.date_created: The timestamp when the entry was created.- Other form field values as provided by the API.
The output is structured as a JSON array under the main output. This allows subsequent nodes in the workflow to process each new form submission individually or in bulk.
No binary data is output by this node.
Dependencies
- Requires an active Gravity Forms API connection configured with appropriate credentials (an API key or token).
- The node uses polling to fetch new entries, so it depends on periodic execution within n8n.
- The Gravity Forms API must be accessible and the user’s API credentials must have permission to read form entries.
Troubleshooting
- No new data triggered: Ensure the correct Form ID is set if filtering by form. Also verify that new entries exist and the API credentials are valid.
- API errors: Common errors may arise from invalid credentials, insufficient permissions, or network issues. Check the API key and endpoint accessibility.
- Duplicate entries: The node tracks the last entry date and ID to avoid duplicates. If duplicates appear, verify system time consistency and that the API returns accurate timestamps.
- Limit property misuse: Setting the "Results Per Poll" too high may cause performance issues or API rate limiting. Use a reasonable number (default 25).