Cryptocurrency volume/mCap screener - automated trading alerts to Discord
Purpose & Audience
This n8n workflow template is designed for cryptocurrency traders, investors, and market analysts who want to automate the process of detecting unusual trading activity across 1,250+ cryptocurrencies. By continuously monitoring volume-to-market-cap ratios and price movements, the workflow delivers real-time alerts directly to your Discord server—helping you catch potential breakouts, pump schemes, or high-impact market events before they become mainstream news.
What It Does
- Monitors 1,250+ cryptocurrencies from CoinGecko every 4 hours for unusual trading patterns
- Calculates volume-to-market-cap ratios to identify coins with abnormally high trading activity (>30% ratio or >$100M volume with significant price movement)
- Ranks and filters the top volume alerts based on trading intensity
- Sends beautifully formatted Discord embeds with coin metrics, price changes, market cap, and direct CoinGecko links
- Provides context with educational information about what volume/MCap ratios mean and trading warnings
Who Is It For
- Day traders and scalpers seeking early signals for high-volatility opportunities
- Market analysts who want automated surveillance of unusual market activity across hundreds of coins
- Discord community managers looking to provide valuable trading insights to their members
- Anyone interested in catching potential pumps, breakouts, or news-driven price movements before the crowd
Setup once and let it run 24/7. The workflow automatically scans the market every 4 hours and only sends alerts when something significant is detected. Customize the alert thresholds, add more coins, or adjust the schedule to fit your trading style. No coding required—just connect your CoinGecko API and Discord webhook, and you're ready to catch the next big move!
How to Set Up
- Obtain a free CoinGecko API key and create a Discord webhook for your server
- Import the workflow and add your API credentials
- Customize alert thresholds and update frequency to match your trading preferences
- That's it—receive real-time volume alerts for potential trading opportunities automatically
Preview:
Cryptocurrency Volume/MCAP Screener - Automated Trading Alerts to Discord
This n8n workflow automates the process of fetching cryptocurrency data, applying custom screening logic, and sending alerts to Discord. It's designed for traders and enthusiasts who want to stay informed about significant market movements based on volume and market capitalization.
What it does
This workflow performs the following steps:
- Triggers on a schedule: The workflow runs automatically at predefined intervals.
- Fetches cryptocurrency data: It makes an HTTP request to an external API to retrieve current cryptocurrency market data.
- Applies conditional logic: It uses an "If" node to evaluate conditions on the fetched data, likely filtering for cryptocurrencies that meet specific criteria (e.g., high volume, significant market cap changes).
- Processes filtered data: The data that passes the "If" condition is then processed further.
- Handles non-matching data: Data that does not meet the "If" condition is also processed, potentially for logging or alternative notifications.
- Merges data streams: It combines the results from both the "true" and "false" branches of the "If" node.
- Executes custom code: A "Code" node is present, indicating custom JavaScript logic is applied to the data. This could be for further data manipulation, formatting, or more complex calculations before sending alerts.
- Sends alerts (implied): Although not explicitly shown in the provided JSON (which only contains core nodes), the typical next step for such a workflow, especially given the directory name, would be to send the processed alerts to a platform like Discord using a dedicated node (e.g., a Discord node).
Prerequisites/Requirements
- n8n Instance: A running n8n instance to host and execute the workflow.
- Cryptocurrency API: Access to a cryptocurrency market data API (e.g., CoinGecko, CoinMarketCap, or similar) from which the "HTTP Request" node will fetch data. You will need the API endpoint and any necessary authentication headers/parameters.
- Discord Account/Webhook (implied): A Discord server and a webhook URL configured to receive messages, if the goal is to send alerts to Discord. This would require an additional Discord node in the workflow.
Setup/Usage
- Import the workflow: Download the provided JSON and import it into your n8n instance.
- Configure the Schedule Trigger: Adjust the "Schedule Trigger" node to your desired frequency for checking cryptocurrency data (e.g., every 5 minutes, hourly).
- Configure the HTTP Request node:
- Set the
URLto your chosen cryptocurrency API endpoint. - Add any required
Headers(e.g., API keys) orQuery Parametersfor authentication or data filtering. - Ensure the
Methodis set correctly (likely GET).
- Set the
- Configure the If node:
- Define the conditions for screening cryptocurrencies based on your trading strategy (e.g.,
volume > 100000000 && marketCapChange24h > 0.1). Use expressions to reference data from the previous "HTTP Request" node.
- Define the conditions for screening cryptocurrencies based on your trading strategy (e.g.,
- Configure the Code node:
- Review and modify the JavaScript code within this node to perform any specific data transformations, calculations, or message formatting you need for your alerts.
- Add Discord (or other) notification node (if not already present):
- Connect a "Discord" node (or your preferred notification service like Slack, Telegram, Email) after the "Code" node.
- Configure the notification node with your webhook URL or API credentials.
- Map the output from the "Code" node to the message content of your notification node to send formatted alerts.
- Activate the workflow: Once configured, activate the workflow in n8n.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte