Block 1 - Cron Trigger
- Type / Role
- n8n-nodes-base.cron - cron
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
This workflow sends a “Join in 10” Slack ping to each interviewer shortly before their interview starts. It checks the Interviews Google Calendar every minute, finds interviews starting in the next...
n8n-nodes-base.cron, n8n-nodes-base.function, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.set, n8n-nodes-base.googlecalendar
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by WeblineIndia.
Original n8n.io sourceThis workflow sends a “Join in 10” Slack ping to each interviewer shortly before their interview starts. It checks the Interviews Google Calendar every minute, finds interviews starting in the next LEAD_MINUTES (default 10), and sends a Slack DM with the candidate name, role, local start time, meeting link, and any CV: / Notes: links present in the event description. If the Slack user can’t be found by email, it posts to a fallback channel (default #recruiting-alerts) with an @‑style email mention. A Data Store prevents duplicate pings for the same event + attendee.
LEAD_MINUTES, creates one item per internal attendee (company domain), and extracts meeting/CV/Notes links.Attendees marked declined are skipped; accepted, tentative, and needsAction are included.
CV: https://... and Notes: https://....users:read.email, chat:write, and im:writeCALENDAR_NAME = InterviewsCOMPANY_DOMAIN = weblineindia.comTIMEZONE = Asia/KolkataLEAD_MINUTES = 10FALLBACK_CHANNEL = #recruiting-alertsusers:read.email, chat:write, im:write.LEAD_MINUTES in Set: Config (e.g., 5, 15).tentative or needsAction.CALENDAR_NAME in Set: Config if you use a different calendar.LEAD_MINUTES and that attendees include internal emails (@weblineindia.com).TIMEZONE is Asia/Kolkata (or your local TZ) and calendar times are correct.If you’d like a hand adjusting filters, message formatting or permissions, feel free to reach out we'll be happy to help you get this running smoothly.
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.
| Workflow | Send interview reminders (10 minutes) from Google Calendar to Slack DMs |
|---|---|
| Complexity | intermediate |
| Nodes | 10 |
| Categories | HR |
| Author | WeblineIndia |
| Published | 30 Jul 2025 |
Use the JSON export at /data/workflows/6683/6683.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
This workflow sends a “Join in 10” Slack ping to each interviewer shortly before their interview starts. It checks the Interviews Google Calendar every minute, finds interviews starting in the next...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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 HR use case.