Fillout icon

Fillout

Interact with Fillout API
Join our community

Actions5

Overview

This node integrates with the Fillout API to manage form submissions. Specifically, the Submission - Create operation allows users to programmatically create a new submission for a selected form by providing answers to questions and optionally including metadata such as submission time, update time, URL parameters, scheduling details, payment information, and login data.

Common scenarios where this node is beneficial include:

  • Automating data entry into Fillout forms from other systems.
  • Creating submissions based on external events or triggers.
  • Enriching submissions with additional contextual data like scheduling or payment info.
  • Integrating user login information with form submissions.

For example, you could use this node to automatically submit a form response when a customer completes a purchase, attaching payment details and scheduling information for follow-up.

Properties

Name Meaning
Form The specific form to which the submission will be added. Selected from available forms loaded dynamically.
Questions A collection of question-answer pairs representing the submission's responses. Each item requires:
• Question ID (string) — the identifier of the question.
• Value (string) — the answer to the question.
Submission Time Optional datetime specifying when the submission was created. If not provided, defaults to the current time.
Last Updated At Optional datetime indicating when the submission was last updated.
URL Parameters Optional JSON array of objects representing URL parameters associated with the submission. Each object must have id, name, and value fields. Example:
[{"id":"email","name":"email","value":"example@example.com"}]
Scheduling Optional JSON array of scheduling details. Each object must contain an id and a value object with relevant scheduling fields. Example:
[{"id":"nLJtxBJgPA","value":{"fullName":"John Smith","email":"john@smith.com","eventStartTime":"2024-05-20T09:00:00.000Z"}}]
Payments Optional JSON array of payment details. Each object must have an id and a value object containing at least a paymentId field. Example:
[{"id":"cLJtxCKgdL","value":{"paymentId":"pi_3PRF2cFMP2ckdpfG0s0ZdJqf"}}]
Login Optional JSON object containing login information. Must include an email field as a string. Example:
{"email":"verified@email.com"}

Output

The node outputs a single JSON object representing the response from the Fillout API after creating the submission. This typically includes details about the newly created submission(s), such as submission IDs, timestamps, and any metadata returned by the API.

Example output structure (simplified):

{
  "submissions": [
    {
      "submissionId": "abc123",
      "submissionTime": "2024-05-01T12:34:56.789Z",
      "questions": [
        {"id": "q1", "value": "Answer 1"},
        {"id": "q2", "value": "Answer 2"}
      ],
      ...
    }
  ]
}

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Fillout API.
  • The node makes HTTP requests to the Fillout API endpoints.
  • No additional environment variables are required beyond the API key credential.
  • The node uses built-in n8n helper methods for HTTP requests and error handling.

Troubleshooting

Common Issues

  • Invalid JSON format in optional fields:
    The properties URL Parameters, Scheduling, Payments, and Login expect valid JSON strings. Malformed JSON or incorrect structure will cause errors.

  • Missing required fields in JSON arrays/objects:
    Each item in URL Parameters, Scheduling, and Payments must contain specific fields (id, name, value, etc.). Missing these will trigger validation errors.

  • API authentication errors:
    If the API key is invalid or missing, requests will fail with authorization errors.

Error Messages and Resolutions

  • "Invalid URL Parameters JSON format"
    Ensure the input is a valid JSON array with each element having id, name, and value.

  • "Invalid Scheduling JSON format"
    Provide a valid JSON array where each item has id and a value object.

  • "Invalid Payments JSON format"
    Provide a valid JSON array with each item containing id and a value object that includes a paymentId.

  • "Invalid Login JSON format"
    Provide a valid JSON object with an email string field.

  • API request errors (e.g., network issues, 4xx/5xx responses)
    Check API key validity, network connectivity, and ensure the form ID and submission data are correct.

Links and References

Discussion