Back to Catalog

Microsoft Outlook AI email assistant with contact support from Monday and Airtable

Cognitive CreatorsCognitive Creators
6914 views
2/3/2026
Official Page

Microsoft Outlook AI Email Assistant

Prerequisites

1. Microsoft 365 Login Credentials

  • Provide your Office 365 credentials to connect Outlook.

2. Monday.com

  • Generate an API token and have a board with your contact details.

3. Airtable

  • Obtain an API key (or personal access token) and set up a base to store:
    • Contacts (populated by the Monday.com sync).
    • Rules & Categories (used by the AI Email Assistant).
  • Use this Airtable base as the template: Airtable AI Email Assistant Template. Define your own rules, categories, and delete rules.

4. OpenAI API Key

  • Sign up for OpenAI if you don’t already have an account.
  • Generate a new API key at OpenAI API Keys.

What the System Does

1. Daily Contact Sync (Monday.com → Airtable)

  • Runs once a day to pull the latest contacts from Monday.com and store or update them in Airtable.

2. AI Email Categorisation & Prioritisation

  • Fetches Outlook emails with filters.
  • Cleans and processes email content.
  • Matches emails with known contacts from Airtable.
  • Uses an AI agent to classify, categorise, and prioritise emails.
  • Updates Outlook categories and importance based on AI results.
  • Runs in parallel with Airtable rules & categories retrieval for real-time decision-making.

Workflow 1: Daily Contact Sync (Monday.com → Airtable)

Purpose

Keep Airtable’s Contacts table up to date by pulling new or updated contact data from Monday.com daily.

Steps

  1. Schedule Trigger

    • Runs at a set interval (daily) to initiate contact syncing.
  2. Monday.com: Get Contacts

    • Reads the specified board/columns from Monday.com where you store contact details.
  3. Airtable - Contacts

    • Upserts (adds or updates) the fetched Monday.com data into Airtable’s Contacts table.
    • Ensures daily updates reflect changes from Monday.com.

Result

A consolidated contact list in Airtable, ready for AI email categorisation.


Workflow 2: Categorise & Prioritise Outlook Emails

Purpose

Fetches Outlook emails, cleans and processes their content, matches senders with known contacts, and uses AI to categorise and prioritise them.

Steps

1. Get Outlook Emails with Filters

  • Trigger: Either scheduled (Check Mail Schedule Trigger) or manual (Test Workflow).
  • Outlook Filters:
    • Not flagged (flag/flagStatus == 'notFlagged').
    • Not categorised (not categories/any()).

🔹 Result: A batch of fresh, unprocessed emails ready for processing.


2. Sanitise Email

  • Convert to Markdown: Strips HTML tags and normalises formatting.
  • Email Messages Processing: Allows manual removal of signatures, disclaimers, or extra content.

🔹 Result: A clean, AI-friendly email for categorisation.


3. Match Contact

  • Loop Over Emails: Iterates over each email.
  • Contact Lookup: Checks Airtable’s Contacts table (updated daily).
  • Merge Data: Enriches emails with known client, supplier, or internal team info.

🔹 Result: Enhanced email context for AI processing.


4. AI Agent to Categorise & Prioritise

  • Retrieve Rules & Categories
    • Reads Rules, Categories, and Delete Rules from Airtable in parallel.
  • AI: Analyse Email (Tools Agent)
    • Uses email text, sender info, and rules to build a structured AI prompt.
  • OpenAI Chat Model
    • Processes the AI prompt and outputs:
      • Category
      • Subcategory (optional)
      • Priority level
      • Short rationale
  • Structured Output Parser
    • Ensures AI response is valid JSON format.

🔹 Result:
Each email is labelled, categorised, and prioritised with AI-driven logic.


5. Set Outlook Category & Importance

  • Set Category: Updates Outlook with the assigned category.
  • Check Priority Conditions (If Node):
    • If Action Required or from a VIP, mark as High Priority.
  • Set Importance: Updates the email's importance flag in Outlook.

🔹 Result:
Outlook is updated with categories & importance based on AI recommendations.


Parallel Processing: Retrieve Rules & Categories

  • Runs alongside the email categorisation workflow.
  • Ensures Airtable-based rules are available before AI processing.

Steps

  1. Airtable: Get Rules & Categories
    • Fetches Rules, Categories, and Delete Rules from Airtable.
  2. Delete Rules (Optional)
    • If a delete rule matches, the email is removed.

🔹 Result:
A dynamic, updatable rule system ensuring emails are handled properly.


Final Outcome

  • Daily Contact Sync keeps contacts up to date.
  • AI-driven email workflow ensures smart categorisation.
  • Outlook automatically updated with AI-generated categories and importance.

This automated system saves time, ensures efficient inbox management, and allows for customisable rules via Airtable.

n8n Microsoft Outlook AI Email Assistant with Contact Support from Monday and Airtable

This n8n workflow acts as an intelligent email assistant for Microsoft Outlook, designed to categorize incoming emails, generate AI-powered responses, and manage customer support requests by creating or updating items in Monday.com and Airtable.

What it does

