Skip to main content

When specific event created in Google Calendar, duplicate & rename Google file

Workflow preview

Workflow preview
100%
When specific event created in Google Calendar, duplicate & rename Google file preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Who is this template for? This template is for everyone who has to take notes during a call: Talent Acquisition Managers / Talent Acquisition Specialists / Recruiters HR professionals Sales teams, ...

Best for

  • File Management automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.filter, n8n-nodes-base.googlecalendartrigger, n8n-nodes-base.googledrive, 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 Candice Capelle.

Original n8n.io source

1.1 Workflow description

Title
When specific event created in Google Calendar, duplicate & rename Google file
Workflow name
When specific event created in Google Calendar, duplicate & rename Google file

Who is this template for?

This template is for everyone who has to take notes during a call:

  • Talent Acquisition Managers / Talent Acquisition Specialists / Recruiters
  • HR professionals
  • Sales teams, customer success teams
  • Product teams / User Experience Designers / anyone conducting user research interviews

Use case

This workflow allows specific events created on Google Calendar (or any other meeting scheduling tool like Calendly) to trigger the duplication and renaming of a specific template document.

Example: For each new screening call that is scheduled in your calendar, you want to create a draft of your screening interview template for the role, titled "{Name of the candidate} | {Date of the interview}", and located in your Google Drive in a specific folder

This workflow could then be extended to copy the link to the file on a Notion database that is shared with the team (check "To go further" section).

This workflow ensures that if you're jumping from calls to calls, you're already set up to take notes, and every document is tidied up and sorted in a structured way!

How it works

  • The workflow starts when a new event is created in Google Calendar
  • The Filter node then selects a specific type of events, depending on a chosen pattern (title includes a specific term, organizer is X, attendees include Y, etc.)
  • The workflow then searches for a specific folder in your Google Drive, where the file you want to duplicate is located
  • The workflow then searches for the specific file you want to duplicate
  • The last step allows to duplicate and rename the file with variables from your Google Calendar event

Set up

  • Set up credentials for Google Calendar, Google Drive, and Google File. You'll need a Google Workspace account.
  • Set up the Filter node with the pattern you want to look for to retreive specific events in your calendar
  • Set up the Google Drive you want to search in
  • Set up the Google File you want to duplicate
  • Set up variable at the last step to rename your duplicated file however you want it, or add a description

To go further

Here's a few idea to enhance this workflow depending on your specific needs:

  • Instead of a filter, separate your flow depending on your use case (ex: you have want to fetch different templates depending on the type of call it'll be).
  • Switch Google Calendar for another trigger (Calendly, Hubspot..)
  • 10 minutes before the event, send the duplicate Google File to the meeting organizer through Slack
  • The day after the event, if the event hasn't been cancelled, add the link to the Google File to your ATS, Hubspot, etc.

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 - Filter specific event

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

Block 2 - New event in Google Calendar

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

Block 3 - Search folder

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 4 - Search file to duplicate

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 5 - Create and rename Google File

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 6 - Sticky Note

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

Block 7 - Sticky Note1

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

Block 8 - Sticky Note2

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

Block 9 - Sticky Note3

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

Block 10 - Sticky Note4

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

Block 11 - Sticky Note5

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

Block 12 - Sticky Note6

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

3. Summary Table

Workflow When specific event created in Google Calendar, duplicate & rename Google file
Complexity intermediate
Nodes 12
Categories File Management
Author Candice Capelle
Published 28 Feb 2024

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/2145/2145.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 When specific event created in Google Calendar, duplicate & rename Google file do?

Who is this template for? This template is for everyone who has to take notes during a call: Talent Acquisition Managers / Talent Acquisition Specialists / Recruiters HR professionals Sales teams, ...

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 File Management use case.