HumationHuman + Automation
Back to Catalog

Sales prospect research & outreach preparation with Apollo, Linkup AI, and LinkedIn

Guillaume DuvernayGuillaume Duvernay
1086 views
2/3/2026
Lead ManagementJotFormAutomationSalesforceCRM
Official Page

This template transforms your sales and outreach process by automating deep, personalized research on any contact. Go beyond simple data enrichment; this workflow acts as an AI research assistant. Starting with just a name and company, it finds the person's professional profile, analyzes it through the lens of your specific business offering, and returns actionable insights to prepare for the perfect outreach.

Stop spending hours manually researching prospects. With this template, you get a synthesized report in seconds, highlighting a contact's potential pain points and exactly how your solution can provide value, setting the stage for more meaningful and effective conversations.

Who is this for?

  • Sales Development & Business Development Reps (SDRs/BDRs): Drastically cut down on research time and increase the quality and personalization of your outreach efforts.
  • Account Executives: Prepare for meetings with a deep, relevant understanding of a prospect's background and potential needs.
  • Founders & Solopreneurs: Handle your own sales and lead generation efficiently by automating the research phase.
  • Marketing Teams: Power your Account-Based Marketing (ABM) campaigns with tailored insights for key accounts.

What problem does this solve?

  • Eliminates time-consuming manual research: Automates the entire process of finding a person, reading their profile, and connecting the dots back to your business.
  • Prevents generic outreach: Provides you with specific, synthesized talking points, moving you beyond "I saw your profile on LinkedIn" to a message that shows you've done your homework.
  • Solves "writer's block": Delivers a clear summary of a prospect's potential challenges and how you can help, making it much easier to start writing a compelling message.
  • Creates actionable intelligence, not just data: Instead of just returning a list of job titles and skills, it synthesizes that information into strategic summaries ready to be used.

How it works

  1. Input contact details: The workflow is triggered by a form where you enter the first name, last name, and company of the person you want to research.
  2. Find the person with Apollo: The workflow uses the Apollo.io API to find the contact's professional data, including their verified LinkedIn profile URL.
  3. Define your business context: This is the "smart" part. The workflow injects information you provide about your offering and the typical pain points your customers face.
  4. Analyze profile with Linkup: Using the Linkup API, the workflow reads the person's public LinkedIn profile. Crucially, it analyzes the profile through the lens of your business context.
  5. Get synthesized insights: Linkup's AI returns three structured summaries: a general overview of the person, their potential pain points relative to your business, and a concise explanation of how your offering could bring them value.
  6. Consolidate results: The final node gathers all the enriched data and AI-generated summaries into a single, clean output, ready for your CRM or next action.

Setup

  1. Define your business context (Critical Step): This is the most important part. In the Define our business context node, fill in the two fields:
    • Area for which the prospect could experience pain points: Describe the general problems your customers face.
    • My offering: Briefly describe your product or service. This context is what makes the AI analysis relevant to you.
  2. Connect your accounts:
    • Apollo: Add your Apollo API key to the Enrich contact with Apollo HTTP node.
    • Linkup: Add your Linkup API key to the Find Linkedin profile information with Linkup HTTP node. Their free plan offers €5 of credits, enough for ~1,000 runs.
  3. Activate the workflow: Toggle the workflow to "Active". You can now run it by filling out the form trigger!

Taking it further

  • Automate CRM enrichment: Connect the final Consolidate results node to a HubSpot, Attio, or Salesforce node to automatically save these rich insights to your contact records.
  • Generate AI-powered outreach: Add an OpenAI node after this workflow to take the synthesized insights and generate a first draft of a personalized outreach email or LinkedIn message.
  • Process leads in bulk: Replace the Form Trigger with a Google Sheets or Airtable trigger to run this enrichment process for an entire list of new leads automatically.

n8n Form Trigger Workflow

This n8n workflow demonstrates a basic setup for triggering an HTTP request based on a form submission and then transforming the data.

Description

This workflow listens for submissions to an n8n-generated form. Upon receiving a submission, it makes an HTTP request (the specifics of which are not defined in the provided JSON) and then processes the output using a "Set" node to potentially modify or add fields.

What it does

  1. Triggers on Form Submission: The workflow starts when a user submits data through an n8n Form Trigger.
  2. Makes an HTTP Request: It then executes an HTTP Request node. The URL, method, and other details for this request are not configured in the provided JSON, so it acts as a placeholder for an external API call.
  3. Edits/Transforms Fields: Finally, it uses a "Set" node (named "Edit Fields") to manipulate the data received from the previous steps. This node can be configured to add, remove, or modify fields in the workflow's data stream.

Prerequisites/Requirements

  • n8n Instance: You need a running n8n instance to host and execute this workflow.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure the Form Trigger:
    • Open the "On form submission" node.
    • Define the fields you expect in your form.
    • Activate the workflow to generate the public URL for your form.
  3. Configure the HTTP Request:
    • Open the "HTTP Request" node.
    • Specify the URL, Method (e.g., GET, POST), Headers, and Body as required for your external API call. This is currently a blank HTTP Request node.
  4. Configure the Edit Fields (Set) node:
    • Open the "Edit Fields" node.
    • Add or modify the Values to transform your data as needed. For example, you might want to rename fields, combine values, or add static data.
  5. Activate the workflow: Once configured, activate the workflow. You can then submit data to the n8n form to test the end-to-end process.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

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.

Le NguyenBy Le Nguyen
942