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.
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.
Each control appears once the one before it succeeded.
- Paste the token under Personal access token and click Verify. A wrong token stops here with an error rather than failing later.
- Choose the Workspace, which ClickUp's own API calls a team.
- Choose the Space. An empty list means ClickUp needs a space first.
- Choose the Target list, or the option that creates a new list named after your bot.
- Click Save channel, which switches the row on.
3. Name the Form Fields the Task Reads#
A ClickUp task is built from a fixed template: the title reads name, and the description reads email, summary, url and utm. Anything unset arrives as Not provided.
So in the Form node, set the field ids to name, email and phone, and 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 Update | Value |
|---|---|
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 see | What it means |
|---|---|
| A task with the visitor's name | Working |
New Lead: Not provided | The Form field id is not name |
Summary: Not provided | Step 4 was skipped |
| No task at all | See 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 send is queued and retried. A failure does not affect the conversation, which has already ended by the time the task is created.
Can I Change the Task Template?#
Not from the dashboard. The title and description come from a fixed system template. 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.