n8n Crypto Crash Alert: CoinGecko + Gemini + Slack

n8n Crypto Crash Alert that combines CoinGecko price signals, Gemini analysis, and Slack notifications

This n8n workflow monitors a crypto asset every 4 hours, detects crash conditions using CoinGecko data, and—when thresholds are breached—generates a structured market assessment with Google Gemini and posts a ready-to-act alert to Slack.

What this workflow does

• Runs on a 4-hour schedule to keep crypto monitoring continuous without manual checks.
• Pulls price data from CoinGecko: the current USD price plus the last 24 hours of market chart data for your configured asset.
• Calculates crash metrics, including 24h change and drop from the 24h high, then evaluates two crash conditions: an absolute floor and a percentage-drop crash threshold (as configured in the workflow settings).
• Fetches related headlines via Marketaux for the asset ticker when a crash is detected, formatting top headlines for context.
• Generates a structured assessment with Google Gemini (Google PaLM): severity, headline, summary, key drivers, and a recommendation based on the price stats + news.
• Posts a formatted alert to Slack, combining computed price metrics, the Gemini output, and the selected top headlines in the chosen channel.

Use cases

• For SaaS operators who need near-real-time crypto risk awareness for treasury, payments, or pricing exposure.
• For automation engineers building a production-ready n8n monitoring pipeline that triggers only on meaningful market moves.
• For crypto teams who want automated Slack alerts with both quantitative thresholds (CoinGecko) and qualitative context (Marketaux + Gemini).

Technical details

• Schedule-based automation: every 4 hours
• Integrations: CoinGecko (HTTP Header Auth), Marketaux (HTTP Query Auth), Google Gemini using the Google PaLM model, and Slack (Slack OAuth)
• Core n8n nodes mentioned in the workflow: if, set, code, slack, plus http request and a sticky note

Setup required: add/verify CoinGecko, Marketaux, Google Gemini, and Slack credentials; then configure asset ID/ticker, crash thresholds (absolute floor and percent drop), and news limit.