Latenode

Automatically sync Zoom registration data and add-to-calendar links

This template runs when Zoom posts a new meeting registrant. JavaScript reads name, email, and meeting time, builds an add-to-calendar URL, and shapes the event.

Google Calendar creates the event with that attendee. Latenode Database stores email, meeting id, and the link. Connect Google Calendar. Point Zoom registrant webhooks at a Latenode webhook.

Updated Sep 16, 2026Est. run: 16sEst. cost: $0.001
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 new Zoom registrants into calendar invites
  • Creates the event on Google Calendar with the attendee
  • Stores an add-to-calendar URL in Latenode Database
  • Starts from a Zoom webhook

How it works

1
Trigger

Receive the Zoom registrant

A webhook starts the scenario when Zoom posts a new meeting registrant.

2
Logic

Build the calendar payload

JavaScript maps name, email, start, and join URL, and builds an add-to-calendar link.

3
Action

Create the Google Calendar event

Google Calendar creates the event and adds the registrant as an attendee.

4
Action

Store the link

Latenode Database saves email, meeting id, and the add-to-calendar URL.

Setup guide

1

Add the webhook

Add a webhook trigger and copy the URL into Zoom event subscriptions for new meeting registrants.

2

Connect Google Calendar

Add a Google Calendar connection for the calendar that should receive the event.

3

Create the Database table

In Latenode Database, create a table with columns for email, meeting id, start time, and add-to-calendar URL.

4

Map and write

Parse the Zoom payload in JavaScript, create the Google Calendar event with the registrant as attendee, then create a Database object. Send a test registration and confirm the invite and row.

Requirements

A Zoom account that can post registrant webhooks
A Google Calendar Latenode can write
A Latenode Database table for registrant rows

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.