Fillout Trigger icon

Fillout Trigger

Starts the workflow when a Fillout form is submitted
Join our community

Overview

This node triggers an n8n workflow when a submission is received from a specified Fillout form. It listens for webhook events sent by Fillout whenever a user submits the chosen form. This is useful for automating processes that depend on form responses, such as lead capture, survey analysis, or customer feedback collection.

For example, you can use this node to start a workflow that sends a thank-you email after a form submission, updates a CRM with new contact data, or logs responses into a database.

Properties

Name Meaning
Form The specific Fillout form that will trigger this workflow upon submission. You select it from a dynamically loaded list of available forms in your Fillout account.

Output

The node outputs the data received from the Fillout webhook as JSON. The output contains the form submission details structured as key-value pairs representing the submitted fields and their values.

If the incoming webhook payload is not already an object, the node attempts to parse it as JSON. If parsing fails, it wraps the raw data inside an object under the property rawData.

The output format is:

[
  {
    "field1": "value1",
    "field2": "value2",
    ...
  }
]

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for accessing the Fillout API.
  • Needs network access to receive webhook POST requests from Fillout.
  • The node automatically creates and deletes webhooks on Fillout via its API.
  • The Fillout API base URL and API key must be configured in the credentials used by the node.

Troubleshooting

  • Webhook creation failure: If the node cannot create a webhook on Fillout, ensure the API key is valid and has permissions to manage webhooks. Check network connectivity.
  • Webhook deletion failure: On workflow deactivation or node removal, webhook deletion might fail if the webhook ID is missing or invalid. This usually does not block operation but may leave orphaned webhooks.
  • Invalid webhook payload: If the webhook payload is malformed or not JSON, the node tries to handle it gracefully by wrapping raw data. However, downstream nodes expecting structured data may fail.
  • Error loading forms: When selecting the form, if the list fails to load, verify the API key and internet connection.

Links and References

Discussion