HTTP Request and Trello integration

Description This workflow is designed for B2B/SaaS teams who want to secure renewals before it’s too late. It runs every day, identifies all accounts whose licenses are up for renewal in J–30, enriches them with CRM, product usage and support data, computes an internal churn risk level, and then triggers the appropriate playbook: HIGH risk** → full escalation (tasks, alerts, emails) MEDIUM risk** → proactive follow-up by Customer Success LOW risk** → light renewal touchpoint / monitoring Everything is logged into a database table so that you can build dashboards, run analysis, or plug additional automations on top. How it works Daily detection (J–30 renewals) A scheduled trigger runs every morning and queries your database (Postgres / Supabase) to fetch all active subscriptions expiring in 30 days. Each row includes the account identifier, name, renewal date and basic commercial data. Data enrichment across tools For each account, the workflow calls several business systems to collect context: HubSpot → engagement history Salesforce → account profile and segment Pipedrive → deal activities and associated products Analytics API → product feature usage and activity trends Zendesk → recent support tickets and potential friction signals All of this is merged into a single, unified item. Churn scoring & routing An internal scoring step evaluates the risk for each account based on multiple signals (engagement, usage, support, timing). The workflow then categorizes each account into one of three risk levels: HIGH – strong churn signals → needs immediate attention MEDIUM – some warning signs → needs proactive follow-up LOW – looks healthy → light renewal reminder A Switch node routes each account to the relevant playbook. Automated playbooks 🔴 HIGH risk Create a Trello card on a dedicated “High-Risk Renewals” board/list Create a Jira ticket for the CS / AM team Send a Slack alert in a designated channel Send a detailed email to the CSM and/or account manager 🟠 MEDIUM risk Create a Trello card in a “Renewals – Follow-up” list Send a contextual email to the CSM to recommend a proactive check-in 🟢 LOW risk Send a soft renewal email / internal note to keep the account on the radar Logging & daily reporting For every processed account, the workflow prepares a structured log record (account, renewal date, risk level, basic context). A Postgres node is used to insert the data into a churn_logs table. At the end of each run, all processed accounts are aggregated and a daily summary email is sent (for example to the Customer Success leadership team), listing the renewals and their risk levels. Requirements Database A table named churn_logs (or equivalent) to store workflow decisions and history. Example fields: account_id, account_name, end_date, riskScore, riskLevel, playbook, trello_link, jira_link, timestamp. External APIs HubSpot (engagement data) Salesforce (account profile) Pipedrive (deals & products) Zendesk (support tickets) Optional: product analytics API for usage metrics Communication & task tools Gmail (emails to CSM / AM / summary recipients) Slack (alert channel for high-risk cases) Trello (task creation for CS follow-up) Jira (escalation tickets for high-risk renewals) Configuration variables Thresholds are configured in the Init config & thresholds node: days_before_renewal churn_threshold_high churn_threshold_medium These parameters let you adapt the detection window and risk sensitivity to your own business rules. Typical use cases Customer Success teams who want a daily churn watchlist without exporting spreadsheets. RevOps teams looking to standardize renewal playbooks across tools. SaaS companies who need to prioritize renewals based on real risk signals rather than gut feeling. Product-led organizations that want to combine usage data + CRM + support into one automated process. Tutorial video Watch the Youtube Tutorial video About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

Automated workflow that transforms BuiltWith technology data into actionable sales leads in Trello, creating a visual sales pipeline. 🚀 What It Does Converts tech stack data into Trello cards Organizes leads by technology stack Tracks sales pipeline stages Enables team collaboration Updates automatically 🎯 Perfect For Sales teams Business development Account executives Tech startups Digital agencies ⚙️ Key Benefits ✅ Visual sales pipeline ✅ Easy lead qualification ✅ Team collaboration ✅ Technology-based filtering ✅ Automated data entry 🔧 What You Need BuiltWith API access Trello account n8n instance Google account (for authentication) 📊 Data Mapped to Trello Company details Technology stack Contact information Website metrics Custom labels 🛠️ Setup & Support Quick Setup Start in 20 minutes with our step-by-step guide 📺 Watch Tutorial 💼 Get Expert Support 📧 Direct Help Turn technology intelligence into sales opportunities with automated lead management.

