H
Hervé Hamon
Category:
Automation / API & Integrations
Context and Problem Statement:
Our users rely on automated workflows to efficiently manage the creation of ClickUp tasks from external sources, primarily incoming emails.
A common workflow involves creating a new ClickUp task via the API and automatically populating its fields by extracting data from the source email.
The critical final step is ensuring the full original email thread is logged into the task's 'Activity' panel. To achieve this, the original email must be forwarded to the task’s unique
“send-to-task” email address
. To maintain a clean and efficient workflow, this forwarding action should preferably be executed
without including the attachments
, as they are often handled by other automation steps.
Currently, the ClickUp API does not provide a direct way to programmatically retrieve this unique “send-to-task” address for a task
immediately after its creation
. This lack of access forces a manual, time-consuming step where the user has to copy the address from the task interface, which defeats the goal of full automation.
Proposed Feature Enhancement:
We propose updating the ClickUp API to allow programmatic retrieval of the unique, per-task “send-to-task” email address. This is essential for achieving a true end-to-end automated workflow for task creation from external sources like email.
We suggest two main options for implementing this access:
  1. Include in Creation Response:
    Modify the task creation API endpoint so that the unique "send-to-task" email address is immediately included in the response message/object returned upon successful creation of the new task.
  2. Dedicated API Retrieval Function:
    Implement a new API function that allows users to query and retrieve the unique "send-to-task" email address for any task by using its unique identifier (Task ID). This would be used if the address is not immediately available in the creation response.
Either of these solutions would enable full, seamless automation of the following critical workflow:
  1. Script/Integration:
    Creates new ClickUp task via API.
  2. API Response/Query:
    Retrieves the unique "send-to-task" email address (via option 1 or 2).
  3. Script/Integration:
    Immediately forwards the body of the original source email to the retrieved “send-to-task” email address,
    excluding attachments
    .