Typeform lead capture to HubSpot with scoring and Slack alerts
π Smart Lead Capture, Scoring & Slack Alerts
This workflow captures new leads from Typeform, checks for duplicates in HubSpot CRM, enriches and scores them, assigns priority tiers (Cold, Warm, Hot), and instantly notifies your sales team in Slack.
π§ How It Works
Typeform Trigger β Monitors form submissions and passes lead details into the workflow.
HubSpot Deduplication β Searches HubSpot by email before creating a new record.
Conditional Routing β
If no match β Creates a new contact in HubSpot.
If match found β Updates the existing contact with fresh data.
Lead Scoring (Function Node) β Custom JavaScript assigns a score based on your rules (e.g. company email, job title, engagement signals, enrichment data).
Tier Assignment β Categorizes the lead as βοΈ Cold, π‘ Warm, or π₯ Hot based on score thresholds.
Slack Notification β Sends formatted lead alerts to a dedicated sales channel with priority indicators.
π€ Who Is This For?
- Sales teams who need to prioritize hot leads in real-time.
Marketing teams running inbound lead capture campaigns with Typeform.
RevOps teams that want custom scoring beyond HubSpot defaults.
Founders/SMBs looking to tighten lead-to-revenue pipeline with automation.
π‘ Use Case / Problem Solved
β Duplicate contacts clogging HubSpot CRM.
β Manual lead triage slows down response time.
β HubSpotβs default scoring is rigid.
β Automates lead creation + scoring + notification in one flow.
β Sales teams get immediate Slack alerts with context to act fast.
βοΈ What This Workflow Does
Captures lead data directly from Typeform.
Cleans & deduplicates contacts before pushing to HubSpot CRM.
Scores and categorizes leads via custom logic.
Sends structured lead alerts to Slack, tagged by priority.
Provides a scalable foundation you can extend with data enrichment (e.g., Clearbit, Apollo).
π οΈ Setup Instructions
π Prerequisites
Typeform account with API access β Typeform Developer Docs
HubSpot CRM account with API key or OAuth β HubSpot API Docs
Slack workspace & API access β Slack API Docs
(Optional) n8n automation platform to build & run β n8n Hub
π Steps to Configure
Typeform Node (Trigger)
- Connect your Typeform account in n8n.
- Select the form to track submissions.
- Fields typically include: first name, last name, email, company, phone.
HubSpot Node (Search Contact) Configure a search by email. Route outcomes:
- Not Found β Create Contact
- Found β Update Contact
HubSpot Node (Create/Update Contact)
- Map Typeform fields into HubSpot (email, name, phone, company).
Ensure you capture both standard and custom properties.
Function Node (Lead Scoring) Example JavaScript:
// Simple lead scoring example const email = $json.email || ""; let score = 0;
if (email.endsWith("@company.com")) score += 30; if ($json.company && $json.company.length > 2) score += 20; if ($json.phone) score += 10;
let tier = "βοΈ Cold"; if (score >= 60) tier = "π₯ Hot"; else if (score >= 30) tier = "π‘ Warm";
return { ...$json, leadScore: score, leadTier: tier };
Customize rules based on your GTM strategy.
Reference β n8n Function Node Docs
Slack Node (Send Message) Example Slack message template:
π New Lead Alert!
π€ {{ $json.firstname }} {{ $json.lastname }}
π§ {{ $json.email }} | π’ {{ $json.company }}
π Score: {{ $json.leadScore }} β {{ $json.leadTier }}
Send to dedicated #sales-leads channel.
Reference β Slack Node in n8n
π Notes & Extensions
π Add enrichment with Clearbit or Apollo.io before scoring.
π Use HubSpot workflows to trigger nurturing campaigns for βοΈ Cold leads.
β± For π₯ Hot leads, auto-assign to an SDR using HubSpot deal automation.
π§© Export data to Google Sheets or Airtable for analytics.
Typeform Lead Capture to HubSpot with Scoring and Slack Alerts
This n8n workflow automates the process of capturing leads from Typeform, scoring them based on predefined criteria, creating or updating contacts in HubSpot, and sending real-time notifications to Slack for high-scoring leads.
What it does
- Listens for new Typeform submissions: The workflow is triggered every time a new response is submitted to a configured Typeform.
- Processes Typeform data: It extracts relevant information from the Typeform submission.
- Scores the lead: A custom JavaScript code node evaluates the lead based on specific criteria (e.g., answers to certain questions) and assigns a score.
- Creates/Updates HubSpot Contact: The lead information, including the calculated score, is used to create a new contact or update an existing one in HubSpot.
- Filters high-scoring leads: An 'If' node checks if the lead's score exceeds a certain threshold.
- Sends Slack Alert (for high-scoring leads): If the lead's score is high, a notification containing lead details is sent to a specified Slack channel, alerting the sales or marketing team.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Typeform Account: A Typeform account with a form configured to capture lead information.
- HubSpot Account: A HubSpot account with API access.
- Slack Account: A Slack workspace with an incoming webhook or bot token for sending messages.
Setup/Usage
- Import the workflow: Download the provided JSON and import it into your n8n instance.
- Configure Typeform Trigger:
- Select your Typeform credential or create a new one.
- Choose the specific Typeform you want to monitor for new submissions.
- Configure Code Node (Lead Scoring):
- Open the "Code" node.
- Review and modify the JavaScript code to define your lead scoring logic based on your Typeform questions and desired criteria.
- Configure HubSpot Node:
- Select your HubSpot credential or create a new one.
- Map the data from the Typeform submission and the calculated score to the appropriate HubSpot contact properties.
- Ensure the operation is set to "Create or Update" to handle both new and existing leads.
- Configure If Node (Score Threshold):
- Adjust the condition in the "If" node to set the threshold for what constitutes a "high-scoring" lead (e.g.,
{{ $json.score > 70 }}).
- Adjust the condition in the "If" node to set the threshold for what constitutes a "high-scoring" lead (e.g.,
- Configure Slack Node:
- Select your Slack credential or create a new one (using a Bot Token is recommended for more control).
- Specify the Slack channel where alerts should be sent.
- Customize the message content to include relevant lead details and their score.
- Activate the workflow: Once all nodes are configured, activate the workflow to start capturing and processing leads automatically.
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 invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive β Download PDF β OCR text β AI normalize to JSON β Upsert Buyer (Account) β Create Opportunity β Map Products β Create OLI via Composite API β Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content β the parsed JSON (ensure itβs an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id β build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total β per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger β Download File From Google Download File From Google β Extract from File β Update File to One Drive Extract from File β Message a model Message a model β Create or update an account Create or update an account β Create an opportunity Create an opportunity β Build SOQL Build SOQL β Query PricebookEntries Query PricebookEntries β Code in JavaScript Code in JavaScript β Create Opportunity Line Items --- Quick setup checklist π Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. π IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) π§ AI Prompt: Use the strict system prompt; jsonOutput = true. π§Ύ Field mappings: Buyer tax id/name β Account upsert fields Invoice code/date/amount β Opportunity fields Product name must equal your Product2.ProductCode in SF. β Test: Drop a sample PDF β verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep βReturn only a JSON arrayβ as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields donβt support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your orgβs domain or use the Salesforce nodeβs Bulk Upsert for simplicity.