Connect Google Calendar to Crowdin

When something happens in Google Calendar, Notis takes the next step in Crowdin. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Google Calendar to Crowdin

View example

Create a Crowdin branch for a scheduled feature

When a feature kickoff appears on Google Calendar, create a matching branch in Crowdin to keep its localization work separate.

View example

Label localization work from a calendar kickoff

Create a Crowdin label when a new calendar event marks a release or feature milestone, making related translation work easier to identify.

View example

Open a Crowdin branch when a launch date changes

When an existing calendar event changes, create a Crowdin branch for the newly planned launch or release when a separate localization workstream is needed.

View example

Add a Crowdin webhook after a review is confirmed

When an attendee accepts a localization review meeting, create a Crowdin webhook for the project's configured events.

View example

Check Crowdin reports before a localization meeting

Before a scheduled localization meeting begins, retrieve the project's available Crowdin reports so you can review what is ready to discuss.

View example

Clean up a Crowdin branch when a release is canceled

When a calendar event for a planned release is canceled, delete its corresponding Crowdin branch after the cancellation is confirmed as obsolete.

View example

Prepare Crowdin notifications for a new project kickoff

When a new project kickoff is scheduled, create the specified Crowdin webhook so localization notifications are ready for the project.

View example

Review Crowdin files before a scheduled content session

Use full calendar event details to identify a content or localization session and retrieve the relevant Crowdin project files for review.

View example

Review Crowdin project members when a reviewer responds

When a localization review attendee responds, retrieve the Crowdin project member list to help confirm who is involved in the project.

Supported Triggers and Actions

Notis builds workflows that link Google Calendar to Crowdin. A trigger fires from one place; an action lands in another.

Google Calendar triggers

Crowdin actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add Branch

Tool to create a new branch in a crowdin project. use when you need to isolate translations for a new feature or release.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add File

Tool to add a new file to a crowdin project. use after uploading the file to storage to place it under the specified project, branch, or directory.

ActionInstant

Attendee Response Changed

Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.

TriggerPolling

Add Label

Tool to create a new label in a crowdin project. use when you need to tag resources with a custom identifier, such as 'sprint-5'.

ActionInstant

Event Canceled or Deleted

Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp.

TriggerPolling

Create Crowdin Project

Tool to create a new project in crowdin. use before uploading source files to initialize translation workflows.

ActionInstant

Event Starting Soon

Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available.

TriggerPolling

Add Webhook

Tool to create a new webhook in a crowdin project. use after confirming the project id and desired event triggers.

ActionInstant

Calendar Event Changes

**SOON TO BE DEPRECATED** - Use Calendar Event Sync (polling trigger) instead. Real-time webhook trigger for calendar event changes. Returns event metadata only. For full event data, use Calendar Event Sync (polling trigger).

TriggerInstant

Assign Label to Strings

Tool to assign the specified label to provided string ids in a project. use after creating the label or verifying string ids to categorize content.

ActionInstant

Event Created

Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.

TriggerPolling

Delete Branch

Tool to delete a specific branch from a crowdin project. use when you need to remove an obsolete branch after it's fully merged.

ActionInstant

Calendar Event Sync

Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook).

TriggerPolling

Delete Label

Tool to delete the label identified by the specified label id in a project. use when you need to remove outdated or incorrect labels. ensure no resources reference the label before deletion.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.