Clickup Create A Time Entry

• endinteger
  Alias for `stop`. The end time of the time entry, as a Unix timestamp in milliseconds. If both `start` and `end` are provided, the API will use these to determine the entry's actual duration, potentially overriding the `duration` field sent in the request.
• tidstring
  The ID of the task to associate this time entry with. If `custom_task_ids` is `true`, this should be the custom task ID.
• stopinteger
  The stop time of the time entry, as a Unix timestamp in milliseconds. If both `start` and `stop` are provided, the API will use these to determine the entry's actual duration, potentially overriding the `duration` field sent in the request.
• tagsarray
  An array of Tag objects to apply to the time entry. Each Tag object should define 'name' (string), 'tag_fg' (hex color string for foreground), and 'tag_bg' (hex color string for background). This feature is available for users on the ClickUp Business Plan and above.
• startinteger

  Required
  The start time of the time entry, as a Unix timestamp in milliseconds.
• team_Idstring

  Required
  The Workspace ID (also called Team ID in ClickUp API) where the time entry will be added. This goes in the URL path.
• team_idstring
  The ID of the Team, required only if `custom_task_ids` is set to `true`. This specifies the team context for the custom task ID. Example: `custom_task_ids=true&team_id=123`.
• assigneeinteger
  The user ID of the person to assign this time entry to. Workspace owners and admins can assign to any user ID. Workspace members can only assign to their own user ID.
• billableboolean
  Indicates whether the time entry is billable. Set to `true` if billable, `false` or omit if not.
• durationinteger

  Required
  The duration of the time entry in milliseconds. Note: If `start` and `end` (or `stop`) times are also provided in the request, the ClickUp API will calculate the duration based on `start` and `end`/`stop`, and this `duration` field's value might be ignored or overridden by the s…
• descriptionstring
  An optional description for the time entry.
• custom_task_idsboolean
  If `true`, the `tid` parameter will be interpreted as a custom task ID. If this is `true`, the `team_id` query parameter must also be provided to specify the team context for the custom task ID.

• data

  Required
  Data from the action execution
• errorstring
  Error if any occurred during the execution of the action
• successfulboolean

  Required
  Whether or not the action execution was successful or not

No verified related use cases are linked yet.

No published Skills explicitly reference this Action yet.