LanguageENES
ClickUpAvailable on Starter

Turn chatbot leads into ClickUp tasks

The conversation arrives with the task

A lead becomes a task in the list you choose, with its fields mapped to yours. The people who act on it get the context without opening another tool.

What it does

Into the list you pick

Choose the space and the list once. Every routed lead lands there as a task with the name and description you mapped.

Custom fields included

We read the list's custom fields so a lead's email, company or plan lands in the right column rather than in the description.

Retried, then logged

A failed delivery retries on a schedule and stays in the dispatch log with what we sent and what came back.

How to connect it

Read the full guide
  1. 1

    Create a ClickUp API token

    From your ClickUp personal settings. It needs access to the workspace holding the list.

  2. 2

    Connect ClickUp

    In Destinations, paste the token and pick the workspace.

  3. 3

    Create a route

    Pick the space and list, then which leads it takes: one widget, or all of them.

  4. 4

    Map the fields

    Auto-map, then correct anything it guessed wrong.

Questions people ask

Can I send only some leads?

Yes. A route is scoped to a widget, and a widget runs one form -- so the widget asking for a demo opens a task in the sales list while the one asking for support goes somewhere else, or nowhere.

Does it create duplicates?

Each lead is dispatched once. A resend from the dispatch log is deliberate and is the only way a second task appears.

What if the list changes?

The route keeps working against the list id. If a mapped custom field disappears, the dispatch log names it rather than failing silently.

What teams use it for