• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

    🚀 Exclusive Lifetime Offers 🚀

    We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:

    • 🔥 Pabbly Connect — Lifetime Access for $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer
    • 🔥 Pabbly Chatflow — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

Create a task in Clickup from Go High Level, using Pabbly Connect.

Status
Not open for further replies.
Your Task History ID
IjU3NjUwNTY4MDYzNjA0MzI1MjY1NTUzMDUxMzE1MTYzNTQzNzBmMzQi_pc
Hello, Pabbly team. I followed a step-by-step tutorial you posted on YouTube
to create a new task in Clickup from a new task in Go High Level using Pabbly Connect.

Specifically, I want that when I create a new task in Go High Level, the task is automatically created in a specific list in my ClickUp.

However, I am getting the following error:

Err

Task name invalid


ECODE

INPUT_005



I have tried many different things, but I cannot get this automation to work.



I am sharing my screenshots with you, and I hope you can help me find the error so I can fix it.



Best regards, I look forward to your response.

1 Workflow.png
2 Webhook response succesful.png
3 Date time formerly.png
4 Mapping.png
5 Error.png
6 Task created in Go High level - Evergrowth.png
7 Task no created in ClickUp.png
 

ArshilAhmad

Moderator
Staff member
Hi @Enfoque Visionario,

In the Assignee ID field of the ClickUp: Create Task action step, you cannot directly pass the email address of the assignee. You need to map the ID associated with the assignee instead.
1750792950875.png



We have added a Lookup Table to your workflow that provides the assignee ID when given an email address. We then mapped this ID to the ClickUp action step, and it appears to have resolved the issue.


You can add multiple email addresses along with their corresponding assignee IDs to the Lookup Table. Each time it receives an email address, it will return the associated Assignee ID.

1750792514401.png



 
Status
Not open for further replies.
Top