Latenode

Sync Google Calendar events to generate OmniFocus tasks

This template watches Google Calendar for new or changed events and creates an OmniFocus task from each one.

JavaScript sends the event title, start time, and notes to OmniFocus with your OmniFocus API token or Mail Drop address in that node. Connect Google Calendar, pick the calendar, and put OmniFocus access in the JavaScript node.

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

  • Turns Google Calendar events into OmniFocus tasks
  • Starts when an event is created or changed
  • Creates each task through JavaScript
  • Keeps the OmniFocus token or Mail Drop address in the JavaScript node

How it works

1
Trigger

Watch Google Calendar

The scenario starts when an event is created or changed on the calendar you connect.

2
Action

Create the OmniFocus task

JavaScript creates the task using the API token or Mail Drop address stored in that node. Set the name from the event title and put start time and location in the note.

Setup guide

1

Connect Google Calendar

Add a Google Calendar connection. Add a trigger for new or changed events and choose the calendar to watch.

2

Store OmniFocus access

Add a JavaScript node and put your OmniFocus API token or Mail Drop address there.

3

Map event to task

In JavaScript, set the task name from the event title. Put start time, location, and description in the note. Skip cancelled events in the same node if they should not become tasks.

Requirements

A Google Calendar Latenode can read via a Google Calendar connection
An OmniFocus API token or Mail Drop address stored in the JavaScript node
A rule for which events become tasks, such as skipping cancelled events

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.