This workflow automates several key aspects of email management and customer support:

  1. Manual Trigger: The workflow can be initiated manually for testing or on-demand processing.
  2. Scheduled Trigger: It can also be configured to run on a schedule, periodically checking for new emails.
  3. Microsoft Outlook Email Retrieval: Fetches emails from a specified Microsoft Outlook account.
  4. AI Email Analysis and Categorization: Uses an AI Agent (likely powered by OpenAI) to analyze the email content and categorize it.
  5. Structured Output Parsing: Extracts structured information from the AI Agent's response, such as the email category and generated response.
  6. Conditional Routing (If Node): Based on the AI's categorization, the workflow routes the email to different branches for further processing.
  7. Monday.com Integration: If the email is categorized as a support request, it creates or updates an item in Monday.com.
  8. Airtable Integration: Similarly, it interacts with Airtable, potentially for contact management or logging.
  9. AI Response Generation: Generates an AI-powered email response based on the email content and category.
  10. Outlook Email Reply: Sends an automated reply via Microsoft Outlook using the AI-generated response.
  11. Data Merging: Combines data from different branches to ensure all relevant information is processed.
  12. Field Editing (Set Node): Manipulates and prepares data for subsequent nodes.
  13. Batch Processing (Loop Over Items): Processes multiple email items in batches if necessary.
  14. Markdown Formatting: Formats text content into Markdown, potentially for internal notes or specific integrations.
  15. Sticky Notes: Provides internal documentation or notes within the workflow.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Microsoft Outlook Account: Configured as a credential in n8n to access and send emails.
  • OpenAI API Key: Or access to a compatible AI model for the AI Agent and OpenAI Chat Model nodes. This needs to be configured as a credential for the Langchain nodes.
  • Monday.com Account: With appropriate API access and boards configured to receive new items or updates.
  • Airtable Account: With appropriate API access and bases/tables configured for data storage.

Setup/Usage

  1. Import the workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Microsoft Outlook credential.
    • Set up your OpenAI (or compatible LLM) credential for the AI Agent and OpenAI Chat Model nodes.
    • Set up your Monday.com credential.
    • Set up your Airtable credential.
  3. Customize Nodes:
    • Microsoft Outlook: Configure the Microsoft Outlook node to specify the mailbox, folders, and criteria for fetching emails.
    • AI Agent / OpenAI Chat Model: Adjust the prompts and model parameters to suit your specific email categorization and response generation needs.
    • Structured Output Parser: Ensure the schema matches the expected output from your AI Agent.
    • If Node: Customize the conditions to accurately route emails based on the AI's categorization.
    • Monday.com: Configure the board, group, and column mappings for creating or updating items.
    • Airtable: Configure the base, table, and field mappings for your Airtable operations.
    • Schedule Trigger: Adjust the schedule to your desired frequency for checking emails.
  4. Activate the Workflow: Once configured, activate the workflow. It will then run according to its schedule or can be triggered manually.

Related Templates

Auto-create TikTok videos with VEED.io AI avatars, ElevenLabs & GPT-4

💥 Viral TikTok Video Machine: Auto-Create Videos with Your AI Avatar --- 🎯 Who is this for? This workflow is for content creators, marketers, and agencies who want to use Veed.io’s AI avatar technology to produce short, engaging TikTok videos automatically. It’s ideal for creators who want to appear on camera without recording themselves, and for teams managing multiple brands who need to generate videos at scale. --- ⚙️ What problem this workflow solves Manually creating videos for TikTok can take hours — finding trends, writing scripts, recording, and editing. By combining Veed.io, ElevenLabs, and GPT-4, this workflow transforms a simple Telegram input into a ready-to-post TikTok video featuring your AI avatar powered by Veed.io — speaking naturally with your cloned voice. --- 🚀 What this workflow does This automation links Veed.io’s video-generation API with multiple AI tools: Analyzes TikTok trends via Perplexity AI Writes a 10-second viral script using GPT-4 Generates your voiceover via ElevenLabs Uses Veed.io (Fabric 1.0 via FAL.ai) to animate your avatar and sync the lips to the voice Creates an engaging caption + hashtags for TikTok virality Publishes the video automatically via Blotato TikTok API Logs all results to Google Sheets for tracking --- 🧩 Setup Telegram Bot Create your bot via @BotFather Configure it as the trigger for sending your photo and theme Connect Veed.io Create an account on Veed.io Get your FAL.ai API key (Veed Fabric 1.0 model) Use HTTPS image/audio URLs compatible with Veed Fabric Other APIs Add Perplexity, ElevenLabs, and Blotato TikTok keys Connect your Google Sheet for logging results --- 🛠️ How to customize this workflow Change your Avatar: Upload a new image through Telegram, and Veed.io will generate a new talking version automatically. Modify the Script Style: Adjust the GPT prompt for tone (educational, funny, storytelling). Adjust Voice Tone: Tweak ElevenLabs stability and similarity settings. Expand Platforms: Add Instagram, YouTube Shorts, or X (Twitter) posting nodes. Track Performance: Customize your Google Sheet to measure your most successful Veed.io-based videos. --- 🧠 Expected Outcome In just a few seconds after sending your photo and theme, this workflow — powered by Veed.io — creates a fully automated TikTok video featuring your AI avatar with natural lip-sync and voice. The result is a continuous stream of viral short videos, made without cameras, editing, or effort. --- ✅ Import the JSON file in n8n, add your API keys (including Veed.io via FAL.ai), and start generating viral TikTok videos starring your AI avatar today! 🎥 Watch This Tutorial --- 📄 Documentation: Notion Guide Need help customizing? Contact me for consulting and support : Linkedin / Youtube

Dr. FirasBy Dr. Firas
39510

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

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247