Fillout icon

Fillout

Interact with Fillout API
Join our community

Actions5

Overview

This node interacts with the Fillout API to manage form submissions. Specifically, the Submission - Get All operation retrieves multiple submissions for a selected form, supporting filtering, sorting, and pagination options.

Common scenarios where this node is beneficial include:

  • Fetching all user responses from a particular form for reporting or analysis.
  • Filtering submissions by date range or status to process only relevant data.
  • Searching submissions by text content to find specific entries.
  • Including edit links in the output to allow quick access to modify submissions.

For example, you might use this node to pull all completed survey responses submitted after a certain date, sorted descending by submission time, to generate a summary report.

Properties

Name Meaning
Form The specific form to retrieve submissions from.
Limit Maximum number of submissions to return (minimum 1).
Additional Options Collection of optional filters and settings:
- After Date Filter submissions submitted after this date.
- Before Date Filter submissions submitted before this date.
- Include Edit Link Whether to include a link to edit each submission.
- Search Text string to filter submissions by matching content.
- Sort Sort order of submissions; options are "Ascending" or "Descending".
- Status Status of submissions to retrieve; options are "Finished" or "In Progress" (the latter requires a higher plan).

Output

The node outputs a JSON object containing the retrieved submissions under the root level. The structure corresponds directly to the API response and includes fields such as:

  • responses: An array of submission objects, each representing a single form submission.
  • Each submission typically contains metadata like submission time, answers to questions, status, and optionally an edit link if requested.

No binary data is output by this operation.

Example output snippet (simplified):

{
  "responses": [
    {
      "submissionId": "abc123",
      "submissionTime": "2024-05-01T12:34:56Z",
      "answers": { ... },
      "status": "finished",
      "editLink": "https://..."
    },
    ...
  ]
}

Dependencies

  • Requires an API key credential for authenticating with the Fillout API.
  • The node makes HTTP requests to the Fillout API endpoints.
  • No additional external dependencies beyond standard n8n credentials and HTTP request helpers.

Troubleshooting

  • Error loading forms or submissions: Usually caused by invalid or missing API credentials. Verify that the API key is correct and has necessary permissions.
  • Empty results: Check that the selected form actually has submissions matching the filters (date range, status, search).
  • Invalid date filters: Ensure dates are provided in proper ISO format.
  • Accessing "In Progress" submissions: This feature may require a business plan or higher on Fillout.
  • API rate limits or network errors: May cause request failures; retry or check network connectivity.

If the node throws errors related to JSON parsing or unexpected response formats, verify that input parameters are correctly set and that the Fillout API is operational.

Links and References

Discussion