Transform your lead generation process with this powerful n8n workflow that automatically captures form submissions from Google Forms and creates organized lead cards in Trello. 🎯 Who Is This For? This workflow is perfect for: Sales teams who need to quickly organize and track incoming leads. Marketing professionals running lead generation campaigns Small business owners wanting to streamline their customer acquisition process Consultants and service providers collecting client information through forms Anyone who wants to eliminate manual data entry between forms and project management tools 🛠️ Tools Involved & Prerequisites Required Tools: n8n Google Forms - for lead capture forms Trello - for lead management and organization Prerequisites: Active Google account with Forms access Trello account with board creation permissions ⚙️ How It Works This workflow automatically transforms Google Form submissions into organized Trello cards for lead management: Form Trigger: When someone submits your Google Form, the workflow instantly captures all their information Data Mapping: The system takes the form responses and maps them to the appropriate Trello card fields Trello Card Creation: Each lead becomes a structured Trello card with the person's name and company as the title, plus all form data organized in custom fields 🚀 Setup Instructions Import the workflow template into your n8n instance Access the set up instructions here: https://www.notion.so/Google-Forms-to-Trello-Automation-Setup-Instructions-213718e8c6ba807f9972ff2f81f1057a?source=copy_link

Summarize Trello board activity with Gemini AI and post updates to Slack Who is this for Project managers and development teams using Trello for task management who want automated daily standup summaries without manual effort. Perfect for remote teams that need consistent project visibility and communication. What it does This workflow automatically generates intelligent daily standup reports from your Trello board activity. Every business day at 5 PM, it collects cards created and updated during the day, sends the data to Gemini AI for analysis, and distributes a human-readable summary via Slack and email. The workflow also logs daily metrics to Google Sheets and sends alerts for overdue cards. The AI summary includes activity stats, new work highlights, progress updates, blockers, and suggested priorities for the next day. How to set up Connect your Trello, Slack, Gmail, and Google Sheets accounts in n8n Get a Gemini API key from Google AI Studio and add it as an HTTP header credential Replace placeholder values in the Configuration Settings node: your Trello board ID, Slack channel, team email addresses, and Google Sheets ID Create a "Standup Metrics" sheet in your Google Sheets with columns: Date, New Cards, Updated Cards, Overdue Cards, Board ID Test with a manual execution before enabling the schedule Requirements Trello account with API access Slack workspace with bot permissions Gmail account Google Sheets document Gemini API key (free tier available) How to customize Modify the Gemini prompt in the Generate AI Summary node to change the summary style or add specific insights. Adjust the schedule trigger timing, change the overdue threshold logic in the code node, or extend to multiple Trello boards by duplicating the data collection nodes.

