Turn booking confirmation emails into calendar events
An n8n workflow extracts details from booking emails and PDF attachments and creates calendar events in a dedicated calendar, built for a CEO's flooded inbox. Task: Suggested implementation: An n8n workflow monitors Gmail for messages labeled "Events". It extracts date, time, location, confirmation number, vendor, and notes from the email body and PDF attachments. The email body is converted to PDF, then both sources are parsed in parallel and merged. A human must initially label the email to trigger the process.; tools: n8n. Human role: The source evidence is unavailable for specific human roles beyond the initial labeling step.; limitations: Prerequisites include Gmail and Calendar API access in n8n. The workflow relies on manual labeling of emails, which is a bottleneck. Integration uncertainty exists regarding PDF parsing accuracy for varied vendor formats. Human approval is required for final calendar entries if auto-creation is disabled..
Tools
Published on Agent Work Atlas:
Overview
An n8n workflow extracts details from booking emails and PDF attachments and creates calendar events in a dedicated calendar, built for a CEO's flooded inbox.
Workflow
Suggested implementation: An n8n workflow monitors Gmail for messages labeled "Events". It extracts date, time, location, confirmation number, vendor, and notes from the email body and PDF attachments. The email body is converted to PDF, then both sources are parsed in parallel and merged. A human must initially label the email to trigger the process.
Reported result
Actual outcomes are unknown as the source is inaccessible. Proposed acceptance check: Verify that 100% of labeled emails result in a calendar event with correct date and location fields in the "Auto-imported" calendar.
Human role
The source evidence is unavailable for specific human roles beyond the initial labeling step.
Limitations
Prerequisites include Gmail and Calendar API access in n8n. The workflow relies on manual labeling of emails, which is a bottleneck. Integration uncertainty exists regarding PDF parsing accuracy for varied vendor formats. Human approval is required for final calendar entries if auto-creation is disabled.
Try it
Act as an automation engineer. I need to build an n8n workflow to convert booking emails into calendar events. Inputs: [Gmail Account], [Calendar ID], [Sample Booking Emails]. Steps: 1. Create an n8n workflow with a Gmail Trigger node watching for emails with the label "Events". 2. Add a node to convert the email body HTML to PDF. 3. Use a PDF parser node to extract text from both the original attachments and the generated PDF. 4. Merge the extracted data using an AI node or regex to identify date, time, location, and confirmation number. 5. Create a Google Calendar event in the "Auto-imported" calendar using the extracted data. 6. Perform a dry run with 3 sample emails. Verify the extracted fields match the source. 7. Ask for my confirmation before enabling the workflow for live emails. Output: A JSON configuration of the n8n workflow and a report of the dry run results. If inputs are missing, ask for the specific Gmail credentials or sample files.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.