n8n-ai calendar sync

Use and limitations

Terms of use

Last updated November 13, 2026

These terms describe the personal calendar-sync integration operated by Zach Rideout using the n8n-ai Google OAuth app. The integration is a private automation for the owner’s account.

1. What the integration does

The integration reads forwarded meeting invitations and calendar snapshots from a configured Gmail label, applies their changes to a selected Google calendar, and keeps local processing records and a message archive.

These terms apply to the personal calendar-sync integration authorized as n8n-ai. This website provides information; it offers no public registration, subscription, or payment service.

2. Permission to use source information

The person configuring the integration must have permission to access the source messages and calendar information, forward them through the chosen services, copy them to the destination calendar, and retain any local archive.

Using the integration does not grant permission to disclose someone else’s information or override an employer’s, organization’s, or service provider’s rules. Google access is subject to the account’s permissions and Google’s terms.

3. Review calendar changes

Calendar sync depends on the messages and snapshots it receives and on third-party services being available. Forwarding gaps, expired authorization, parsing errors, or changes to a source event can delay or affect an update.

Review important meeting times, cancellations, and joining details against the original source calendar. The copied calendar should not be the only record used for a time-critical commitment.

4. Availability and changes

This is a personal automation without a guaranteed uptime, sync speed, completeness, or support response time. The operator may change or stop the integration as its needs or connected services change.

Copies already created can remain after the service stops. The owner is responsible for reviewing the destination calendar and managing local records and backups.

5. Data handling and controls

The privacy policy explains the information accessed, its uses, storage locations, retention, and deletion controls. The local archive can contain full messages and attachments, including messages without calendar content.

The account owner can stop the integration and revoke its Google authorization. Gmail app-password access is managed separately. Revocation does not delete original messages, copied calendar events, or local data and backups; those require separate removal.

6. Contact and updates

Questions about this integration, its data handling, or these terms can be sent to zrides@gmail.com. Updates will be reflected in these pages and their last-updated date.

Operator: Zach Rideout