Skip to main content

Create Google Calendar events from labeled Gmail confirmations with easybits Extractor

Workflow preview

Workflow preview
100%
Create Google Calendar events from labeled Gmail confirmations with easybits Extractor preview
Open on n8n.io

1. Workflow Overview

Quick overview This workflow monitors labeled Gmail messages, uses easybits Extractor to pull event details from the email body and any PDF/image attachments, and either creates a Google Calendar e...

Best for

  • Document Extraction automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.gmailtrigger, n8n-nodes-base.code, @easybits/n8n-nodes-extractor.easybitsextractor, n8n-nodes-base.if, n8n-nodes-base.set, n8n-nodes-base.googlecalendar, n8n-nodes-base.gmail, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Felix.

Original n8n.io source

1.1 Workflow description

Title
Create Google Calendar events from labeled Gmail confirmations with easybits Extractor
Workflow name
Create Google Calendar events from labeled Gmail confirmations with easybits Extractor

Quick overview

This workflow monitors labeled Gmail messages, uses easybits Extractor to pull event details from the email body and any PDF/image attachments, and either creates a Google Calendar event or labels the email for review and sends you a notification.

How it works

  1. Polls Gmail every minute for new emails that have the specified “Events” label and downloads any attachments.
  2. Renders the email subject, sender, date, and body into a minimal PDF and sends it to easybits Extractor to extract structured event fields.
  3. Splits PDF/image attachments into separate items and sends each one to easybits Extractor to extract the same event fields.
  4. Merges the extracted results, prioritizing attachment data over email-body data and filling missing fields from the body when needed.
  5. Validates that required fields (at least start_datetime and event_type) are present.
  6. If valid, creates a Google Calendar event with the extracted title, start/end time, location, and a formatted description, then removes the “Events” label from the email.
  7. If invalid, adds a “Needs-Review” label, removes the “Events” label, and sends you an HTML email listing missing fields and what was extracted.

Setup

  1. Connect Gmail OAuth2 credentials for the Gmail Trigger and Gmail actions, and update the Events label ID, Needs-Review label ID, and review recipient email address.
  2. Install and configure the easybits Extractor community node (@easybits/n8n-nodes-extractor) and add your easybits Extractor API key and Pipeline ID to both Extractor steps.
  3. Connect Google Calendar OAuth2 credentials and replace the target calendar ID with your calendar (or create a dedicated “Auto-imported” calendar and select it).
  4. Create the Gmail labels used by the workflow (for example, Events and Events/Needs-Review) and apply the Events label to test emails you want turned into calendar events.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Gmail Trigger

Type / Role
n8n-nodes-base.gmailTrigger - gmailTrigger
Config choices
Version 1.3

Block 2 - Code: Email Body Preparation

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 3 - Extractor: Email Body

Type / Role
@easybits/n8n-nodes-extractor.easybitsExtractor - easybitsExtractor
Config choices
Version 2

Block 4 - If: Valid Event?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 5 - Set: Build Event Description

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 6 - Calendar: Create Event

Type / Role
n8n-nodes-base.googleCalendar - googleCalendar
Config choices
Version 1.3

Block 7 - Gmail: Remove Events Label

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

Block 8 - Code: Explode Attachments

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 9 - Extractor: Attachment

Type / Role
@easybits/n8n-nodes-extractor.easybitsExtractor - easybitsExtractor
Config choices
Version 2

Block 10 - Code: Merge Extractions

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 11 - Gmail: Flag for Review

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

Block 12 - Gmail: Remove Events Label (Review Path)

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

Block 13 - Gmail: Send Review Notification

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.2

Block 14 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Sticky Note7

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Sticky Note8

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Sticky Note9

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Sticky Note10

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 27 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Create Google Calendar events from labeled Gmail confirmations with easybits Extractor
Complexity advanced
Nodes 27
Categories Document Extraction, AI Summarization
Author Felix
Published 03 Jun 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/16097/16097.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Create Google Calendar events from labeled Gmail confirmations with easybits Extractor do?

Quick overview This workflow monitors labeled Gmail messages, uses easybits Extractor to pull event details from the email body and any PDF/image attachments, and either creates a Google Calendar e...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction, AI Summarization use case.