Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

TimeOps

Time tracking and project management for teams and freelancers.

CategoryProductivity
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect TimeOps with Flows360

Time tracking and project management for teams and freelancers.

Use the TimeOps 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 6 actions and 4 triggers.

Available actions

  • Create Customer
  • Create Project
  • Start Timer
  • Stop Timer
  • Create Registration
  • Custom API Call

Available triggers

  • New Customer
  • New Project
  • New User
  • New Registration

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: TimeOps
  • Package: @activepieces/piece-time-ops@0.1.0
  • Exact artifact digest: sha256:742caabcc63d2801772592ca6d046c8519c12a0948b12d79b3d0de255d1b6bad
  • 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 Customer (create_customer), Creates a customer. Classification: read.
  • Create Project (create_project), Create a project. Classification: read.
  • Start Timer (start_timer), Starts the timer by creating a new Registration. Classification: read.
  • Stop Timer (stop_timer), Stop the currently running timer. Classification: read.
  • Create Registration (create_registration), Creates a registration. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Customer, polling.
  • New Project, polling.
  • New User, polling.
  • New Registration, polling.

Verification

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

Capability summary

Authenticationcustom
Supported objects10
Supported actions6
Triggers4

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Customer Yes No Creates a customer.
Create Project Yes No Create a project.
Start Timer Yes No Starts the timer by creating a new Registration.
Stop Timer Yes No Stop the currently running timer.
Create Registration Yes No Creates a registration.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Customer Yes No polling trigger declared by the pinned package.
New Project Yes No polling trigger declared by the pinned package.
New User Yes No polling trigger declared by the pinned package.
New Registration Yes No polling trigger declared by the pinned package.

Supported actions

Create Customer · Read

Creates a customer.

create_customer · Risk: low · Retry: safe

Inputs

  • name · string · Optional, The name of the customer.
  • vatNumber · string · Optional, The VAT number of the customer.
  • defaultRate · number · Optional, The default hourly rate for this customer.
Create Project · Read

Create a project.

create_project · Risk: low · Retry: safe

Inputs

  • name · string · Required, The name of the project.
  • customerId · string · Required, The customer this project belongs to.
  • billable · boolean · Optional, Whether the project is billable.
  • rate · number · Optional, The hourly rate for this project.
  • finishedAt · string · Optional, The date and time when the project was finished.
Start Timer · Read

Starts the timer by creating a new Registration.

start_timer · Risk: low · Retry: safe

Inputs

  • userId · string · Required, The user to start the timer for.
  • projectId · string · Optional, The project to associate with this timer.
  • description · string · Optional, Description of the time entry.
  • billable · boolean · Optional, Whether this time entry is billable.
  • tags · array · Optional, Tag IDs to associate with this timer.
Stop Timer · Read

Stop the currently running timer.

stop_timer · Risk: low · Retry: safe

Inputs

  • userId · string · Required, The user to stop the timer for.
Create Registration · Read

Creates a registration.

create_registration · Risk: low · Retry: safe

Inputs

  • userId · string · Required, The user for this registration.
  • startedAt · string · Required, The start date and time of the registration.
  • stoppedAt · string · Optional, The end date and time of the registration.
  • projectId · string · Optional, The project to associate with this registration.
  • description · string · Optional, Description of the registration.
  • billable · boolean · Optional, Whether this registration is billable.
  • tags · array · Optional, Tag IDs to associate with this registration.
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 Customer · Poll

Triggers when a new customer is created.

New Project · Poll

Triggers when a new project is created.

New User · Poll

Triggers when a new user has been created.

New Registration · Poll

Triggers when new registrations are added.

Setup

Setup

  1. Add the TimeOps 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-time-ops@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 4 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 TimeOps 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-time-ops@0.1.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