AFI AFI

ClickUp

Estimated reading: 2 minutes Updated August 1, 2026

ClickUp is a fast-growing productivity and project-management platform. Advanced Form Integration creates a new ClickUp task for every form submission, useful for routing leads, support tickets, or client requests into your team’s workspace.

What you’ll need

  • An active ClickUp account.
  • A ClickUp API token.
  • The Advanced Form Integration plugin installed and activated.

Get your ClickUp API token

  1. Log in to ClickUp.
  2. Click your avatar (top right) → Settings.
  3. Open the Apps tab.
  4. Under API Token, click Generate.
  5. Copy the token (starts with pk_).

Connect ClickUp to AFI

  1. In WordPress, go to AFI → Settings → ClickUp.
  2. Paste the API Token and click Save Changes.

Create the integration

  1. Go to AFI → Add New.
  2. Configure the trigger.
  3. In Action → Platform, select ClickUp.
  4. In Task, choose Create Task.
  5. Pick the Workspace, Space, Folder/List from the dropdowns.
  6. Map the form fields to ClickUp task properties:
  • Name (required): the task title.
  • Description: task body.
  • Assignees: comma-separated ClickUp user IDs.
  • Due date: YYYY-MM-DD (ClickUp converts to Unix timestamp).
  • Priority: 1 Urgent, 2 High, 3 Normal, 4 Low.
  1. Optional: configure Conditional Logic.
  2. Click Save Integration.

Screenshot: AFI field-mapping screen with ClickUp task fields visible

Tasks supported

Create Task

Adds a new task to the chosen list. Custom fields defined on the list also appear in the mapping dropdown.

Conditional logic example

Goal: when a support form’s Severity is Critical, create the ClickUp task with priority Urgent in the on-call list. Lower severities go to the standard backlog.

Create two integrations on the same form, each pointing at a different list and priority. Add the matching Equal To condition on each.

Troubleshooting

Task not created

Common ClickUp API errors:

  • Authorization header missing or OAUTH_001: token is wrong or revoked. Re-generate.
  • List not found: wrong list ID, or the token’s user doesn’t have access.
  • Field not found: custom field was renamed. Re-pick the list to refresh.

Custom field mapping issue

ClickUp custom fields use IDs internally. AFI shows them by name, but rapid renames in ClickUp may take a few seconds to propagate. Re-pick the list if a freshly renamed custom field doesn’t appear.

Related docs