Get real-time crypto token insights via Telegram with DexScreener and GPT-4o
Instantly access real-time decentralized exchange (DEX) insights directly in Telegram! This workflow integrates the DexScreener API with GPT-4o-powered AI and Telegram, allowing users to fetch the latest blockchain token analytics, liquidity pools, and trending tokens effortlessly. Ideal for crypto traders, DeFi analysts, and investors who need actionable market data at their fingertips. How It Works A Telegram bot listens for user queries about tokens or trading pairs. The workflow interacts with the DexScreener API (no API key required) to fetch real-time data, including: Token fundamentals (profiles, images, descriptions, and links) Trending and boosted tokens (hyped projects, potential market movers) Trading pair analytics (liquidity, price action, volumes, volatility) Order and payment activity (transaction insights, investor movements) Liquidity pool depth (market stability, capital flows) Multi-chain pair comparisons (performance tracking across networks) An AI-powered language model (GPT-4o-mini) enhances responses for better insights. The workflow logs session data to improve user interaction tracking. The requested DEX insights are sent back via Telegram in an easy-to-read format. What You Can Do with This Agent This AI-driven Telegram bot enables you to: ✅ Track trending and boosted tokens before they gain mainstream traction. ✅ Monitor real-time liquidity pools to assess token stability. ✅ Analyze active trading pairs across different blockchains. ✅ Identify transaction trends by checking paid orders for tokens. ✅ Compare market activity with detailed trading pair analysis. ✅ Receive instant insights with AI-enhanced responses for deeper understanding. Set Up Steps Create a Telegram Bot Use @BotFather on Telegram to create a bot and obtain an API token. Configure Telegram API Credentials in n8n Add your Telegram bot token under Telegram API credentials. Deploy and Test Send a query (e.g., "SOL/USDC") to your Telegram bot and receive real-time insights instantly! 🚀 Unlock powerful, real-time DEX insights directly in Telegram—no API key required! 📺 Setup Video Tutorial Watch the full setup guide on YouTube: [](https://www.youtube.com/watch?v=ZzlxBX6tDbk)
By Don Jayamaha JrAI-powered Scrum Master assistant with OpenAI, Slack and Asana integration
What is This? This automation simulates Scrum Master role on daily meetings. Essentially it is an AI Scrum Master using different sources of data. As intelligent support system for Scrum Masters that leverages data from Asana, Slack, and direct developer responses for comprehensive sprint status analysis and identification of areas requiring intervention. As such it is usable for Scrum Masters (of course) but Scrum Team aswell, Product Owner and possibly Business Owner. Who is it For? This automation is designed for Agile teams to support the Scrum Master role by collecting and analyzing data from various sources to identify potential impediments and support the team in sprint delivery. How Does It Work? The workflow has four main data entry points, that are launched either on-click or on workdays. First is collecting project section information from Asana. The automation retrieves project structure, available sections, and their organization, allowing the AI to understand the team's work context. Second is getting recently modified tasks in the Asana project. The system tracks changes in tasks, their status, assignments, and updates to detect potential delays or issues. Third is obtaining communication in the team's Slack channel. The flow collects data about recent conversations, discussion threads, and team communication to identify warning signals or areas requiring attention. Fourth is directly collecting responses from developers about the current sprint - their progress, impediments, concerns, and support needs. All collected data is passed to an AI model that analyzes it within the Scrum methodology context and identifies: Potential impediments in sprint delivery Areas requiring Scrum Master intervention Recommendations for team support Warning signals regarding Sprint Goal achievement Output is being pushed to Slack channel so it can be potentially used by another iteration of same flow itself via Slack channel history. Requirements You need Asana oAuth credentials You need OpenAI / alternative AI for processing data You need to have Slack app with proper permissions channels:history chat:write groups:history im:history mpim:history users.profile:write users:write Configuration Set up node "Asana Project and Slack Channel". Provide Asana project ID and Slack Channel ID (optional) Set up node "Get Scrum Master Answers". There are daily questions/answers that are being sent to channel. Alternative use You can get rid of the whole "Ask Users Daily ScrumMaster Questions" part if you don't want to do it simirarly as "daily Scrum standups". In such case whole flow is essentially changed to static analyzer of project status based on Slack and Asana. Extensions and Customizations There are many possibilities to extend this automation depending on team needs. For example, you can add integration with additional project management tools, implement different notification schemes based on detected issue criticality, or adjust data collection frequency to match the team's work rhythm. Disclaimers and Notes Whole automation has one important assumption: project is run on single Slack channel and on single Asana board. Of cource this can be extended, but is beyond currently designed scope. Adding new sources for AI to analyze should be fairly easy - just add another branch of data and push it to AI prompt. This automation represents a proof-of-concept and should not replace an actual Scrum Master. The Scrum Master role extends far beyond data collection and analysis - it requires deep understanding of team dynamics, business context, and interpersonal skills. As Scrum.org emphasizes, the Scrum Master doesn't need to be present during Daily Scrum, and their role is to ensure the meeting happens, but developers are responsible for conducting the meeting. Mindlessly executing daily questions without proper context analysis can lead to situations where the Scrum Master becomes a team manager instead of a self-organization facilitator. A real Scrum Master analyzes much more data than what's collected by automation - they observe team dynamics, understand business context, identify deeper root causes of problems, and support the team in developing self-organization skills. AI can be a valuable support tool, but it cannot replace the human intuition, empathy, and experience essential in this role. The automation should be treated as a tool supporting the Teams's work, providing additional insights and helping identify areas requiring attention, but always under the supervision and interpretation of an experienced Scrum practitioner.
By ŁukaszSend WhatsApp bulk messages from Google Sheets
WhatsApp Bulk Message Broadcast via Google Sheets (n8n Workflow) Use Case This workflow enables automated bulk WhatsApp message broadcasting using the WhatsApp Business Cloud API. It pulls recipient and message data from a Google Sheet, sends templated messages (optionally with image headers), and updates the sheet with the message status. It is ideal for marketing teams, support agents, and businesses handling high-volume outreach. --- Who Is This For? Businesses conducting WhatsApp marketing or outreach campaigns Customer support or notification teams Administrators seeking an automated, no-code message distribution system using Google Sheets --- What This Workflow Does Triggers automatically every minute to scan for pending messages Fetches unsent entries from a Google Sheet Limits the number of messages processed per execution to comply with API usage guidelines Sanitizes WhatsApp numbers for proper formatting Sends messages using a pre-approved WhatsApp template (text and optional image) Marks the row as "Sent" in the sheet upon successful delivery --- Workflow Breakdown (Node by Node) Trigger Every 5 Minutes Initiates the workflow every minute using a scheduled trigger to continuously monitor pending rows. Fetch All Pending Queries for Messaging Reads rows from a Google Sheet where the Status column is empty, indicating they haven’t been processed yet. Limit Restricts processing to 2 rows per execution to manage API throughput. Loop Over Items Uses SplitInBatches to iterate through each row individually. Clean WhatsApp Number A code node that strips non-numeric characters from the WhatsApp No field, ensuring the format is valid for the API. Send Message to 300 Phone No Sends a WhatsApp message using the WhatsApp Cloud API and a pre-approved template. Template includes: An image from the Image URL column (as header, optional) Dynamic variables for the recipient's Name and Message fields Template variables must be pre-defined and approved in the Meta Developer Portal, such as {{1}}, {{2}}. Change State of Rows in Sent1 Updates the Status column to Sent for each successfully processed row using the row number as a reference. --- Google Sheet Format Structure your Google Sheet as shown below: | WhatsApp No | Name | Message | Image URL | Status | |--------------|------------|---------------------------|---------------------|--------| | +8801XXXXXXX | John Doe | Hello, your order shipped | https://.../img.jpg | | Leave the Status column empty for rows that need to be processed. --- Requirements WhatsApp Business Cloud API access via Meta for Developers A properly structured Google Sheet as described above Active OAuth2 credentials configured in n8n for: googleSheetsOAuth2Api whatsAppApi --- Customization Options Update the Limit node to control how many rows are processed in each run Adjust the trigger schedule (e.g., change to every 5 minutes) Replace the message template ID with your own custom-approved one from Meta Add error-handling logic (e.g., IF or Try/Catch nodes) to log failures or set Status = Failed --- Sample Sheet Template View Sample Google Sheet --- Workflow Highlights Automated execution every 1 minute Reads and processes only pending records Verifies WhatsApp numbers and delivers templated messages Updates Google Sheet after each attempt --- Support & Community Need help setting up or customizing the workflow? WhatsApp: Contact Support Discord: Join SpaGreen Server Facebook Group: SpaGreen Community Website: Visit SpaGreen Creative
By SpaGreen CreativeAuto-create GitHub PRs & JIRA updates from git commit commands (multi-repo)
This n8n template from Intuz provides a complete and automated solution for scaling your DevOps practices across multiple repositories. Are you tired of the repetitive dance between git push, creating a pull request in GitHub, updating the corresponding task in JIRA, and then manually notifying your team in Slack, or Notion? This template puts your entire post-commit workflow on autopilot, creating a seamless and intelligent bridge between your code and your project management. By embedding specific keywords and a JIRA issue ID into your git commit commands, this workflow automatically creates a Pull Request in the correct GitHub repository and updates the corresponding JIRA ticket. This creates a complete, centralized system that keeps all your projects synchronized, providing a massive efficiency boost for teams managing a diverse portfolio of codebases. Who This Template Is For? This template is a must-have for any organization looking to streamline its software development lifecycle (SDLC). It’s perfect for: Development Teams: Eliminate tedious, manual tasks and enforce a consistent workflow, allowing developers to stay focused on coding. DevOps Engineers: A ready-to-deploy solution that integrates key developer tools without weeks of custom scripting. Engineering Managers & Team Leads: Gain real-time visibility into development progress and ensure processes are followed without constant check-ins. Project Managers: Get accurate, automatic updates in JIRA the moment development work is completed, improving project tracking and forecasting. Step-by-Step Setup Instructions Follow these steps carefully to configure the workflow for your environment. Connect Your Tools (Credentials) GitHub: Create credentials with repo scope to allow PR creation. JIRA: Create an API token and connect your JIRA Cloud or Server instance. Slack: Connect your Slack workspace using OAuth2. Notion: Connect your Notion integration token. Configure the GitHub Webhook (For Each Repository) This workflow is triggered by a GitHub webhook. You must add it to every repository you want to automate. First, Save and Activate the n8n workflow to ensure the webhook URL is live. In the n8n workflow, copy the Production URL from the Webhook node. Go to your GitHub repository and navigate to Settings > Webhooks > Add webhook. In the Payload URL field, paste the n8n webhook URL. Change the Content type to application/json. Under "Which events would you like to trigger this webhook?", select "Just the push event." Click "Add webhook." Repeat this for all relevant repositories. Configure the JIRA Nodes (Crucial Step) Your JIRA project has unique IDs for its statuses. You must update the workflow to match yours. Find the two JIRA nodes named "Update task status after PR" and "Update the task status without PR." In each node, go to the Status ID field. Click the dropdown and select the status that corresponds to "Done" or "Development Done" in your specific JIRA project workflow. The list is fetched directly from your connected JIRA instance. Configure Notification Nodes Tell the workflow where to send updates. For Slack: Open the two nodes named "Send message in slack..." and select your desired channel from the Channel ID dropdown. For Notion: Open the two nodes named "Append a block in notion..." and paste the URL of the target Notion page or database into the Block ID field. Final Activation Once all configurations are complete, ensure the workflow is Saved and the toggle switch is set to Active. You are now ready to automate! Customization Guidance This template is a powerful foundation. Here’s how you can adapt it to your team's specific needs. Changing the PR Title or Body: Go to the "Request to create PR" (HTTP Request) node. In the JSON Body field, you can edit the title and body expressions. For example, you could add the committer's name ({{$('Webhook').item.json.body.pusher.name }}) or a link back to the JIRA task. Adapting to a Fixed Branching Strategy: If your team always creates pull requests against a single branch (e.g., develop), you can simplify the workflow. In the "Request to create PR" node, change the base value in the JSON body from {{...}} to your static branch name: "base": "develop". You can then remove the base branch logic from the "Commit Message Breakdown" (Code) node. Modifying Notification Messages: The text sent to Slack and Notion is fully customizable. Open any of the Slack or Notion nodes and edit the text fields. You can include any data from previous nodes, such as the PR URL ({{ $('Request to create PR').item.json.body.html_url }}) or the repository name. Adjusting the Commit Regex for Different Conventions: This is an advanced customization. If your team uses a different commit format (e.g., (DEV-123) instead of DEV-123), you can edit the regular expression in the "Commit Message Breakdown" (Code) node. Be sure to test your changes carefully. Adding/Removing Notification Channels: Don't use Notion? Simply delete the two Notion nodes. Want to send an email instead? Add a Gmail or SMTP node in parallel with a Slack node and configure it with the same data. Connect with us Website: https://www.intuz.com/services Email: getstarted@intuz.com LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Worflow Automation Click here- Get Started
By Intuz Automated 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 MarthPersonalize candidate feedback with GPT-4o, Google Sheets & Gmail for HR teams
Description This workflow automates personalized candidate communication for both shortlisted and rejected applicants. It fetches candidate details, processes resumes, checks for errors, and uses GPT-4o to generate professional HTML emails. Shortlisted candidates receive congratulatory onboarding plans, while rejected candidates receive polite rejections with learning resources. What This Template Does (Step-by-Step) ⚡ Manual Trigger – Starts the workflow execution. 📑 Candidate Data Fetch (Google Sheets) – Pulls structured candidate data (name, email, resume link, skills, job info, status). 📥 Resume Downloader (Google Drive) – Downloads candidate resumes from sheet links. ✅ Resume File Check (If Condition) – Ensures the resume file is valid before proceeding. ⚠️ Error Logging (Google Sheets) – Records failed or missing resumes in a dedicated sheet for audit. 📄 PDF → Text Extractor – Extracts raw resume text for deeper AI analysis. 🧩 Candidate Data Builder (Code Node) – Combines Google Sheets data with extracted resume text into a single enriched JSON object. 🎯 Shortlisted vs Rejected (If Condition) – Splits candidates into two flows based on their status field. Shortlisted Path 🎉 Congrats + Onboarding Plan (LLM Chain) – GPT-4o generates a congratulatory HTML email including: Identified skill gaps Recommended online courses (Coursera/Udemy/LinkedIn Learning) Next onboarding steps 📧 Candidate Mailer – Shortlisted (Gmail) – Sends the onboarding email directly to the candidate. Rejected Path 🙏 Polite Rejection + Learning Plan (LLM Chain) – GPT-4o generates a professional rejection email including: Empathetic rejection message Constructive feedback on skill gaps Learning resources to improve for future opportunities 📧 Candidate Mailer – Rejected (Gmail) – Sends the polite rejection + learning plan to the candidate. Prerequisites Google Sheets (candidate database + error log) Google Drive (resume storage) Gmail API (for sending candidate emails) Azure OpenAI (GPT-4o-mini model access) Key Benefits ✅ Automates candidate communication (both shortlisted & rejected) ✅ Delivers professional, HTML-ready emails ✅ Enhances candidate experience with personalized learning plans ✅ Prevents silent rejections by providing constructive resources ✅ Improves employer branding with empathetic communication ✅ Error resilience via logging and validation steps Perfect For Recruitment teams managing high candidate volume Companies looking to humanize rejections HR departments that want automated but personalized communication Organizations investing in candidate experience & employer brand
By Rahul Joshi