We use the Fillout → ClickUp integration to automatically create ClickUp tasks from form submissions.

We recently redesigned our ClickUp workflow to use different Task Types, with each Task Type having its own set of Custom Fields. We need Fillout to populate those Custom Fields when the task is created.

The issue is that the Fillout integration currently creates every task using the default Task Type. Because of this, only the Custom Fields associated with the default Task Type are available at the moment of creation.

If we change the Task Type afterward using a ClickUp Automation or apply a Task Template, the correct Custom Fields can be added to the task, but Fillout cannot populate them retroactively because those fields did not exist when the task was originally created.

We tested several workarounds, including:

Changing the Task Type through a ClickUp Automation.

Using a Text Custom Field from Fillout as a trigger.

Applying a Task Template through an Automation.

Using the Task Type associated with the Template.

These approaches can change the Task Type and/or add the Custom Fields afterward, but they cannot solve the core issue because Fillout can only populate Custom Fields that already exist when the task is created.

##### Requested feature

We would like Task Type to be available as a configurable/mappable field in the Fillout → ClickUp integration.

Ideally, the workflow would be:

Fillout submission → determine Task Type → create ClickUp task with that Task Type → populate the Custom Fields associated with that Task Type

For example, if a Fillout submission indicates that the task should be “Bug,” the integration would create the task as the “Bug” Task Type from the beginning. This would make all of the Custom Fields associated with that Task Type available before Fillout attempts to populate them.

This functionality would allow users to build more advanced workflows where different form submissions create different ClickUp Task Types, each with their own Custom Fields.

At the moment, there does not appear to be a native workaround for this use case because changing the Task Type or adding the Custom Fields after task creation happens too late for the Fillout integration to populate them.

Please consider adding Task Type as a supported field in the Fillout → ClickUp integration.