Lead Scoring Pipeline with Mattermost and Trello This workflow automatically enriches incoming form-based leads, calculates a lead-score from multiple data points, and then routes high-value prospects to a Mattermost alert channel while adding all leads to Trello for further handling. It centralizes lead intelligence and streamlines sales team triage—no manual spreadsheet work required. Pre-conditions/Requirements Prerequisites n8n instance (self-hosted or n8n cloud) ScrapeGraphAI community node installed Active Trello and Mattermost workspaces Lead-capture form or webhook that delivers JSON payloads Required Credentials Trello API Key & Token** – Access to the board/list where cards will be created Mattermost Access Token** – Permission to post messages in the target channel (Optional) Clearbit / Apollo / 3rd-party enrichment keys** – If you replace the sample enrichment HTTP requests Specific Setup Requirements | Variable | Purpose | Example Value | |-------------------------|-------------------------------------------|------------------------| | MM_CHANNEL_ID | Mattermost channel to post high-score leads | leads-alerts | | TRELLO_BOARD_ID | Board where new cards are added | 62f1d… | | TRELLO_LIST_ID_HOT | Trello list for hot leads | Hot Deals | | TRELLO_LIST_ID_BACKLOG| Trello list for all other leads | New Leads | | LEAD_SCORE_THRESHOLD | Score above which a lead is considered hot| 70 | How it works This workflow grabs new leads at a defined interval, enriches each lead with external data, computes a custom score, and routes the lead: high-scorers trigger a Mattermost alert and are placed in a “Hot Deals” list, while the rest are stored in a “Backlog” list on Trello. All actions are fully automated and run unattended once configured. Key Steps: Schedule Trigger**: Runs every 15 minutes to poll for new form submissions. HTTP Request – Fetch Leads**: Retrieves the latest unprocessed leads from your form backend or CRM API. Split In Batches**: Processes leads 20 at a time to respect API rate limits. HTTP Request – Enrich Lead**: Calls external enrichment (e.g., Clearbit) to append company and person data. Code – Calculate Score**: JavaScript that applies weightings to enriched attributes and outputs a numeric score. IF – Score Threshold**: Branches flow based on LEAD_SCORE_THRESHOLD. Mattermost Node**: Sends a rich-text message with lead details for high-score prospects. Trello Node (Hot List)**: Creates a Trello card in the “Hot Deals” list for high-value leads. Trello Node (Backlog)**: Creates a Trello card in the “New Leads” list for everyone else. Merge & Flag Processed**: Marks leads as processed to avoid re-processing in future runs. Set up steps Setup Time: 10–15 minutes Import the Workflow: Download the JSON template and import it into n8n. Create / Select Credentials: Add your Trello API key & token under Trello API credentials. Add your Mattermost personal access token under Mattermost API credentials. Configure Environment Variables: Set MM_CHANNEL_ID, TRELLO_BOARD_ID, TRELLO_LIST_ID_HOT, TRELLO_LIST_ID_BACKLOG, and LEAD_SCORE_THRESHOLD in n8n → Settings → Environment. Form Backend Endpoint: Update the first HTTP Request node with the correct URL and authentication for your form or CRM. (Optional) Enrichment Provider: Replace the sample enrichment HTTP Request with your chosen provider’s endpoint and credentials. Test Run: Execute the workflow manually with a sample payload to ensure Trello cards and Mattermost messages are produced. Activate: Enable the workflow; it will now run on the defined schedule. Node Descriptions Core Workflow Nodes: Schedule Trigger** – Triggers workflow every 15 minutes. HTTP Request (Fetch Leads)** – Pulls unprocessed leads. SplitInBatches** – Limits processing to 20 leads per batch. HTTP Request (Enrich Lead)** – Adds firmographic & technographic data. Code (Calculate Score)** – JavaScript scoring algorithm; outputs score field. IF (Score ≥ Threshold)** – Determines routing path. Mattermost** – Sends formatted message with lead summary & score. Trello (Create Card)** – Adds lead as a card to the appropriate list. Merge (Flag Processed)** – Updates source system to mark lead as processed. Data Flow: Schedule Trigger → HTTP Request (Fetch Leads) → SplitInBatches → HTTP Request (Enrich Lead) → Code (Calculate Score) → IF IF (Yes) → Mattermost → Trello (Hot List) IF (No) → Trello (Backlog) Both branches → Merge (Flag Processed) Customization Examples Adjust Scoring Weights // Code node: adjust weights to change scoring logic const weights = { industry: 15, companySize: 25, jobTitle: 20, intentSignals: 40 }; Dynamic Trello List Mapping // Use a Lookup table instead of IF node const mapping = { hot: 'TRELLO_LIST_ID_HOT', cold: 'TRELLO_LIST_ID_BACKLOG' }; items[0].json.listId = mapping[items[0].json.segment]; return items; Data Output Format The workflow outputs structured JSON data: { "leadId": "12345", "email": "[email protected]", "score": 82, "priority": "hot", "trelloCardUrl": "https://trello.com/c/abc123", "mattermostPostId": "78yzk9n8ppgkkp" } Troubleshooting Common Issues Trello authentication fails – Ensure the token has write access and that the API key & token pair belong to the same Trello account. Mattermost message not sent – Confirm the token can post in the target channel and that MM_CHANNEL_ID is correct. Performance Tips Batch leads in groups of 20–50 to avoid enrichment API rate-limit errors. Cache enrichment responses for repeat domains to reduce API calls. Pro Tips: Add a second IF node to send ultra-high (>90) scores directly to an account executive via email. Store raw enrichment responses in a database for future analytics. Use n8n’s built-in Execution Data Save to debug edge-cases without rerunning external API calls.

