Back to Catalog

AI-powered Candidate Screening & Interview Scheduling with OpenAI GPT & Google Suite

Oneclick AI SquadOneclick AI Squad
223 views
2/3/2026
Official Page

Streamline your hiring process with intelligent AI-powered candidate screening and automated interview scheduling. This workflow receives applications via webhook, evaluates candidates using OpenAI's GPT model, scores them against job requirements, stores data in Google Sheets, and automatically schedules interviews for high-scoring candidates β€” all while sending personalized email notifications and updating statuses in real time. Reduce manual screening time and ensure only top candidates move forward. πŸ€–πŸ“§


What This Template Does

Step 1: Triggers on new application submission via Webhook (e.g., from job portal or form).
Step 2: Stores applicant data (resume, contact, role) into Google Sheets for centralized tracking.
Step 3: Uses OpenAI GPT to evaluate candidate fit based on resume, skills, and job requirements.
Step 4: Applies Scoring Logic:
  ‒ Score β‰₯ 70 β†’ Qualified for interview
  ‒ Score < 70 β†’ Not a fit
Step 5: Branches based on score:
  → High Score Path:
   ‒ Sends Interview Invitation Email
   ‒ Creates Google Calendar Event
   ‒ Updates Sheet: Status β†’ β€œInterview Scheduled”
  → Low Score Path:
   ‒ Sends Polite Rejection Email
   ‒ Updates Sheet: Status β†’ β€œRejected”
Step 6: Final metrics logged and webhook response confirms completion.


Key Benefits

βœ… Eliminates manual resume screening
βœ… AI evaluates candidates consistently and objectively
βœ… Automates interview scheduling with calendar integration
βœ… Real-time status updates in Google Sheets
βœ… Personalized email communication at every stage
βœ… Full audit trail of decisions and actions


Features

  • Webhook-triggered application intake
  • Google Sheets as applicant tracking system (ATS)
  • OpenAI GPT-powered candidate evaluation
  • Dynamic scoring threshold (customizable)
  • Conditional branching (High/Low Score)
  • Gmail integration for email notifications
  • Google Calendar auto-event creation
  • Real-time status updates via sheet write-back
  • Final webhook response for system confirmation

Requirements

  • GOOGLE_SHEET_ID: Your Google Sheet ID
  • Credentials Needed:
    1. Google Sheets OAuth2
    2. Gmail API Key
    3. OpenAI API Key
    4. Google Calendar OAuth2
  • Customize:
    β€’ Job requirements & AI prompt
    β€’ Score threshold (currently 70)
    β€’ Email templates
    β€’ Interview scheduling time slots

Target Audience

  • HR teams managing high-volume applications πŸ‘₯
  • Recruiters seeking faster shortlisting ⏱️
  • Startups automating early-stage hiring πŸš€
  • Tech companies with technical screening needs πŸ’»
  • Remote-first organizations using digital workflows 🌍

Step-by-Step Setup Instructions

  1. Set up Google Sheet
     → Create a sheet with columns: Name, Email, Resume Link, Role, Status, Score, Timestamp
     → Replace YOUR_SHEET_ID in the workflow with your actual Sheet ID.

  2. Configure Webhook
     → Connect your job application form (e.g., Typeform, LinkedIn, custom portal) to trigger this workflow.

  3. Add OpenAI API Key
     → Insert your OpenAI key and customize the evaluation prompt under β€œAI Evaluation” node.

  4. Set Scoring Threshold
     → Adjust the β€œIF – Check Score Threshold” node (default: β‰₯70 = pass).

  5. Connect Gmail & Calendar
     → Enable Gmail OAuth2 and Google Calendar OAuth2.
     → Define interviewer email and default interview duration.

  6. Customize Emails
     → Edit β€œInterview Invitation” and β€œRejection Notice” templates with your branding.

  7. Test the Flow
     → Submit a test application via webhook.
     → Verify: Sheet update β†’ AI score β†’ Email β†’ Calendar event β†’ Status change.

  8. Go Live
     → Enable automation. Monitor first few runs in Google Sheets.


Workflow Complete!
Now sit back as AI screens, scores, schedules, and communicates β€” all without lifting a finger.

Metrics to Track:

  • Applications received
  • Average AI score
  • Interview rate
  • Time to process

n8n AI-Powered Candidate Screening and Interview Scheduling with OpenAI GPT & Google Suite

This n8n workflow automates the process of screening job candidates using AI and scheduling interviews, leveraging OpenAI's GPT models and Google Suite applications. It streamlines the recruitment pipeline from initial application review to interview scheduling.

What it does

This workflow simplifies and automates several key steps in the candidate screening and interview scheduling process:

  1. Receives Candidate Data: It is triggered by a webhook, presumably receiving candidate application data (e.g., from a form submission or an ATS).
  2. AI-Powered Candidate Screening: Uses OpenAI's GPT to process and screen candidate information, likely evaluating resumes, cover letters, or responses to screening questions.
  3. Conditional Logic for Interview: Based on the AI screening results, an If node determines if the candidate should proceed to the interview stage.
  4. Schedules Interview: If the candidate passes the screening, it uses Google Calendar to schedule an interview.
  5. Updates Google Sheets: Records candidate information and screening/scheduling status in a Google Sheet.
  6. Sends Email Notifications: Sends email notifications to relevant parties (e.g., the candidate for interview confirmation, or the hiring manager with screening results).
  7. Responds to Webhook: Provides a response back to the triggering system, indicating the outcome of the process.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • OpenAI API Key: For the OpenAI node to perform AI-powered screening.
  • Google Sheets Account: Configured with a spreadsheet to store candidate data.
  • Google Calendar Account: To schedule interviews.
  • SMTP Credentials: For the Send Email node to send notifications.
  • Webhook Source: An external system or application that can send data to the n8n webhook trigger.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your OpenAI credentials with your API key.
    • Configure your Google Sheets credentials, ensuring access to the target spreadsheet.
    • Configure your Google Calendar credentials.
    • Set up your SMTP credentials for sending emails.
  3. Configure Nodes:
    • Webhook: Copy the webhook URL and configure your external system to send candidate data to this URL.
    • OpenAI: Configure the OpenAI node with the specific prompt and model you want to use for candidate screening. Ensure it extracts relevant information or a screening score.
    • If: Adjust the conditions in the If node based on the output of the OpenAI screening to determine if a candidate should be interviewed (e.g., score > 70).
    • Google Calendar: Configure the Google Calendar node to create events with details like interview duration, attendees, and a meeting link.
    • Google Sheets: Specify the Spreadsheet ID and Sheet Name where candidate data will be written. Map the incoming data to the correct columns.
    • Send Email: Customize the email content, recipients (e.g., candidate's email, hiring manager's email), and subject lines for both successful and unsuccessful screening paths.
    • Respond to Webhook: Customize the response body as needed.
  4. Activate the Workflow: Once all configurations are complete, activate the workflow.

This workflow provides a robust framework for automating recruitment tasks, saving time and improving efficiency in candidate management.

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.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use β€” Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➀ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

πŸ“Š Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. πŸš€πŸ“šπŸ’¬ What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. πŸ“¦ Step 3: Logs release data into Google Sheets for record-keeping and analysis. πŸ“Š Step 4: Retrieves FAQ or documentation data from Notion. πŸ“š Step 5: Merges GitHub and Notion data to calculate documentation drift. πŸ” Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. πŸ”” Key Benefits βœ… Keeps SDK documentation aligned with product releases βœ… Prevents outdated information from reaching users βœ… Provides centralized release tracking in Google Sheets βœ… Sends real-time Slack alerts for overdue updates βœ… Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31