Monitor SSL certificate of any domain with uProc
Do you want to check the SSL certificate expiration dates of your customers or servers? This workflow gets information of an SSL certificate using the uProc Get Certificate by domain tool. You can use this workflow to query SSL certificates in bulk and send alarms when any certificate has expired. You need to add your credentials (Email and API Key - real -) located at Integration section to n8n. You can replace "Create Domain Item" with any integration containing a domain, like Google Sheets, MySQL, or Zabbix server. Every "uProc" node returns the next fields per every analyzed SSL certificate: issuer: Contains the issuer. provider: Contains the provider. valid_from: Contains the start date. valid_to: Contains the end date. serial_number: Contains the serial number. type: Contains if supports one or multiple domains. protocol: Contains the protocol. valid: Contains its validity. domains: Contains all domains and subdomains supported. An "IF" node detects if the certificate is valid or not. Finally, the workflow sends an alarm to a Telegram channel to know if the certificate has expired.
By Miquel ColomerSend private welcome messages to new WhatsApp group members with Evolution API
Who's it for This template is perfect for community managers, business owners, and WhatsApp group administrators who want to create a welcoming experience for new members. Whether you're running a support group, managing a business community, or moderating a hobby group, this automation ensures every new member feels valued from the moment they join. How it works The workflow automatically detects when someone joins your WhatsApp group and sends them a personalized welcome message directly to their private chat. It uses Evolution API to interface with WhatsApp Business and includes a natural delay to make the interaction feel more human. The entire process is hands-off once configured, ensuring consistent engagement with new members 24/7. What it does Monitors group activity - Receives real-time notifications when members join or leave Filters for your specific group - Ensures messages are only sent for your designated group Validates new joins - Confirms the event is a member joining (not leaving) Adds natural timing - Waits a customizable period before sending the message Sends private welcome - Delivers your welcome message directly to the new member's chat Requirements Evolution API instance (self-hosted or cloud service) WhatsApp Business account connected to Evolution API Group admin permissions for the WhatsApp group n8n instance (self-hosted or cloud) How to set up Import the workflow into your n8n instance Configure the Set Variables node with: Your WhatsApp group ID (format: xxxxxxxxxxxxx@g.us) Evolution API key Instance name from Evolution API Evolution API URL Custom welcome message Delay time in minutes Copy the webhook URL from the Webhook node Configure Evolution API to send group notifications to your webhook URL Test the workflow by having someone join your group Activate the workflow for continuous operation For a detailed video tutorial on setting up this workflow, check out: https://youtu.be/WO2MJoQqLvo How to customize the workflow Welcome message: Edit the message in the Set Variables node to match your group's tone Timing: Adjust the wait time to send messages immediately or after several minutes Multiple groups: Duplicate the workflow and change the group ID for each group Rich media: Extend the HTTP Request node to send images or documents with the welcome Conditional messages: Add IF nodes to send different messages based on time of day or member count Follow-up sequence: Chain additional HTTP Request nodes to create a welcome series
By Anderson AdelinoTransfer workflows with credentials & sub-workflow management between n8n instances
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Export Workflows Between n8n Instances Copy workflows between n8n instances — with optional credential export and automatic sub-workflow adjustments. 🧠 How it Works This workflow copies a selected workflow from a SOURCE n8n server to a TARGET server and guides you through safe checks: Name conflict check: If a workflow with the same name exists on the target the export is stopped. Sub-workflows: Detects calls to sub-workflows. If all sub-workflows exist on the target (same names), references are auto-updated and the export continues. If any are missing, the form shows what’s missing and lets you cancel or proceed anyway. Credentials: Detects nodes using credentials and lets you export those credentials along with the workflow. The workflow can only apply credential corrections for the credentials that you choose to export with it. At the end, the form lists which credentials were successfully exported. 💡 For in-depth behavior and edge cases, see the Notes inside the workflow (Setup, How It Works, and Credential Issues). 🚀 How to Use Run this workflow on your SOURCE server. Follow the step-by-step form: pick the workflow to export, choose whether to include credentials, and review sub-workflow checks. Done. ⚙️ Setup Create an n8n API key on both servers (SOURCE and TARGET). On the SOURCE server, create two n8n API credentials in n8n: one for SOURCE and one for TARGET (using the respective base URL and key). Configure the nodes in this workflow with these two credentials. Detailed step-by-step instructions are available in the workflow notes. ✅ Once configured, you’ll be ready to migrate workflows between servers in just a few clicks.
By Arthur Braghetto🛠️ Metabase tool MCP server 💪 all 10 operations
Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator? Join the community Complete MCP server exposing all Metabase Tool operations to AI agents. Zero configuration needed - all 10 operations pre-built. ⚡ Quick Setup Import this workflow into your n8n instance Activate the workflow to start your MCP server Copy the webhook URL from the MCP trigger node Connect AI agents using the MCP URL 🔧 How it Works • MCP Trigger: Serves as your server endpoint for AI agent requests • Tool Nodes: Pre-configured for every Metabase Tool operation • AI Expressions: Automatically populate parameters via $fromAI() placeholders • Native Integration: Uses official n8n Metabase Tool tool with full error handling 📋 Available Operations (10 total) Every possible Metabase Tool operation is included: 🔧 Alerts (2 operations) • Get an alert • Get many alerts 🔧 Databases (3 operations) • Add a databases • Get many databases • Get Fields a databases 🔧 Metrics (2 operations) • Get a metric • Get many metrics 🔧 Questions (3 operations) • Get a questions • Get many questions • Get the results from a question 🤖 AI Integration Parameter Handling: AI agents automatically provide values for: • Resource IDs and identifiers • Search queries and filters • Content and data payloads • Configuration options Response Format: Native Metabase Tool API responses with full data structure Error Handling: Built-in n8n error management and retry logic 💡 Usage Examples Connect this MCP server to any AI agent or workflow: • Claude Desktop: Add MCP server URL to configuration • Custom AI Apps: Use MCP URL as tool endpoint • Other n8n Workflows: Call MCP tools from any workflow • API Integration: Direct HTTP calls to MCP endpoints ✨ Benefits • Complete Coverage: Every Metabase Tool operation available • Zero Setup: No parameter mapping or configuration needed • AI-Ready: Built-in $fromAI() expressions for all parameters • Production Ready: Native n8n error handling and logging • Extensible: Easily modify or add custom logic > 🆓 Free for community use! Ready to deploy in under 2 minutes.
By David Ashby