Shipfox

ClickUp events

Look up the ClickUp task and comment events Shipfox delivers and the payload fields available to workflows.

This reference lists ClickUp task and comment events that Shipfox delivers to a ClickUp integration connection. See the ClickUp overview for authentication and access boundaries.

Payload

ClickUp webhook payloads are thin. They identify the task and describe its change, but they do not contain the complete current task.

Shipfox validates the ClickUp webhook envelope and adds team_id for the configured ClickUp workspace. The event value exposes these fields:

FieldDescription
eventThe ClickUp event name.
webhook_idThe ClickUp webhook that delivered the event.
task_idThe affected ClickUp task ID.
history_itemsChange records supplied by ClickUp, when the event includes them.
team_idThe configured ClickUp workspace ID, added by Shipfox.

Each history item can include its ID, type, date, field, parent List ID, source, actor, and before and after values. Comment events also include the ClickUp comment object.

See ClickUp's webhook reference and task webhook payloads for provider-owned field details.

Control access and prevent repeated runs

Shipfox receives events only for ClickUp items the connected account can access. Give the service account access to every Space, Folder, and List your workflows should monitor.

ClickUp sends a new event when Shipfox updates a task. If that event matches the workflow's trigger, the workflow runs again and may repeat the update. To prevent repeated runs, add a trigger filter that ignores changes made by the Shipfox service account or matches only fields the workflow does not update.

Paired deliveries

One ClickUp action can produce more than one delivered event:

  • taskCreated is also delivered as taskStatusUpdated.
  • taskStatusUpdated, taskAssigneeUpdated, taskPriorityUpdated, taskDueDateUpdated, and taskTagUpdated are also delivered as taskUpdated.

A source-only trigger can therefore start more than one run for one user action. Match the specific event name when the workflow needs one change type.

Trigger fragment

Replace clickup_acme with the slug of your ClickUp integration connection:

triggers:
  on_clickup_comment:
    source: clickup_acme
    event: taskCommentPosted

For trigger field rules, see the workflow schema reference.

Event catalog

taskCreated

A ClickUp task is created.

Emitted when: ClickUp sends a taskCreated webhook.

Payload: Shipfox-normalized payload.

taskUpdated

A ClickUp task changes.

Emitted when: ClickUp sends a taskUpdated webhook.

Payload: Shipfox-normalized payload.

taskDeleted

A ClickUp task is deleted.

Emitted when: ClickUp sends a taskDeleted webhook.

Payload: Shipfox-normalized payload.

taskMoved

A ClickUp task is moved.

Emitted when: ClickUp sends a taskMoved webhook.

Payload: Shipfox-normalized payload.

taskStatusUpdated

A ClickUp task status changes.

Emitted when: ClickUp sends a taskStatusUpdated webhook.

Payload: Shipfox-normalized payload.

taskAssigneeUpdated

A ClickUp task assignee changes.

Emitted when: ClickUp sends a taskAssigneeUpdated webhook.

Payload: Shipfox-normalized payload.

taskPriorityUpdated

A ClickUp task priority changes.

Emitted when: ClickUp sends a taskPriorityUpdated webhook.

Payload: Shipfox-normalized payload.

taskDueDateUpdated

A ClickUp task due date changes.

Emitted when: ClickUp sends a taskDueDateUpdated webhook.

Payload: Shipfox-normalized payload.

taskTagUpdated

A ClickUp task tag changes.

Emitted when: ClickUp sends a taskTagUpdated webhook.

Payload: Shipfox-normalized payload.

taskCommentPosted

A comment is posted on a ClickUp task.

Emitted when: ClickUp sends a taskCommentPosted webhook.

Payload: Shipfox-normalized payload.

taskCommentUpdated

A comment on a ClickUp task changes.

Emitted when: ClickUp sends a taskCommentUpdated webhook.

Payload: Shipfox-normalized payload.

Was this page helpful?
Edit this page on GitHub

On this page