ClickUp logo
Gmail logo

Workflow template

Email new ClickUp tasks with Gmail

Email a fixed recipient when a new task is created in your selected ClickUp Workspaces. FastHook retrieves the task and sends its name, status, creator, List, ID and link through Gmail.

How it works

From a ClickUp task creation to a Gmail notification

1 Trigger · 2 Actions
ClickUp1 · Trigger

Task Created

Receive new taskCreated events from the selected ClickUp Workspaces. The webhook supplies a task ID rather than the full task.

ClickUp2 · Action

Get the new ClickUp task

Retrieve the task’s current name, status, creator, List and URL using the ID in the creation event.

Gmail3 · Action

Email the new ClickUp task

Send a plain-text message to your fixed recipient from the connected Gmail mailbox. Gmail keeps a copy in Sent.

The result

A task notification in the recipient’s inbox

The email contains the fields needed to identify the task and a link to open it in ClickUp.

Example Gmail notification

New ClickUp task: FICTIONAL Hamburg launch

A new ClickUp task was created. Task: FICTIONAL Hamburg launch Status: to do Created by: Mara König List: Fictional launch tasks Task ID: example-task-hamburg-384 Open in ClickUp: https://app.clickup.com/t/example-task-hamburg-384 Task descriptions, comments, and attachments stay in ClickUp.

Fictional task. Receiving the email does not grant access to ClickUp; the recipient needs their own permission to open the task.

Before activation

Set up your workflow

  1. Choose the source Workspaces

    Connect ClickUp and select the source Workspaces in the trigger’s browser. This watches those Workspaces, rather than only the List currently open in ClickUp.

  2. Connect the sender and set a recipient

    Connect Gmail with permission to send mail. Enter a fixed recipient in Email the new ClickUp task and review the prepared subject and body. Start with your own email address.

  3. Activate before creating a task

    Wait until the trigger shows Instant, then create a fictional task in an isolated List within a selected Workspace. Check the recipient’s inbox and the connected mailbox’s Sent folder.

Details and limitations
  • Creation events, rather than synchronization. Only taskCreated events received after activation are handled. Existing tasks, later edits, comments and deletions are excluded. This is a one-way notification, not bulk outreach.

  • The task must remain readable. A task deleted immediately after creation or hidden from the connected account can prevent the lookup and email. Retrieved fields reflect the task when the workflow runs and may include changes made after creation.

  • Limited content, with normal mail delivery rules. Descriptions, Custom Fields, assignees, attachments and comments are not copied. Recipients see the mapped task metadata. Manual reruns or ambiguous provider failures can send duplicate emails; Gmail limits still apply.

Questions about this template

Does this watch only one ClickUp List?

No. The prepared trigger watches the Workspaces you select. The List currently open in ClickUp does not restrict the webhook to that List.

Why is there a Get task step before Gmail?

The task-created event supplies identifiers rather than complete task details. FastHook reads the task to obtain its current name, status, creator, List and link.

Does the email copy descriptions, comments or attachments?

No. It contains name, status, creator, List, task ID and link. Descriptions, Custom Fields, assignees, comments and attachments are not mapped.

Can someone open the task just because they received the email?

No. ClickUp access is checked separately. The recipient needs permission to view the linked task; the email grants no additional access.

Explore connected apps