Latenode

Automatically log Teamwork time entries from Google Calendar events

This template starts when a Google Calendar event ends, computes minutes from the start and end times, and logs that duration in Teamwork.

Put a task or project id in the event description, or set a default on the Teamwork step. Connect Google Calendar and Teamwork, then point the trigger at the calendar you track.

Updated Sep 16, 2026Est. run: 8sEst. cost: $0.0005
How Latenode estimates time and cost

Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how CPU seconds work →

Workflow preview

What this template does

  • Logs Teamwork time when a calendar event ends
  • Uses the Google Calendar ended-event trigger as the signal
  • Writes time on a Teamwork task or project
  • Computes duration in JavaScript from start and end

How it works

1
Trigger

Event ended

The scenario starts when an event on the connected Google Calendar finishes.

2
Logic

Compute duration and ids

JavaScript turns start and end into minutes or hours and reads a Teamwork task or project id from the description, or uses the default id you configured.

3
Action

Create the time entry

Teamwork logs time against that task. If you only have a project id, log time on the project instead. Map the event title into the time-entry notes.

Setup guide

1

Connect Google Calendar

Add a Google Calendar connection and point the ended-event trigger at the calendar you track.

2

Connect Teamwork

Add a Teamwork connection with permission to create time entries.

3

Decide task vs project

Put a Teamwork task id in the event description if you bill tasks. Otherwise set a default project id and log time on the project. JavaScript should stop if neither id is present.

4

Map duration

Compute minutes from start and end, then map them into the Teamwork time-entry fields. End a test event and confirm the entry in Teamwork.

Requirements

A Google Calendar Latenode can read
A Teamwork account that can create time entries
A default Teamwork project or task id, or ids written into event descriptions

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.