Skip to main content

Fillout Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Fillout location.
fillout_api.png

Fillout

Create a Fillout Destination​

  1. Click the + icon on the Nexset that will be sent to the Fillout destination, and select the Send to Destination option from the menu.

  2. Select the Fillout connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Fillout account, and click Next; or, create a new Fillout credential for use in this flow.

  3. In Nexla, Fillout destinations can be created using pre-built endpoint templates, which expedite destination setup for common Fillout API write operations. Each template is designed specifically for the corresponding Fillout endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Fillout destinations can also be configured manually, allowing you to send data to Fillout endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Fillout endpoints. Each template is designed specifically for the corresponding Fillout endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create Anonymous Form

    Creates an anonymous form, survey, or quiz in Fillout that can later be claimed by a user. This endpoint is useful for programmatically generating new forms from templates or data in a Nexset — for example, dynamically provisioning intake forms for new clients or projects. After creation, Fillout returns a claim link that the designated owner can use to take ownership of the form.

    • No additional URL parameters are required for this endpoint. Nexla will send the Nexset record data as a JSON body to the Fillout POST /v1/api/forms/anonymous endpoint.
    • Each record in the Nexset will result in one API call to Fillout. Ensure the Nexset schema matches the fields expected by the Fillout anonymous form creation API. Refer to the Fillout API reference for the expected request body structure.
    • The API response from each call — including the form claim link — can be captured and routed to a Nexla webhook source by enabling the Response Webhook option in the manual configuration settings.

    Anonymous forms are not associated with any Fillout account until they are claimed. This makes them suitable for use cases where forms are generated on behalf of third parties or end users who have not yet signed up for Fillout.

    Create Submissions (Import into Form)

    Programmatically creates (imports) one or more submissions into an existing Fillout form. This is the primary write action for any form-data pipeline — use it to migrate historical submission data into Fillout, sync records from external systems, or backfill responses from an offline data collection workflow.

    • Enter the unique identifier of the form into which submissions will be imported in the Form ID field. This value is required.

      • Form IDs can be retrieved using the Fillout List Forms source endpoint, or from the form URL in the Fillout editor at build.fillout.com.
    • Each record in the Nexset will be sent as a submission payload to the Fillout form. Submission payloads must include question field IDs and their corresponding response values. Use the Get Form Metadata source endpoint to retrieve the field IDs for the target form before mapping your data.
    • The Fillout API supports importing up to 10 submissions in a single request. Nexla handles this automatically, but consider using the Record Batching option in the manual configuration to group records into batches of up to 10 for efficient throughput.
    • Once imported, submissions are visible in the Results tab of the form editor in Fillout and are treated identically to manually submitted responses.

    Ensure the field IDs in your Nexset data match the question field IDs in the target Fillout form. Mismatched IDs will result in submissions being created without the expected response data. Run the Get Form Metadata source endpoint first to retrieve the correct field IDs.

    Register Webhook

    Registers a webhook with Fillout so that new form submissions are pushed in real time to a target URL. This endpoint replaces or augments polling-based ingestion pipelines and is ideal when low-latency data delivery is required.

    • Enter the target URL to which Fillout will push new submission payloads in the Webhook URL field. This value is required.

      • The webhook URL must be a publicly accessible HTTPS endpoint. In Nexla, this is typically a Nexla Webhook data source URL that you have already created to receive the incoming payloads.
    • Once registered, Fillout will send a POST request to the specified URL each time a new submission is received for the associated form. The payload format mirrors the response structure of the List Form Submissions source endpoint.

    Fillout webhooks are registered per form. If you need to capture submissions from multiple forms in real time, configure a separate webhook registration for each form. Use the Deregister Webhook endpoint to cleanly remove webhooks when they are no longer needed.

    Deregister Webhook

    Deregisters (removes) an existing Fillout webhook, stopping real-time submission pushes to the previously registered target URL. Use this endpoint for clean lifecycle management when a pipeline is torn down, reconfigured, or the target URL changes.

    • No additional URL parameters are required for this endpoint. Nexla will send the webhook removal request as a JSON body to the Fillout POST /v1/api/webhook/remove endpoint. Ensure the Nexset record includes the form ID and webhook URL (or webhook ID) that should be deregistered — refer to the Fillout webhook API documentation for the expected request body fields.
    • After successful deregistration, Fillout will no longer send submission payloads to the previously registered URL. Confirm that any dependent Nexla webhook sources have been deactivated before removing the registration.

    Delete Submission

    Deletes a specific submission from a Fillout form by its unique submission ID. Use this endpoint for GDPR right-to-erasure workflows, data hygiene pipelines, or when you need to programmatically remove test or duplicate submissions.

    • Enter the unique identifier of the form containing the submission in the Form ID field. This value is required.

      • Form IDs can be retrieved using the List Forms source endpoint.

    • Enter the unique identifier of the submission to be deleted in the Submission ID field. This value is required.

      • Submission IDs are included in the records returned by the List Form Submissions source endpoint and the Fetch Submission by ID source endpoint.
    • Deletion is permanent and cannot be undone. Verify the Submission ID before activating this destination in a production pipeline.

    This endpoint is appropriate for data erasure workflows where you have identified a list of submission IDs to remove — for example, after processing a batch of GDPR deletion requests. Pair it with the List Form Submissions source endpoint to identify the relevant Submission IDs before deletion.

Configure Manually​

Fillout destinations can be manually configured to send data to any valid Fillout API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Fillout API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Fillout API from the Method pulldown menu. Common methods for Fillout destination endpoints include:

    • POST: For creating submissions, registering webhooks, removing webhooks, and creating anonymous forms
    • DELETE: For deleting specific submissions

Data Format​

  1. Select the format in which the Nexset data will be sent to the Fillout API from the Content Format pulldown menu. Fillout's API accepts JSON (application/json) for all write endpoints. Nexla will automatically convert the data to the selected format for each API call.

API Endpoint URL​

  1. Enter the URL of the Fillout API endpoint to which you want to send the Nexset data in the URL field. The Fillout REST API base URL is https://api.fillout.com/v1/api. Common destination endpoint URLs include:
    • Create submissions: https://api.fillout.com/v1/api/forms/{'{formId}'}/submissions
    • Create anonymous form: https://api.fillout.com/v1/api/forms/anonymous
    • Register webhook: https://api.fillout.com/v1/api/webhook/create
    • Deregister webhook: https://api.fillout.com/v1/api/webhook/remove
    • Delete submission: https://api.fillout.com/v1/api/forms/{'{formId}'}/submissions/{'{submissionId}'}

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include the Authorization header here — it is automatically managed by the Fillout credential configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Fillout destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

    The Fillout API supports a maximum of 10 submissions per request for the Create Submissions endpoint. Set the Batch Size to 10 or fewer when using this endpoint to stay within Fillout's API limits.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Fillout API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call — for example, capturing the form claim link returned by the Create Anonymous Form endpoint.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Fillout API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Fillout API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Fillout API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured Fillout endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to Fillout until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.