Back to Catalog

Email reports on expiring Microsoft Entra ID app secrets and certificates with Microsoft Graph

Alexander SchnablAlexander Schnabl
131 views
2/3/2026
Official Page

Monitor expiring EntraID application secrets and notify responsible

Stay ahead of credential expirations by automatically detecting Entra ID application client secrets and certificates that are about to expire, and sending a neatly formatted email report.

What this workflow solves

Expired client secrets and certificates are a common cause of unexpected outages and failed integrations. Manually checking expiration dates across many Entra ID applications is tedious and easy to miss. This workflow automates the discovery and reporting of credentials that will expire within a configurable time window.

Key features

  • Fetches all Microsoft Entra ID applications along with:

    • Client secrets (passwordCredentials)

    • Certificates (keyCredentials)

  • Splits credentials into individual entries for easier processing

  • Filters credentials expiring within the next N days (configurable)

  • Normalizes results into a consistent structure including:

    • Application name

    • App ID

    • Credential type (Client Secret / Certificate)

    • Credential name + ID

    • Days remaining until expiration

  • Generates an HTML table report, sorted by application name

  • Sends an email only when expiring items are found (otherwise does nothing)

How it works

  1. Fetches all Entra ID applications and their credential metadata via Microsoft Graph
  2. Separates client secrets and certificates into individual entries
  3. Filters entries that expire within the configured time window
  4. Builds a normalized list of expiring items with days remaining
  5. Emails an HTML table report (only if results exist)

Setup requirements

  • Microsoft Entra ID app registration with Microsoft Graph Application permissions:

    • Application.Read.All
  • In n8n:

    • Create Microsoft Graph OAuth2 credentials (Client Credentials flow recommended)

    • Assign those credentials to the Get EntraID Applications and Secrets HTTP Request node

  • Update the Set Variables node:

    • notificationEmail: where to send the report

    • daysBeforeExpiry: alert window in days (e.g., 14)

Notes

  • The email table highlights soon-to-expire credentials more prominently (based on remaining days).

  • For automation, replace the manual trigger with a Schedule Trigger (e.g., daily/weekly).

  • The workflow accesses metadata only (names/IDs/expiry), not secret values.

Email Reports on Expiring Microsoft Entra ID App Secrets and Certificates with Microsoft Graph

This n8n workflow automates the process of generating and emailing reports on expiring application secrets and certificates within Microsoft Entra ID (formerly Azure Active Directory). It leverages the Microsoft Graph API to retrieve the necessary data, filters for items nearing expiration, formats the information into a readable HTML table, and sends it via email.

What it does

  1. Manually Trigger: The workflow is initiated manually, allowing for on-demand execution.
  2. Fetch Application Data: It makes an HTTP request to the Microsoft Graph API to retrieve a list of all applications registered in Microsoft Entra ID.
  3. Process Application Data:
    • It iterates through each application.
    • For each application, it checks its configured password credentials (secrets) and key credentials (certificates).
    • It filters these credentials, keeping only those that are set to expire within a defined timeframe (e.g., 90 days from the current date).
    • It extracts relevant details such as application name, credential type, key ID, and expiration date.
  4. Format Report Data:
    • It aggregates the filtered expiring credentials into a single dataset.
    • It then transforms this data into an HTML table format, making it suitable for email presentation.
  5. Conditional Email Sending:
    • It checks if there are any expiring secrets or certificates found.
    • If expiring items are found, an email containing the HTML report is sent.
    • If no expiring items are found, the workflow concludes without sending an email.
  6. Send Email: An email is sent with the formatted HTML table listing all expiring application secrets and certificates.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Microsoft Entra ID (Azure AD) Application Registration: An application registered in Microsoft Entra ID with appropriate permissions to read application details (e.g., Application.Read.All or Directory.Read.All Microsoft Graph API permissions).
  • Microsoft Graph API Credentials: An OAuth2 or client credentials setup in n8n for authenticating with the Microsoft Graph API.
  • SMTP Server Configuration: An SMTP server configured in n8n to send emails.
  • Email Recipient(s): The email address(es) to which the report should be sent.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Microsoft Graph Credentials:
    • Locate the "HTTP Request" node (ID: 19).
    • Configure the "Authentication" section to use your Microsoft Graph API credentials. This typically involves setting up an OAuth2 or Client Credentials credential in n8n that points to your Microsoft Entra ID application registration.
    • Ensure the configured application has the necessary permissions to read application data (Application.Read.All or Directory.Read.All).
  3. Configure Email Sending:
    • Locate the "Send Email" node (ID: 11).
    • Set up your SMTP credentials in n8n.
    • Specify the "To" email address(es) where you want the reports to be sent.
    • Adjust the "Subject" and "Body" as needed. The body will typically reference the HTML table generated earlier.
  4. Adjust Expiration Threshold (Optional):
    • The "Filter" node (ID: 844) is likely configured to filter items expiring within a certain timeframe. You can adjust this logic to suit your organization's reporting needs (e.g., 30, 60, or 180 days).
  5. Activate and Execute:
    • Activate the workflow.
    • Click "Execute Workflow" on the "Manual Trigger" node to run it on demand, or set up a "Schedule Trigger" if you want it to run periodically (e.g., daily, weekly).

Related Templates

AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp

This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The β€œvirtual executive team,” is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier 🎯 Core Features πŸ§‘β€πŸ’Ό 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. πŸ“Š 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. πŸ•΅οΈβ€β™€οΈ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. ⏰ 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline β€” key traits for early-stage success. πŸ—“οΈ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. πŸ’¬ WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. βš™οΈ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. 🧩 Integrations Required Gemini API – for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API – for business and competitor analysis SerpAPI – for market research and opportunity scouting Google OAuth – to connect Sheets, Calendar, and Gmail WhatsApp Business API – for message triggers and responses πŸš€ Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. 🧰 Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startup’s needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you πŸ’‘ Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business

ShadrackBy Shadrack
331

πŸŽ“ How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits βœ… Full Automation: Eliminates manual reading and data entry from incoming emails. βœ… Multi-Source Integration: Handles data from different email providers seamlessly. βœ… AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. βœ… Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. βœ… Time Efficiency: Processes emails in real time, improving productivity and response speed. *βœ… Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API

Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. It’s designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this ➀ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait 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) 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. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. 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
110