Automate Everhour Time-off Sync to Google Calendar with All-day Events — Workflow n8n

Élevé complexité Planifié18 nœuds🏷️ File Managementpar Hossein Karami

Aperçu

Who’s it for Teams that track absences in Everhour and want a shared Google Calendar view for quick planning. Ideal for managers, HR/OPS, and teammates who need instant visibility into approved time off.

What it does Pulls approved time-off from Everhour on a schedule
Creates/updates all-day events per day of absence in Google Calendar
Removes stale events if a request changes or is canceled
Uses a stable external key (everhour:ASSIGNMENT_ID:YYYY-MM-DD) to avoid duplicates

How it works A

Nœuds utilisés

HTTP RequestGoogle CalendarCode

Aperçu du workflow

Everhour time-off sync to Google Calendar
Who’s it for
Teams using Everhour for time tracking and Google Calen
What it does
- Fetches approved time-off from
Fetch Everhour
Fetch approved time-off from Everhour using Header Auth
Build Keys
Generate per-day `externalKey` like `everhour:<id>:<dat
Upsert Events
Search by key → update if found, otherwise create all-d
Cleanup
List events and delete those not present in current key
S
Schedule Trigger
Build Assignment Groups
Build Global Key Set
Everhour - Fetch Time Off
F
Filter Approved Time-Off
B
Build Calendar Payload
Prepare Time-Off Items
Find Existing Event by E…
Attach Found Event ID
C
Check if Event Exists
Update All-Day Event
Create All-Day Event
List Assignment Events
Find Obsolete Events (pe…
Delete Calendar Event
List All Everhour Events
Find Obsolete Events (gl…
C
Config
18 nodes18 edges

Comment ça fonctionne

  1. 1

    Déclencheur

    Le workflow démarre avec un déclencheur planifié, s'exécutant selon un planning défini.

  2. 2

    Traitement

    Les données transitent par 18 nœuds, connecting code, googlecalendar, httprequest.

  3. 3

    Sortie

    Le workflow termine son automatisation et livre le résultat à la destination configurée.

Détails des nœuds (18)

HT

HTTP Request

httpRequest

#1
GO

Google Calendar

googleCalendar

#2
CO

Code

code

#3

Comment importer ce workflow

  1. 1Cliquez sur le bouton Télécharger JSON à droite pour enregistrer le fichier du workflow.
  2. 2Ouvrez votre instance n8n. Accédez à Workflows → Nouveau → Importer depuis un fichier.
  3. 3Sélectionnez le fichier automate-everhour-time-off-sync-to-google-calendar-with-all-day-events téléchargé et cliquez sur Importer.
  4. 4Configurez les identifiants pour chaque nœud de service (clés API, OAuth, etc.).
  5. 5Cliquez sur Tester le workflow pour vérifier que tout fonctionne, puis activez-le.

Ou collez directement dans n8n → Importer depuis JSON :

{ "name": "Automate Everhour Time-off Sync to Google Calendar with All-day Events", "nodes": [...], ...}

Intégrations

codegooglecalendarhttprequestifscheduletriggerset

Obtenir ce workflow

Téléchargez et importez en un clic

Télécharger JSONVoir sur n8n.io
Nœuds18
Complexitéhigh
Déclencheurscheduled
CatégorieFile Management

Créé par

Hossein Karami

Hossein Karami

@hosseinkarami

Tags

codegooglecalendarhttprequestifscheduletriggerset

Nouveau sur n8n ?

n8n est un outil d'automatisation de workflows gratuit et open-source. Hébergez-le vous-même ou utilisez la version cloud.

Obtenir n8n gratuitement →

Related File Management Workflows

COCOGOHT+5
medium

Sync SharePoint to Google Drive via Supabase (n8n Workflow)

Eliminate manual file transfers and data silos with this enterprise-grade synchronization pipeline. This n8n workflow automates the heavy lifting of mirroring your Microsoft SharePoint document libraries to Google Drive while maintaining a robust audit trail in Supabase or Postgres. Designed for high-reliability environments, the automation utilizes a sophisticated delta-check logic: it fetches SharePoint metadata, compares it against your existing database records using the 'Compare Datasets' node, and identifies only new or modified files for processing. By leveraging the 'Split in Batches' node, the system handles large volumes of data without hitting memory limits, ensuring every document is securely downloaded via HTTP and re-uploaded to its destination. Once the transfer is verified, the workflow updates your database status in real-time, providing a transparent log of your synchronization history. This is an essential solution for organizations transitioning between cloud ecosystems or those requiring a redundant, cross-platform backup strategy. It effectively bridges the gap between Microsoft and Google ecosystems using Supabase as a high-performance state-management layer. **Common Use Cases:** - Automated Multi-Cloud Disaster Recovery: Maintain a real-time mirror of critical SharePoint corporate assets in Google Drive to ensure business continuity during service outages. - Cross-Departmental Collaboration: Automatically sync project documentation from an executive SharePoint site to a creative team's Google Drive folder for seamless cross-platform access. - Centralized Document Auditing: Use Supabase to track every file movement between ecosystems, creating a searchable metadata index for compliance and regulatory reporting.

Scheduled·15 nodes
FOGOGOHT+2
medium

Automate Threads Video Backups to Google Drive & Sheets

Streamline your social media asset management with this robust n8n automation designed for digital marketers and content creators. This workflow eliminates the manual effort of downloading Threads content by providing a seamless bridge between Instagram's text-based platform and your cloud storage. Once triggered via a simple form input, the automation utilizes a RapidAPI connection to fetch high-quality video assets, processes the binary data, and securely uploads the file to a designated Google Drive folder. Simultaneously, the workflow maintains a centralized audit log in Google Sheets, capturing essential metadata such as timestamps and file IDs. Built-in logic gates and wait nodes ensure API rate limits are respected and file transfers are verified before logging. This is an essential tool for agencies managing high volumes of social content who need a reliable, automated pipeline for content repurposing, archival compliance, or collaborative review processes. By centralizing your Threads media assets, you ensure your creative team has instant access to raw footage without the friction of manual downloads. **Common Use Cases:** - Automated Social Media Content Archiving for Compliance - Centralized Asset Library Syncing for Creative Agencies - Competitor Research and Video Content Benchmarking

Trigger·9 nodes