chatleadr Docs

Send Leads to ClickUp

By the end of this guide a visitor who gives their details on your website has a ClickUp task waiting for whoever follows leads up, in the list you chose, with the conversation summary in the description. A form collects the details, a Function node writes the summary, and one End node sends it.

Send a lead to ClickUp and your dashboard Start FlowStart NodeChatbot TriggerAsk for their detailsForm Input2 Fields ConfiguredSet the summaryFunctionUpdate summaryPush to ClickUpEnd NodeThey closed the formEnd NodeUpdate / Override DataSend to your lead integrations · SuccessNone · Failure
One End node per outcome, which is how a workflow should end. The success End node set to Send to your lead integrations reaches every enabled destination at once, the dashboard included.

Takes about half an hour. Needs a Growth plan or above and a ClickUp account you can generate a token on.

1. Generate a ClickUp Token#

In ClickUp, open the menu on your avatar, then Settings, then Apps. Under API Token, click Generate and then Copy. Personal tokens do not expire, so treat this one as a password: it can read and write everything your ClickUp user can.

2. Connect ClickUp to Your Bot#

Open your bot, then the Lead capture tab, then the gear on the ClickUp Task Creation row of the Automated Lead Tracking card.

ClickUp Task Creation Growth and above ClickUp Task Creation Creates a ClickUp task for each lead, with the name, email and a summary of the chat. Disabled 1. Personal access token Where do I find this? •••••••••••••••••••• Verify 2. Workspace Patio Warehouse 3. Space Sales 4. Target list Create a new list: "Patio Warehouse Chatleadr Leads" Save channel
The ClickUp setup, which walks down your ClickUp hierarchy. The token is verified before the next step appears.

Each control appears once the one before it succeeded.

  1. Paste the token under Personal access token and click Verify. A wrong token stops here with an error rather than failing later.
  2. Choose the Workspace, which ClickUp's own API calls a team.
  3. Choose the Space. An empty list means ClickUp needs a space first.
  4. Choose the Target list, or the option that creates a new list named after your bot.
  5. Click Save channel, which switches the row on.

3. Name the Form Fields the Task Reads#

The task title reads name. The description reads email, phone, summary, url and utm, each showing Not provided when nothing supplied it. Every other field in Lead fields that the visitor answered follows Phone, under the name you gave it and in the order you listed them. A field the visitor did not answer is left out.

Two more lines follow those fields, and no form field sets them: Channel, which names Web Chat, WhatsApp or Instagram, and Came from, which says what brought the visitor in the same words as the leads table. Came from is left out when the lead has no conversation to read, or when nothing more than the channel is known.

Ask for their details Label Email Address Field ID (Variable Name) email Type Email Required Field Validation Preset Email address On WhatsApp and Instagram this form is sent as a secure link. Done
One field inside the Form panel. The Field ID is the variable name, so email fills the Email column and visitor_email does not.

So in the Form node, set the field ids to name, email and phone, and give every other field the same id as its name in Lead fields. Label them however reads best to a visitor. The id rather than the label is what an integration reads. See how a lead is captured.

4. Write the Summary Yourself#

Nothing on the workflow path sets summary, url or utm, so the task tells whoever picks it up nothing about what the visitor wanted. Add a Function node before the End node, set Operation Type to Update / Override Data, and set:

Variable to UpdateValue
summary{{product_interest}} enquiry from the {{channel}} widget

Any {{variables}} in scope can go in the text.

5. Send the Lead From the End Node#

Open the End node on the success path, set Goal Tracking (Optional) to Send to your lead integrations and Completion Status to Success. Leave the row that writes the leads table enabled, which is the default, so the same run writes a row there as well as the ClickUp task. Give the form's Cancelled port its own End node.

Save the workflow. A dialog reading "Saved, but this lead will arrive empty" names any field nothing in the workflow sets, and the workflow saves either way.

6. Test It#

Open your site in a private window, run the workflow through to the end, and check ClickUp. The task appears within a few seconds.

What you seeWhat it means
A task with the visitor's nameWorking
New Lead: Not providedThe Form field id is not name
Summary: Not providedStep 4 was skipped
No task at allSee my lead did not arrive

Common Questions#

Does It Work on WhatsApp and Instagram?#

Yes. On WhatsApp and Instagram the form is delivered as a secure link instead of being rendered in the thread, and the rest is the same.

Can Two Bots Write to Different Lists?#

Yes. Each bot saves its own token and chooses its own list, so two bots can use the same ClickUp token and write to different lists.

What Happens When ClickUp Is Down?#

The task for that lead is not created, and Chatleadr does not try again. A failure does not affect the conversation, and the visitor sees no error.

Can I Change the Task Template?#

Not from the dashboard. To add a line to the description, add the field to Lead fields. To build a task of your own design, call the ClickUp API from an API Request node instead.

Will the Conversation Transcript Be in the Task?#

The summary is. The full transcript stays on the lead record in Chatleadr, which is where the person following up reads it.