Build a self-hosted URL shortener with a dashboard
This workflow creates an automatic self-hosted URL shortener. It consists of three sub-workflows: Short URL creation for extracting the provided long URL, generating an ID, and saving the record in the database. It returns a short link as a result. Redirection for extracting the ID value, validating the existence of its correspondent record in the database, and returning a redirection page after updating the visits (click) count. Dashboard for calculating simple statistics about the saved record and displaying them on a dashboard. Read more about this use case and how to set up the workflow in the blog post How to build a low-code, self-hosted URL shortener in 3 steps. Prerequisites A local proxy set up that redirects the n8n.ly domain to your n8n instance An Airtable account and credentials Basic knowledge of JavaScript, HTML, and CSS Nodes Webhook nodes trigger the sub-workflows on calls to a specified link. IF nodes route the workflows based on specified query parameters. Set nodes set the required values returned by the previous nodes (id, longUrl, and shortUrl). Airtable nodes retrieve records (values) from or append records to the database. Function node calculates statistics on link clicks to be displayed on the dashboard, as well as its design. Crypto node generates a SHA256 hash.
By mohamed aliSend outreach/cold email using Gmail to new HubSpot contacts
Use case This workflow uses Gmail to send outreach emails to new Hubspot contacts that have yet to be contacted (usually unknown contacts), and records the outreach in Hubspot. Setup Setup HubSpot Oauth2 creds (Be careful with scopes. They have to be exact, not less or more. Yes, it's not simple, but it's well documented in the n8n docs. Be smarter than me, read the docs) Setup Gmail creds. Change the from email and from name in the Record outreach in HubSpot node How to adjust this template to your needs Change the email message in the Set keys node Think about your criteria to reach out to new contacts. Here we simply filter for only contacts with unknown dates.
By MutasemAutomated CVE scanning of Bug Bounty programs with Nuclei and Project Discovery
Description Automates daily CVE-driven scanning against bug bounty scopes. It fetches bug-bounty domains, pulls newly published Project Discovery templates, converts them to Nuclei rules, runs targeted scans, and emails findings. Objective Help security researchers and bug bounty hunters discover exploitable instances quickly by automatically running the latest public templates from Project Discovery against a consolidated bug-bounty scope. Reduce manual steps and maintain continuous reconnaissance. How it works The workflow accepts or fetches a domain list that covers HackerOne, Bugcrowd, Intigriti, and YesWeHack. It downloads the latest public templates from Project Discovery. For each new template published since the last run it: creates a file, uploads it to a remote host, and converts it to a Nuclei-compatible YAML. It uploads a consolidated domains wordlist to the remote host. It executes Nuclei with the new templates against the domains list using configured flags (concurrency, rate limits, severity tags). It collects and deduplicates Nuclei output. If results exist, it sends the findings via Gmail. Requirements • SSH access (root or equivalent) to a VPS or host. • Nuclei installed on the remote host. • Gmail OAuth2 credentials for sending notifications. • Recommended: VPS with enough CPU and network capacity for concurrent scanning when scope is large.
By Javier RieiroExtract & analyze Amazon reviews with Apify, Gemini AI & save to Google Sheets
Template Description 📝 Template Title Analyze Amazon product reviews with Gemini and save to Google Sheets 📄 Description This workflow automates the process of analyzing customer feedback on Amazon products. Instead of manually reading through hundreds of reviews, this template scrapes reviews (specifically targeting negative feedback), uses Google Gemini (AI) to analyze the root causes of dissatisfaction, and generates specific improvement suggestions. The results are automatically logged into a Google Sheet for easy tracking, and a Slack notification is sent to keep your team updated. This tool is essential for understanding "Voice of Customer" data efficiently without manual data entry. 🧍 Who is this for Product Managers looking for product improvement ideas. E-commerce Sellers (Amazon FBA, D2C) monitoring brand reputation. Market Researchers analyzing competitor weaknesses. Customer Support Teams identifying recurring issues. ⚙️ How it works Data Collection: The workflow triggers the Apify actor (junglee/amazon-reviews-scraper) to fetch reviews from a specified Amazon product URL. It is currently configured to filter for 1 and 2-star reviews to focus on complaints. AI Analysis: It loops through each review and sends the content to Google Gemini. The AI determines a sentiment score (1-5), categorizes the issue (Quality, Design, Shipping, etc.), summarizes the complaint, and proposes a concrete improvement plan. Formatting: A Code node parses the AI's response to ensure it is in a clean JSON format. Storage: The structured data is appended as a new row in a Google Sheet. Notification: A Slack message is sent to your specified channel to confirm the batch analysis is complete. 🛠️ Requirements n8n (Self-hosted or Cloud) Apify Account: You need to rent the junglee/amazon-reviews-scraper actor. Google Cloud Account: For accessing the Gemini (PaLM) API and Google Sheets API. Slack Account: For receiving notifications. 🚀 How to set up Apify Config: Enter your Apify API token in the credentials. In the "Run an Actor" node, update the startUrls to the Amazon product page you want to analyze. Google Sheets: Create a new Google Sheet with the following header columns: sentiment_score, category, summary, improvement. Copy the Spreadsheet ID into the Google Sheets node. AI Prompt: The "Message a model" node contains the prompt. It is currently set to output results in Japanese. If you need English output, simply translate the prompt text inside this node. Slack: Select the channel where you want to receive notifications in the Slack node.
By 小林幸一Generate and schedule AI discussion posts for Reddit with GPT-4 and Airtable
How the sequence works: A "Schedule Trigger" node activates the automation at a defined schedule. An "Airtable" node will search for previously posted questions in your question database. Airtable Base Template: here An "Aggregate" node will take all the questions from Airtable and compress them to a single output. ChatGPT, or a model of your choice, will generate a discussion question based on the options in the system prompt. The discussion question will be posted to the subreddit of your choice by the "Reddit" node. You can choose between a text, image, or link post! The recently-posted discussion question will then be uploaded to your Airtable base using the "Airtable" node. This will be used to prevent ChatGPT from creating duplicate questions. Setup Steps The setup process will take about 5 minutes. An Airtable base template is also pre-made for you here: https://airtable.com/app6wzQqegKIJOiOg/shrzy7L9yv8BFRQdY Set the recurrence in the "Schedule" node Create an Airtable account, you can use the link here. Get an Airtable personal access token here. Configure the "Get Previous Discussions" Airtable node. Configure the options in brackets in the "Generate New Discussion" node. Set the desired subreddit to post to and the post type(text, image, or link) in the "Post Discussion" node. Configure the "Create Archived Discussion" node to map to the Airtable base(required) and specific subreddit(optional).
By Josh UniverseAutomate support ticket prioritization with Jotform, Gemini AI, ClickUp tasks
Automated Support Prioritization and AI Task Creation This n8n workflow instantly captures support issues submitted via Jotform and efficiently routes them to the appropriate team and logging system based on the severity level defined by the customer. It then uses an AI Agent (Google Gemini) to transform the raw customer data into a clear, concise, and actionable task for the development team. Workflow Overview Ingestion & Logging: A new support ticket is received via Jotform and immediately logged into a Google Sheet as a central record. Priority Assessment & Routing: An If node checks the reported issue Severity. High/Medium Severity: The ticket details are instantly sent to a dedicated Slack channel for immediate team attention. Low Severity: The ticket details are sent via Gmail (acting as an internal email notification) to a support inbox, allowing for less immediate handling. AI Processing: An AI Agent summarizes the raw feedback into a clear, professional task description. Task Creation: The AI-generated task is automatically created in ClickUp for the development team to manage. Requirements To implement and run this automated support workflow, the following accounts and credentials are required: Service Credentials Jotform API Key: For the Jotform Trigger to receive real-time form submissions. Google Sheets OAuth2/API Key: To write data to the designated sheet. Slack OAuth2/API Key: To post messages to the target Slack channel. Gmail OAuth2/API Key: To send internal email notifications. Google Gemini API Key: To power the AI Agent for task summarization. ClickUp API Key: To create tasks in the target workspace. Sign up for n8n using: https://n8n.partnerlinks.io/pe6gzwqi3rqw External Configurations Jotform Setup: A form configured with fields for Name, Email, Issue, Description, and the crucial Severity field. Sign up for Jotform using: https://www.jotform.com/?partner=zainurrehman ClickUp Setup: The specific Team, Space, Folder, and List IDs must be configured in the Create a task node to ensure tickets are created in the correct project board.
By Zain KhanAutomated recruitment process with Slack, DocuSign, Trello & Gmail notifications
How It Works & Setup Guide for the Automated Candidate Management & Feedback System This guide will walk you through setting up your n8n workflow. By the end, you'll have a fully automated system for managing your recruitment pipeline. --- How It Works: The Workflow Explained This workflow is designed in three logical phases to handle the entire post-interview process automatically. Phase 1: Trigger & Feedback Loop: The workflow triggers when an interview ends on your Google Calendar. It immediately sends a Slack message to the interviewer with a link to the feedback form. After a 2-hour wait, it checks if the feedback has been submitted. If not, it sends a reminder. Once feedback is received, it logs the data in Airtable and uses an If node to determine if the candidate has passed or failed. Phase 2: Automated Communication: Based on the candidate's status, the workflow sends a personalized and professional email using Gmail. For candidates who pass, it sends a follow-up invitation. For those who don't, it sends a polite rejection email crafted by a Code node. If a candidate is in the final stage and passes, the workflow automatically generates and sends an offer letter for signature via DocuSign. Phase 3: Onboarding & Reporting: Once a candidate accepts the offer (by signing the document), the workflow is triggered to create a new task list in Trello for the HR team. It sends a personalized welcome email to the new hire and a notification to the team on Slack. Finally, a Cron Trigger runs every Friday to collect all candidate data, calculate key recruitment metrics, log them in Google Sheets, and send a summary report to your team on Slack. --- Step-by-Step Setup Guide Follow these steps to configure the workflow in your n8n instance. Step 1: Prerequisites Before you begin, ensure you have the following accounts and a workspace set up: n8n Google Calendar, Google Sheets, Gmail Airtable Slack Trello DocuSign Step 2: Database & Form Preparation Airtable: Create a new Airtable base with two tables: Candidates Table: Create columns for Candidate Name, Email, Interviewer ID, Interview Date, and Status. Feedback Table: Create columns for Candidate Name, Overall Score, and Comments. Feedback Form: Create a feedback form (e.g., using Google Forms or Typeform) that collects the candidate's name, the interviewer's name, and a score/comments. Step 3: Import the Workflow In your n8n instance, click "New" and select "Import from File". Import the .json file you purchased. The entire workflow, with all nodes, will appear on your canvas. Step 4: Configure Credentials Click on any node with a red "!" icon (e.g., the Google Calendar Trigger or Slack node). In the right-hand panel, click "Create new credential". Follow the on-screen instructions to connect your accounts. Repeat this process for all nodes that require credentials. Step 5: Node-Specific Configuration Now, let's configure the specific details for each node to ensure it works for your company. Google Calendar Trigger: Click on the node and in the Calendar ID field, enter the ID of the calendar you use for scheduling interviews. Airtable Nodes: For every Airtable node in the workflow, enter the correct Base ID and Table Name (Candidates or Feedback) that you created in Step 2. Trello Node: Enter the Board ID and the specific List ID where you want new onboarding tasks to be created. Gmail Nodes: Customize the Subject and HTML Body of the emails to match your company's tone and branding. DocuSign Node: Enter your Account ID and the Template ID for your offer letter. Ensure your offer letter template includes the anchorString (e.g., /s1/) that the workflow uses to place the signature tag. Environment Variables: In your n8n settings, go to Environment Variables and add the following: FEEDBACKFORMURL: The URL of your feedback form. SCHEDULING_LINK: The URL for candidates to schedule their next interview. REPORTSDASHBOARDURL: A link to your Google Sheets report or a separate dashboard. Step 6: Final Step - Activating the Workflow Once all nodes are configured, click "Save" at the top of the canvas. Click the "Active" toggle in the top right corner. The workflow is now live! Final Tip: It's a good practice to test the system once by creating a test interview event on your calendar to ensure all steps run as expected.
By MarthGitHub to Jira bug sync with GPT-4o analysis & team alerts
Automate Bug Reports: GitHub Issues → AI Analysis → Jira Tickets with Slack & Discord Alerts Automatically convert GitHub issues into analyzed Jira tickets with AI-powered severity detection, developer assignment, and instant team alerts. Overview This workflow captures GitHub issues in real-time, analyzes them with GPT-4o for severity and categorization, creates enriched Jira tickets, assigns the right developers, and notifies your team across Slack and Discord—all automatically. Features AI-Powered Triage: GPT-4o analyzes bug severity, category, root cause, and generates reproduction steps Smart Assignment: Automatically assigns developers based on mentioned files and issue context Two-Way Sync: Posts Jira ticket links back to GitHub issues Multi-Channel Alerts: Rich notifications in Slack and Discord with action buttons Time Savings: Eliminates 15-30 minutes of manual triage per bug Customizable Routing: Easy developer mapping and priority rules What Gets Created Jira Ticket: Original GitHub issue details with reporter info AI severity assessment and categorization Reproduction steps and root cause analysis Estimated completion time Automatic labeling and priority assignment GitHub Comment: Jira ticket link AI analysis summary Assigned developer and estimated time Team Notifications: Severity badges and quick-access buttons Developer assignment and root cause summary Color-coded priority indicators Use Cases Development teams managing 10+ bugs per week Open source projects handling community reports DevOps teams tracking infrastructure issues QA teams coordinating with developers Product teams monitoring user-reported bugs Setup Requirements Required: GitHub repository with admin access Jira Software workspace OpenAI API key (GPT-4o access) Slack workspace OR Discord server Customization Needed: Update developer email mappings in "Parse GPT Response & Map Data" node Replace YOURJIRAPROJECT_KEY with your project key Update Slack channel name (default: dev-alerts) Replace YOURDISCORDWEBHOOK_URL with your webhook Change your-company.atlassian.net to your Jira URL Setup Time: 15-20 minutes Configuration Steps Import workflow JSON into n8n Add credentials: GitHub OAuth2, Jira API, OpenAI API, Slack, Discord Configure GitHub webhook in repository settings Customize developer mappings and project settings Test with sample GitHub issue Activate workflow Expected Results 90% faster bug triage (20 min → 2 min per issue) 100% consistency in bug analysis Zero missed notifications Better developer allocation Improved bug documentation Tags GitHub, Jira, AI, GPT-4, Bug Tracking, DevOps, Automation, Slack, Discord, Issue Management, Development, Project Management, OpenAI, Webhook, Team Collaboration
By Shelly-Ann Davy