Connect Clockify to Transport for The Netherlands

Both apps 38Clockify 31Transport for The Netherlands 7

• Trigger
  New Client

  Triggers when a new client is added to a workspace.

• Trigger
  New Project

  Triggers when a new project is added to a workspace.

• Trigger
  New Tag

  Triggers when a new tag is added to a workspace.

• Trigger
  New Task

  Triggers when a new task is added to a project on a specified workspace.

• Trigger
  New Time Entry

  Triggers when a new time entry is added.

• Trigger
  New Timer Started

  Triggers when a new entry is started and running.

• Trigger
  New Workspace

  Triggers when a new workspace is created.

• Action
  Create Client

  Creates a client on a specified workspace.

• Action
  Create Project

  Creates a project on a specified workspace.

• Action
  Create Tag

  Creates a tag on a specified workspace.

• Action
  Create Task

  Creates a task on a specified project.

• Action
  Create Time Entry

  Creates a new time entry on a specified workspace.

• Action
  Delete Client

  Delete a client from a workspace. DELETE /v1/workspaces/{workspaceId}/clients/{id}

• Action
  Delete Project

  Delete a project from a workspace. DELETE /v1/workspaces/{workspaceId}/projects/{projectId}

• Action
  Delete Tag

  Delete a tag from a workspace. DELETE /v1/workspaces/{workspaceId}/tags/{id}

• Action
  Delete Task

  Delete a task from a project. DELETE /v1/workspaces/{workspaceId}/projects/{projectId}/tasks/{taskId}

• Action
  Delete Time Entry

  Delete a time entry from a workspace. DELETE /v1/workspaces/{workspaceId}/time-entries/{id}

• Action
  Find Client

  Finds a client by name on a specified workspace.

• Action
  Find Project

  Finds a project by name on a specified workspace.

• Action
  Find Running Timer

  Finds a currently running time entry on a specified workspace.

• Action
  Find Tag

  Finds a tag on a specified workspace.

• Action
  Find Task

  Finds a task by name on a specified project and workspace.

• Action
  Find Time Entry

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

• Action
  List Workspaces

  List all workspaces the authenticated user belongs to. GET /v1/workspaces

• Action
  Start Timer

  Starts a new time entry.

• Action
  Stop Timer

  Stops currently running time entry on a specified workspace.

• Action
  Update Client

  Update a client's name/note/archived status. PUT /v1/workspaces/{workspaceId}/clients/{id}

• Action
  Update Project

  Update a project's name/color/client/billable status/dates. PUT /v1/workspaces/{workspaceId}/projects/{projectId}

• Action
  Update Tag

  Update a tag's name/archived status on a workspace. PUT /v1/workspaces/{workspaceId}/tags/{id}

• Action
  Update Task

  Update a task's name/status/assignee/estimate on a project. PUT /v1/workspaces/{workspaceId}/projects/{projectId}/tasks/{taskId}

• Action
  Update Time Entry

  Update a time entry's start/end/description/project/task/billable/tags on a workspace. PUT /v1/workspaces/{workspaceId}/time-entries/{id}

• Action
  Find passtimes by line

  Get the expected and real-time arrival/departure passtimes for all timing points served by one or more transit lines.

• Action
  Find passtimes by stop area

  Get the expected and real-time arrival/departure passtimes for all timing points within one or more stop areas.

• Action
  Find passtimes by timing point

  Get the expected and real-time arrival/departure passtimes for one or more timing points, identified by their timing point code.

• Action
  List journeys

  List the keys of currently planned or driving vehicle journeys, with the number of stops in each journey.

• Action
  List lines

  List all transit lines known to the OVAPI, with data owner code, line planning number, direction, and optionally line name/public number/transport type/destination.

• Action
  List stop areas

  List all stop areas (groups of nearby timing points sharing one traveler-facing stop name) known to the OVAPI, with position, name, and town.

• Action
  List timing points

  List all timing point codes (bus stops, tram/train stops, and virtual points) known to the OVAPI within its current uptime.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.