Quick Overview This workflow automates HR onboarding by capturing new hires via a webhook, saving them to Google Sheets, emailing a Slack invite via Gmail, and notifying managers in Slack, then listening for Slack team_join events to add new hires to department channels and update onboarding status. How it works Receives a POST webhook request from an HR form with new employee details and validates required fields. Appends the employee record to a Google Sheets spreadsheet and assigns a department-based list of Slack channels plus a static Slack invite link. Sends the new hire a welcome email through Gmail containing their start details and the Slack workspace invite link. Sends a Slack direct message to a manager user with the new hire details and the channels they will be added to, then updates the Google Sheets row to “Invite Sent” with a timestamp and responds to the HR form. Receives Slack Events API requests for the workspace and replies to url_verification challenges or immediately acknowledges real team_join events within 3 seconds.
Tags
Gmail
Google SheetsWHTTP RequestSlackRelated workflows
See all Gmail→
Manage clinic appointments and prescriptions with Telegram, Gmail and Google
Quick overview This workflow manages clinic appointments across Google Sheets and Google Calendar, using webhooks and Telegram to book and confirm visits, Gmail and Telegram to deliver prescriptions, scheduled Telegram reminders for upcoming appointments, and Slack notifications for workflow errors. How it works Receives a POST webhook request to book an appointment, generates a Booking ID, stores the booking in Google Sheets, and notifies the doctor via Telegram. Triggers when a patient messages your Telegram bot, extracts the Booking ID from the message, and replies with instructions if the ID is missing or invalid. When the Booking ID is valid, updates the matching Google Sheets row to Confirmed, sends a confirmation message to the patient on Telegram, and creates a Google Calendar event. Reads the confirmed appointment details from Google Sheets and sends the full patient and appointment information to the doctor via Telegram. Receives a POST webhook request with post-visit prescription details, updates the matching Google Sheets row to “Prescription Sent,” emails the prescription link and medicines to the patient via Gmail, and sends the same details via Telegram. Runs every h
Calculate litigation deadlines from intake forms with Google Calendar, Sheets, Slack and Gmail
Quick Overview This workflow collects litigation matter intake details via an n8n form, calculates limitation and procedural deadlines using a built-in rules table, then creates deadline and reminder events in Google Calendar, logs each deadline to Google Sheets, and sends a summary via Slack and Gmail. How it works Receives a submission from an n8n form with the matter details, jurisdiction, claim type, and trigger dates. Loads the configured limitation rules, procedural rules, holidays, reminder offsets, and target Google Calendar/Google Sheets/Slack/email settings. Calculates limitation and procedural due dates (and any review notes) from the provided dates, rolling deadlines off weekends/holidays and generating reminder dates. Appends each calculated deadline record to a Google Sheets register. Creates an all-day Google Calendar event for each calculated deadline and separate all-day events for each upcoming reminder offset. Posts a consolidated deadline summary to a Slack channel and emails the same summary via Gmail to the responsible lawyer (or a fallback team email). Setup Connect credentials for Google Calendar, Google Sheets, Slack, and Gmail. In the rules/settings step,
WURL and IP lookups through Greynoise and VirusTotal
This n8n workflow serves as a powerful cybersecurity and threat intelligence tool to look up URLs or IP addresses through industry standard threat intelligence vendors. It starts with either a form submission or a webhook trigger, allowing users to input data, URLs or IPs that require analysis. The workflow then splits into two paths depending on whether the input data is an IP or URL. If an IP was given, it sets the ip variable to the IP; however if a URL was given the workflow will perform a DNS lookup using Google Public DNS and sets the ip variable based on the results from Google. The workflow then checks the obtained IP addresses against GreyNoise services, with one branch utilizing GreyNoise RIOT IP Lookup to assess IP reputation and association with known benign services, and the other using GreyNoise IP Context to evaluate potential threats. The results from both GreyNoise services are merged to create a comprehensive analysis which includes the IP, classification (benign, malicious, or unknown), IP location, tags to identify activity or malware, category, and trust level. In parallel, a VirusTotal scan is initiated for the URL/IP to identify if it is malicious. A 5-second