Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Clockify

Clockify integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Clockify with Flows360

Clockify integration for Flows360 workflows.

Use the Clockify connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and 3 triggers.

Available actions

  • Create Task
  • Create Time Entry
  • Start Timer
  • Stop Timer
  • Find Task
  • Find Time Entry
  • Find Running Timer
  • Custom API Call

Available triggers

  • New Task
  • New Time Entry
  • New Timer Started

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Clockify
  • Package: @activepieces/piece-clockify@0.2.0
  • Exact artifact digest: sha256:5b9851c1367bc679eb93b1f8e045234542317087f927a1e70ae2a4bdf9d60743
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Task (create-task), Creates a new in a specific project. Classification: read.
  • Create Time Entry (create-time-entry), Creates a new time entry. Classification: read.
  • Start Timer (start-timer), Starts a new time entry. Classification: read.
  • Stop Timer (stop-timer), Stops currently running timer on specified workspace. Classification: read.
  • Find Task (find-task), Finds an existing task in a specific project. Classification: read.
  • Find Time Entry (find-time-entry), Finds a time entry by description, start datetime or end datetime. Classification: read.
  • Find Running Timer (find-running-timer), Finds currently running timer on specified workspace. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Task, webhook.
  • New Time Entry, webhook.
  • New Timer Started, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects11
Supported actions8
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Task Yes No Creates a new in a specific project.
Create Time Entry Yes No Creates a new time entry.
Start Timer Yes No Starts a new time entry.
Stop Timer Yes No Stops currently running timer on specified workspace.
Find Task Yes No Finds an existing task in a specific project.
Find Time Entry Yes No Finds a time entry by description, start datetime or end datetime.
Find Running Timer Yes No Finds currently running timer on specified workspace.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Task Yes No webhook trigger declared by the pinned package.
New Time Entry Yes No webhook trigger declared by the pinned package.
New Timer Started Yes No webhook trigger declared by the pinned package.

Supported actions

Create Task · Read

Creates a new in a specific project.

create_task · Risk: low · Retry: safe

Inputs

  • workspaceId · string · Required
  • projectId · string · Required
  • name · string · Required
  • status · string · Optional
  • assigneeIds · array · Optional
Create Time Entry · Read

Creates a new time entry.

create_time_entry · Risk: low · Retry: safe

Inputs

  • workspaceId · string · Required
  • start · string · Required
  • end · string · Required
  • description · string · Optional
  • projectId · string · Optional
  • taskId · string · Optional
  • billable · boolean · Optional
  • tagIds · array · Optional
Start Timer · Read

Starts a new time entry.

start_timer · Risk: low · Retry: safe

Inputs

  • workspaceId · string · Required
  • description · string · Optional
  • projectId · string · Optional
  • taskId · string · Optional
  • billable · boolean · Optional
  • tagIds · array · Optional
Stop Timer · Read

Stops currently running timer on specified workspace.

stop_timer · Risk: low · Retry: safe

Inputs

  • workspaceId · string · Required
Find Task · Read

Finds an existing task in a specific project.

find_task · Risk: low · Retry: safe

Inputs

  • workspaceId · string · Required
  • projectId · string · Required
  • name · string · Required
  • exactMatch · boolean · Optional
Find Time Entry · Read

Finds a time entry by description, start datetime or end datetime.

find_time_entry · Risk: low · Retry: safe

Inputs

  • workspaceId · string · Required
  • start · string · Optional
  • end · string · Optional
  • description · string · Optional
  • projectId · string · Optional
  • taskId · string · Optional
Find Running Timer · Read

Finds currently running timer on specified workspace.

find_running_timer · Risk: low · Retry: safe

Inputs

  • workspaceId · string · Required
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Task · Webhook

Triggers when a new task is created in specified project.

Inputs

  • workspaceId · string
  • projectId · string
New Time Entry · Webhook

Triggers when a new time entry is created.

Inputs

  • workspaceId · string
  • projectId · string
  • taskId · string
New Timer Started · Webhook

Triggers when a new entry is started and running.

Inputs

  • workspaceId · string

Setup

Setup

  1. Add the Clockify connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-clockify@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Clockify connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-clockify@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com