Actions10
- Form Actions
- Entry Actions
- Tool Action Actions
Overview
This node interacts with the Gravity Forms REST API v2, specifically to list entries submitted through forms. It allows users to retrieve multiple form entries with optional filtering and pagination controls. This is useful for automating workflows that need to process or analyze form submissions, such as exporting data, triggering notifications based on entry status, or integrating form data into other systems.
For example, you can use this node to:
- Retrieve all active entries from a specific form.
- Fetch entries submitted within a certain date range.
- Limit the number of entries returned for batch processing.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching entries or limit the number of results. |
| Limit | Maximum number of entries to return if "Return All" is false (minimum 1, maximum 500). |
| Filters | Collection of filters to narrow down the entries: |
| Form ID | Limit entries to those submitted to a specific form (by its ID). |
| Start Date | Only include entries submitted on or after this date/time. |
| End Date | Only include entries submitted on or before this date/time. |
| Status | Filter entries by their status: Active, Spam, or Trash. |
Output
The node outputs an array of JSON objects representing the Gravity Forms entries matching the specified criteria. Each object corresponds to one entry and contains all available fields returned by the Gravity Forms API for that entry.
If binary data were involved (e.g., file uploads), it would be included in the output's binary property, but this operation only returns JSON data about entries.
Dependencies
- Requires an API key credential for authenticating with the Gravity Forms REST API v2.
- The node uses HTTP requests to communicate with the Gravity Forms API endpoints.
- No additional external dependencies beyond the configured API credentials and network access to the Gravity Forms instance.
Troubleshooting
- Empty or invalid JSON errors: If providing JSON input elsewhere in the node, ensure it is valid and not empty.
- API authentication failures: Verify that the API key credential is correctly configured and has sufficient permissions.
- Rate limits or large data sets: When retrieving many entries, consider using the "Return All" option carefully to avoid hitting API rate limits or timeouts.
- Invalid filter values: Ensure that form IDs exist and dates are in correct ISO format.
- Unsupported operations or resources: The node throws clear errors if an unsupported resource or operation is requested.