Automate employee date tracking & reminders for HR with JavaScript
HR Date Management Automation - Complete Setup Guide
🎯 How It Works
This n8n workflow transforms your HR department from reactive to proactive by automatically monitoring 5 critical employee timelines and generating smart alerts before deadlines hit.
Core Components
- Data Input → Employee information (hire dates, contracts, certifications)
- Date Analysis Engine → Calculates days until critical events
- Smart Categorization → Sorts employees by urgency level
- Reminder Scheduler → Creates proactive notifications
- Multi-Format Export → Sends alerts to your preferred systems
Business Value
- Prevents compliance violations ($5K-50K+ in fines)
- Reduces HR workload (15-20 hours/month saved)
- Improves employee experience (no missed reviews/renewals)
- Provides management visibility (dashboard reporting)
🚀 Quick Start Test
1. Import the Workflow
- Download the
Javascript_Hr.jsonfile - Open n8n and click “Import from file”
- Select the downloaded JSON file
- Click “Import”
2. Test with Sample Data
- Click the “Execute Workflow” button
- Review the sample output in each node
- Check the final export data format
What you’ll see:
- 5 sample employees with different scenarios
- Calculated days until contract/certification expiry
- Priority levels (high/medium/low)
- Scheduled reminders with recipient emails
- Export data in multiple formats
🔧 Real-World Integration Setup
Option 1: Google Sheets Integration (Most Popular)
Step 1: Prepare Your Employee Data
Create a Google Sheet with these columns:
| Employee ID | Name | Email | Department | Hire Date | Contract End | Certification Expiry | Last Review | Probation End | Vacation Days | Status |
Sample data format:
| 1 | John Smith | john@company.com | IT | 2024-01-15 | 2025-12-31 | 2025-03-20 | 2024-06-15 | 2024-07-15 | 20 | active |
Step 2: Replace Sample Data Generator
- Delete the “Sample Data Generator” node
- Add “Google Sheets” node
- Connect to your Google account
- Configure these settings:
- Operation: Read
- Document: Your employee spreadsheet
- Sheet: Employee data sheet
- Range: A1:K100 (adjust for your data size)
- Options: ✅ RAW data, ✅ Header row
Step 3: Map Your Data
Add a “Set” node after Google Sheets to standardize field names:
// Map your sheet columns to workflow format
{
"id": "{{ $json['Employee ID'] }}",
"name": "{{ $json['Name'] }}",
"email": "{{ $json['Email'] }}",
"department": "{{ $json['Department'] }}",
"hiredOn": "{{ $json['Hire Date'] }}",
"contractEndDate": "{{ $json['Contract End'] }}",
"certificationExpiry": "{{ $json['Certification Expiry'] }}",
"lastReviewDate": "{{ $json['Last Review'] }}",
"probationEndDate": "{{ $json['Probation End'] }}",
"vacationDays": "{{ $json['Vacation Days'] }}",
"status": "{{ $json['Status'] }}"
}
Option 2: HRIS Integration (BambooHR Example)
Step 1: BambooHR API Setup
- Get your BambooHR API key from Settings > API Keys
- Note your company subdomain (e.g.,
yourcompany.bamboohr.com)
Step 2: Replace Sample Data Generator
- Delete the “Sample Data Generator” node
- Add “HTTP Request” node
- Configure these settings:
- Method: GET
- URL:
https://api.bamboohr.com/api/gateway.php/[SUBDOMAIN]/v1/employees/directory - Authentication: Basic Auth
- Username: Your API key
- Password: x (leave as ‘x’)
- Headers:
Accept: application/json
Step 3: Transform BambooHR Data
Add a “Code” node to transform the API response:
// Transform BambooHR response to workflow format
const employees = [];
for (const employee of $input.all()) {
const emp = employee.json;
employees.push({
id: emp.id,
name: `${emp.firstName} ${emp.lastName}`,
email: emp.workEmail,
department: emp.department,
hiredOn: emp.hireDate,
contractEndDate: emp.terminationDate || "2025-12-31", // Default if not set
certificationExpiry: emp.customCertDate || "2025-12-31",
lastReviewDate: emp.customReviewDate || null,
probationEndDate: emp.customProbationDate || null,
vacationDays: emp.paidTimeOff || 20,
status: emp.employeeStatus || "active"
});
}
return employees.map(emp => ({ json: emp }));
Option 3: CSV File Upload
Step 1: Prepare CSV File
Create a CSV with the same structure as the Google Sheets format.
Step 2: Use CSV Parser
- Replace “Sample Data Generator” with “Read Binary File” node
- Add “CSV Parser” node
- Configure settings:
- Include Headers: Yes
- Delimiter: Comma
- Skip Empty Lines: Yes
📧 Output Integration Setup
Email Notifications
Step 1: Add Email Node
- Add “Email” node after “Reminder Scheduler”
- Connect to your email provider (Gmail/Outlook)
Step 2: Configure Email Templates
// Dynamic email content based on reminder type
const reminder = $json;
const emailTemplates = {
contract_renewal: {
subject: `🚨 Contract Renewal Required - ${reminder.employeeName}`,
body: `
Hi HR Team,
${reminder.employeeName}'s contract expires on ${reminder.dueDate}.
Days remaining: ${Math.ceil((new Date(reminder.dueDate) - new Date()) / (1000*60*60*24))}
Please initiate renewal process immediately.
Best regards,
HR Automation System
`
},
certification_renewal: {
subject: `📜 Certification Renewal Reminder - ${reminder.employeeName}`,
body: `
Hi ${reminder.employeeName},
Your certification expires on ${reminder.dueDate}.
Please renew your certification to maintain compliance.
Contact HR if you need assistance.
Best regards,
HR Team
`
}
};
const template = emailTemplates[reminder.type];
return {
to: reminder.recipientEmail,
subject: template.subject,
body: template.body
};
Slack Integration
Step 1: Add Slack Node
- Add “Slack” node after “Advanced Date Filters”
- Connect to your Slack workspace
Step 2: Configure Channel Alerts
// Send summary to #hr-alerts channel
const summary = $json.summary;
const message = `
🏢 *Daily HR Report*
👥 Total Employees: ${summary.totalEmployees}
🆕 New Hires: ${summary.newHires}
⚠️ High Priority Actions: ${summary.highPriority}
📋 Contracts Expiring: ${summary.contractsExpiring}
🎓 Certifications Expiring: ${summary.certificationsExpiring}
Generated: ${new Date().toLocaleDateString()}
`;
return {
channel: '#hr-alerts',
text: message
};
Google Calendar Integration
Step 1: Add Calendar Node
- Add “Google Calendar” node after “Reminder Scheduler”
- Connect to your Google account
Step 2: Create Calendar Events
// Create calendar events for upcoming deadlines
const reminder = $json;
const eventTitles = {
contract_renewal: `Contract Renewal - ${reminder.employeeName}`,
certification_renewal: `Certification Renewal - ${reminder.employeeName}`,
performance_review: `Performance Review - ${reminder.employeeName}`,
probation_review: `Probation Review - ${reminder.employeeName}`
};
return {
calendarId: 'hr-calendar@yourcompany.com',
summary: eventTitles[reminder.type],
description: reminder.message,
start: {
dateTime: reminder.dueDate,
timeZone: 'America/New_York'
},
end: {
dateTime: reminder.dueDate,
timeZone: 'America/New_York'
},
attendees: [
{ email: 'hr@yourcompany.com' },
{ email: reminder.recipientEmail }
]
};
🎯 Scheduling & Automation
Daily Monitoring Setup
Step 1: Add Cron Trigger
- Replace “Manual Trigger” with “Cron” node
- Set schedule:
0 9 * * 1-5(9 AM, Monday-Friday) - Configure timezone to your business hours
Step 2: Error Handling
- Add “Error Trigger” node
- Connect to email notification for failures
- Set up retry logic for failed integrations
Weekly Reports
Step 1: Create Weekly Summary
- Add separate “Cron” trigger for weekly reports
- Set schedule:
0 9 * * 1(9 AM every Monday) - Modify the filtering logic to show weekly trends
🔍 Customization Options
Adjust Alert Timings
In the “Date Analysis & Categorization” node:
// Modify these values to change alert timing
const isContractExpiringSoon = daysUntilContractEnd <= 90; // Change from 90 days
const isCertificationExpiringSoon = daysUntilCertificationExpiry <= 60; // Change from 60 days
const needsReview = daysSinceLastReview >= 365; // Change from 365 days
Add Custom Employee Categories
// Add new categories in the analysis node
const isContractor = employee.employeeType === 'contractor';
const isRemoteWorker = employee.location === 'remote';
const isHighRisk = employee.performanceRating === 'needs_improvement';
Custom Date Formats
Modify the “Date Formatting & Export” node to add your preferred formats:
// Add custom date format
const formatters = {
custom: (date) => {
const options = {
year: 'numeric',
month: 'long',
day: 'numeric',
weekday: 'long'
};
return date.toLocaleDateString('en-US', options);
}
};
🎚️ Testing & Validation
Step 1: Data Validation
- Test with 2-3 sample employees first
- Verify all dates are parsing correctly
- Check that calculations match manual calculations
Step 2: Alert Testing
- Create test scenarios with dates 30/60/90 days out
- Verify emails are sent to correct recipients
- Test Slack notifications in a test channel
Step 3: Performance Testing
- Test with your full employee dataset
- Monitor execution time (should be under 30 seconds)
- Check for memory usage with large datasets
🆘 Troubleshooting Guide
Common Issues
Date Parsing Errors
// Add date validation in the analysis node
const parseDate = (dateStr) => {
const date = new Date(dateStr);
if (isNaN(date.getTime())) {
console.error(`Invalid date: ${dateStr}`);
return null;
}
return date;
};
Missing Data Fields
// Add data validation
const validateEmployee = (employee) => {
const required = ['name', 'email', 'hiredOn'];
const missing = required.filter(field => !employee[field]);
if (missing.length > 0) {
console.error(`Missing required fields for ${employee.name}: ${missing.join(', ')}`);
return false;
}
return true;
};
API Rate Limits
- Add “Wait” nodes between API calls
- Implement retry logic with exponential backoff
- Cache API responses when possible
🚀 Advanced Features
Multi-Company Support
// Add company filtering in the analysis node
const processEmployeesByCompany = (employees, companyId) => {
return employees.filter(emp => emp.companyId === companyId);
};
Custom Notification Rules
// Advanced notification logic
const shouldNotify = (employee, eventType) => {
const rules = {
contract_renewal: employee.department !== 'intern',
certification_renewal: employee.role === 'certified_professional',
performance_review: employee.status === 'active'
};
return rules[eventType] || false;
};
Integration with Time Tracking
// Connect to time tracking APIs
const calculateWorkingDays = (startDate, endDate) => {
// Implementation for working days calculation
// Excluding weekends and holidays
};
This workflow transforms your HR department from reactive to proactive, preventing costly compliance issues while improving employee experience. The modular design allows you to start simple and add complexity as needed.
Automate Employee Date Tracking and Reminders for HR
This n8n workflow simplifies and automates the process of tracking employee dates (like anniversaries, birthdays, or contract renewals) and sending timely reminders to HR. It reads employee data from a Google Sheet, processes it to identify upcoming dates, and then sends personalized notifications via Slack and Gmail.
What it does
- Manually Triggered: The workflow is initiated manually by clicking "Execute workflow".
- Reads Employee Data: It connects to a specified Google Sheet to retrieve a list of employee records.
- Processes Data with Custom Code: A JavaScript code node processes the data from Google Sheets. This node is likely responsible for:
- Calculating upcoming dates (e.g., "date in 30 days", "date in 7 days", "date in 1 day").
- Filtering employees whose dates fall within these upcoming windows.
- Formatting the data for notifications.
- Sends Slack Notifications: For relevant upcoming dates, the workflow sends a notification to a designated Slack channel or user, alerting HR about the approaching employee milestones.
- Sends Gmail Notifications: In addition to Slack, the workflow sends an email notification via Gmail to relevant HR personnel, providing details about the upcoming employee dates.
- Creates Google Calendar Events (Optional/Future Enhancement): The workflow includes a Google Calendar node, suggesting a future capability or current setup to automatically create calendar events for these important employee dates.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Google Sheets Account: A Google Sheets spreadsheet containing employee data (e.g., employee name, date of joining, date of birth, contract end date).
- Google Credentials: Configured Google OAuth2 credentials in n8n with access to Google Sheets, Google Calendar, and Gmail.
- Slack Account: A Slack workspace and a configured Slack credential in n8n with permissions to post messages.
Setup/Usage
- Import the workflow: Download the JSON and import it into your n8n instance.
- Configure Google Sheets Node:
- Select your Google Sheets credential.
- Specify the Spreadsheet ID and Sheet Name where your employee data is stored.
- Ensure the data includes relevant date columns (e.g., "Hire Date", "Birthday", "Contract End Date").
- Configure Code Node: Review and adjust the JavaScript code within the "Code" node to match your specific date tracking logic and desired output format. This is where you define what "upcoming" means (e.g., 30, 7, 1 days out).
- Configure Slack Node:
- Select your Slack credential.
- Specify the Channel or User ID where you want the notifications to be sent.
- Customize the message content using expressions to include employee details from the previous nodes.
- Configure Gmail Node:
- Select your Gmail credential.
- Specify the recipient To address (e.g., HR email).
- Customize the Subject and Body of the email to provide clear and informative reminders.
- Configure Google Calendar Node (Optional): If you wish to create calendar events, configure this node with your Google Calendar credential, specifying the calendar ID and event details.
- Activate the workflow: Once configured, activate the workflow.
- Execute manually: Click "Execute workflow" to run it and send out the reminders. For automated execution, you would typically replace the "Manual Trigger" with a "Cron" node to run on a schedule (e.g., daily).
Related Templates
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.
Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack
AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us