Verified Beta Tester Access Kit - Automated Onboarding System Transform Your Beta Testing Program Automate your entire beta tester onboarding process from signup to tracking with this comprehensive, production-ready n8n workflow. 📚 CATEGORY TAGS Primary Category: ✅ Marketing & Sales Additional Tags: Automation Email Marketing User Management Onboarding SaaS Product Launch Beta Testing Access Control What This Workflow Does When a beta tester signs up through your form or API, this workflow automatically: ✅ Verifies Email Authenticity - Uses VerifiEmail API to validate addresses and block disposable emails ✅ Generates Unique Access Codes - Creates secure BETA-XXXXXX codes with timestamps ✅ Creates QR Codes - Generates scannable codes for quick mobile activation ✅ Builds Branded Access Cards - Produces professional HTML/CSS cards with tester details ✅ Converts to Images - Transforms cards into shareable PNGs ✅ Sends Welcome Emails - Delivers beautifully formatted emails via Gmail ✅ Logs in Trello - Creates organized tracking cards automatically ✅ Returns API Responses - Sends success/error responses with complete data Complete execution time: 5-10 seconds per signup Perfect For 🚀 SaaS startups launching beta programs 📱 Mobile app developers managing beta testers 🎮 Game studios running closed beta tests 🏢 Enterprise teams controlling early access 💼 Product managers organizing user testing 🔬 Research projects managing participants Key Features Security First Real-time email validation Blocks disposable email addresses Unique, non-guessable access codes Webhook authentication ready Professional Branding Customizable HTML/CSS templates Embedded QR codes Responsive email design High-quality PNG generation Team Collaboration Automatic Trello card creation Organized tracking boards Checklist items for follow-ups Easy team assignments Production Ready Comprehensive error handling Detailed logging Scalable architecture Easy integration What You'll Need Required API Keys (All Have Free Tiers): VerifiEmail - Email verification at https://verifi.email HTMLCSSToImage - Image generation at https://htmlcsstoimg.com Gmail Account - Email delivery Trello Account - Project tracking at https://trello.com/app-key Workflow Steps Webhook receives POST request with tester data VerifiEmail validates email authenticity Conditional logic routes valid/invalid emails Function generates unique BETA-XXXXXX access codes HTTP Request creates QR code image Set node stores QR code URL HTMLCSSToImage converts access card to PNG Gmail sends branded welcome email with kit Trello creates tracking card in board Webhook responds with success/error status Sample Request POST to webhook: { "tester_name": "Aarav Mehta", "tester_email": "[email protected]", "product_name": "YourApp v1.0", "signup_date": "2025-11-05" } Success Response (200): { "status": "success", "message": "Beta tester verified and access kit delivered", "data": { "tester_name": "Aarav Mehta", "access_code": "BETA-A7K9M2", "trello_card_created": true, "email_sent": true, "qr_code_generated": true } } Error Response (400): { "status": "error", "message": "Invalid or disposable email address detected", "reason": "Disposable email" } Customization Options Email Template Modify HTML in Gmail node Add company logo Change colors and fonts Access Card Design Edit CSS in HTMLCSSToImage node Adjust QR code size Match your brand Access Code Format Change prefix from "BETA-" to your choice Modify length and characters Trello Integration Add custom fields Include labels Set due dates Assign team members Use Cases Mobile App Beta Launch User fills form → Email verified → Code sent → App activated → Team tracks in Trello SaaS Early Access User signs up → Email validated → Access kit received → Product team manages Game Testing Campaign Player requests access → Email verified → Unique key generated → Community team tracks What Makes This Special Unlike simple email workflows, this is a complete system that handles: Security (email verification) Branding (custom access cards) Communication (professional emails) Tracking (team collaboration) Integration (webhook API) All in one cohesive, production-ready workflow! Troubleshooting Common Issues & Solutions: Webhook not receiving data → Check URL and POST method Email verification fails → Verify API key and rate limits Gmail not sending → Reconnect OAuth2 Trello card fails → Confirm List ID is correct Image not generating → Check HTMLCSSToImage credentials 🏷️ ADDITIONAL METADATA Difficulty Level: ⭐⭐⭐ Intermediate (requires API key setup) Time to Setup: 🕐 10-15 minutes