Back to Catalog

Generate personalized sales leads with Claude AI & Explorium for Gmail outreach

exploriumexplorium
185 views
2/3/2026
Official Page

Outbound Agent - AI-Powered Lead Generation with Natural Language Prospecting

This n8n workflow transforms natural language queries into targeted B2B prospecting campaigns by combining Explorium's data intelligence with AI-powered research and personalized email generation. Simply describe your ideal customer profile in plain English, and the workflow automatically finds prospects, enriches their data, researches them, and creates personalized email drafts.

DEMO

Template Demo

Credentials Required

To use this workflow, set up the following credentials in your n8n environment:

Anthropic API

  • Type: API Key
  • Used for: AI Agent query interpretation, email research, and email writing
  • Get your API key at Anthropic Console

Explorium API

  • Type: Generic Header Auth
  • Header: Authorization
  • Value: Bearer YOUR_API_KEY
  • Used for: Prospect matching, contact enrichment, professional profiles, and MCP research
  • Get your API key at Explorium Dashboard

Explorium MCP

  • Type: HTTP Header Auth
  • Used for: Real-time company and prospect intelligence research
  • Connect to: https://mcp.explorium.ai/mcp

Gmail

  • Type: OAuth2
  • Used for: Creating email drafts
  • Alternative options: Outlook, Mailchimp, SendGrid, Lemlist

Go to Settings → Credentials, create these credentials, and assign them in the respective nodes before running the workflow.


Workflow Overview

Node 1: When chat message received

This node creates an interactive chat interface where users can describe their prospecting criteria in natural language.

  • Type: Chat Trigger
  • Purpose: Accept natural language queries like "Get 5 marketing leaders at fintech startups who joined in the past year and have valid contact information"
  • Example Prompts:
    • "Find SaaS executives in New York with 50-200 employees"
    • "Get marketing directors at healthcare companies"
    • "Show me VPs at fintech startups with recent funding"

Node 2: Chat or Refinement

This code node manages the conversation flow, handling both initial user queries and validation error feedback.

  • Function: Routes either the original chat input or validation error messages to the AI Agent
  • Dynamic Input: Combines chatInput and errorInput fields
  • Purpose: Creates a feedback loop for validation error correction

Node 3: AI Agent

The core intelligence node that interprets natural language and generates structured API calls.

Functionality:

  • Interprets user intent from natural language queries
  • Maps concepts to Explorium API filters (job levels, departments, company size, revenue, location, etc.)
  • Generates valid JSON requests with precise filter criteria
  • Handles off-topic queries with helpful guidance
  • Connected to MCP Client for real-time filter specifications

AI Components:

  • Anthropic Chat Model: Claude Sonnet 4 for query interpretation
  • Simple Memory: Maintains conversation context (100 message window)
  • Output Parser: Structured JSON output with schema validation
  • MCP Client: Connected to https://mcp.explorium.ai/mcp for Explorium specifications

System Instructions:

  • Expert in converting natural language to Explorium API filters
  • Can revise previous responses based on validation errors
  • Strict adherence to allowed filter values and formats
  • Default settings: mode: "full", size: 10000, page_size: 100, has_email: true

Node 4: API Call Validation

This code node validates the AI-generated API request against Explorium's filter specifications.

Validation Checks:

  • Filter key validity (only allowed filters from approved list)
  • Value format correctness (enums, ranges, country codes)
  • No duplicate values in arrays
  • Proper range structure for experience fields (total_experience_months, current_role_months)
  • Required field presence

Allowed Filters:

  • country_code, region_country_code, company_country_code, company_region_country_code
  • company_size, company_revenue, company_age, number_of_locations
  • google_category, naics_category, linkedin_category, company_name
  • city_region_country, website_keywords
  • has_email, has_phone_number
  • job_level, job_department, job_title
  • business_id, total_experience_months, current_role_months

Output:

  • isValid: Boolean validation status
  • validationErrors: Array of specific error messages

Node 5: Is API Call Valid?

Conditional routing node that determines the next step based on validation results.

  • If Valid: Proceed to Explorium API: Fetch Prospects
  • If Invalid: Route to Validation Prompter for correction

Node 6: Validation Prompter

Generates detailed error feedback for the AI Agent when validation fails. This creates a self-correcting loop where the AI learns from validation errors and regenerates compliant requests by routing back to Node 2 (Chat or Refinement).

Node 7: Explorium API: Fetch Prospects

Makes the validated API call to Explorium's prospect database.

  • Method: POST
  • Endpoint: /v1/prospects/fetch
  • Authentication: Header Auth (Bearer token)
  • Input: JSON with filters, mode, size, page_size, page
  • Returns: Array of matched prospects with prospect IDs based on filter criteria

Node 8: Pull Prospect IDs

Extracts prospect IDs from the fetch response for bulk enrichment.

  • Input: Full fetch response with prospect data
  • Output: Array of prospect_id values formatted for enrichment API

Node 9: Explorium API: Contact Enrichment

Single enrichment node that enhances prospect data with both contact and profile information.

  • Method: POST
  • Endpoint: /v1/prospects/enrich
  • Enrichment Types: contacts, profiles
  • Authentication: Header Auth (Bearer token)
  • Input: Array of prospect IDs from Node 8

Returns:

  • Contacts: Professional emails (current, verified), phone numbers (mobile, work), email validation status, all available email addresses
  • Profiles: Full professional history, current role details, company information, skills and expertise, education background, experience timeline, job titles and seniority levels

Node 10: Clean Output Data

Transforms and structures the enriched data for downstream processing.

Node 11: Loop Over Items

Iterates through each prospect to generate individualized research and emails.

  • Batch Size: 1 (processes prospects one at a time)
  • Purpose: Enable personalized research and email generation for each prospect
  • Loop Control: Processes until all prospects are complete

Node 12: Research Email

AI-powered research agent that investigates each prospect using Explorium MCP.

Input Data:

  • Prospect name, job title, company name, company website
  • LinkedIn URL, job department, skills

Research Focus:

  • Company automation tool usage (n8n, Zapier, Make, HubSpot, Salesforce)
  • Data enrichment practices
  • Tech stack and infrastructure (Snowflake, Segment, etc.)
  • Recent company activity and initiatives
  • Pain points related to B2B data (outdated CRM data, manual enrichment, static workflows)
  • Public content (speaking engagements, blog posts, thought leadership)

AI Components:

  • Anthropic Chat Model1: Claude Sonnet 4 for research
  • Simple Memory1: Maintains research context
  • Explorium MCP1: Connected to https://mcp.explorium.ai/mcp for real-time intelligence

Output: Structured JSON with research findings including automation tools, pain points, personalization notes

Node 13: Email Writer

Generates personalized cold email drafts based on research findings.

Input Data:

  • Contact info from Loop Over Items
  • Current experience and skills
  • Research findings from Research Email agent
  • Company data (name, website)

AI Components:

  • Anthropic Chat Model3: Claude Sonnet 4 for email writing
  • Structured Output Parser: Enforces JSON schema with email, subject, message fields

Output Schema:

  • email: Selected prospect email address (professional preferred)
  • subject: Compelling, personalized subject line
  • message: HTML formatted email body

Node 14: Create a draft (Gmail)

Creates email drafts in Gmail for review before sending.

  • Resource: Draft
  • Subject: From Email Writer output
  • Message: HTML formatted email body
  • Send To: Selected prospect email address
  • Authentication: Gmail OAuth2

After Creation: Loops back to Node 11 (Loop Over Items) to process next prospect

Alternative Output Options:

  • Outlook: Create drafts in Microsoft Outlook
  • Mailchimp: Add to email campaign
  • SendGrid: Queue for sending
  • Lemlist: Add to cold email sequence

Workflow Flow Summary

  1. Input: User describes target prospects in natural language via chat interface
  2. Interpret: AI Agent converts query to structured Explorium API filters using MCP
  3. Validate: API call validation ensures filter compliance
  4. Refine: If invalid, error feedback loop helps AI correct the request
  5. Fetch: Retrieve matching prospect IDs from Explorium database
  6. Enrich: Parallel bulk enrichment of contact details and professional profiles
  7. Clean: Transform and structure enriched data
  8. Loop: Process each prospect individually
  9. Research: AI agent uses Explorium MCP to gather company and prospect intelligence
  10. Write: Generate personalized email based on research
  11. Draft: Create reviewable email drafts in preferred platform

This workflow eliminates manual prospecting work by combining natural language processing, intelligent data enrichment, automated research, and personalized email generation—taking you from "I need marketing leaders at fintech companies" to personalized, research-backed email drafts in minutes.


Customization Options

Flexible Triggers

The chat interface can be replaced with:

  • Scheduled runs for recurring prospecting
  • Webhook triggers from CRM updates
  • Manual execution for ad-hoc campaigns

Scalable Enrichment

Adjust enrichment depth by:

  • Adding more Explorium API endpoints (technographics, funding, news)
  • Configuring prospect batch sizes
  • Customizing data cleaning logic

Output Destinations

Route emails to your preferred platform:

  • Email Platforms: Gmail, Outlook, SendGrid, Mailchimp
  • Sales Tools: Lemlist, Outreach, SalesLoft
  • CRM Integration: Salesforce, HubSpot (create leads with research)
  • Collaboration: Slack notifications, Google Docs reports

AI Model Flexibility

Swap AI providers based on your needs:

  • Default: Anthropic Claude (Sonnet 4)
  • Alternatives: OpenAI GPT-4, Google Gemini

Setup Notes

  1. Domain Filtering: The workflow prioritizes professional emails—customize email selection logic in the Clean Output Data node
  2. MCP Configuration: Explorium MCP requires Header Auth setup—ensure credentials are properly configured
  3. Rate Limits: Adjust Loop Over Items batch size if hitting API rate limits
  4. Memory Context: Simple Memory maintains conversation history—increase window length for longer sessions
  5. Validation: The AI self-corrects through validation loops—monitor early runs to ensure filter accuracy

This workflow represents a complete AI-powered sales development representative (SDR) that handles prospecting, research, and personalized outreach with minimal human intervention.

Generate Personalized Sales Leads with Claude AI & Explorium for Gmail Outreach

This n8n workflow leverages the power of AI to generate personalized sales leads and draft tailored email outreach messages for Gmail. By integrating with Claude AI and utilizing a custom Model Context Protocol (MCP) client, it automates the process of identifying potential leads and crafting compelling initial contact emails.

What it does

This workflow orchestrates a series of steps to automate personalized sales outreach:

  1. Receives a Chat Message: The workflow is triggered by an incoming chat message, likely containing initial lead generation criteria or a prompt to start the process.
  2. Initial Logic Check: An 'If' node evaluates a condition, potentially to determine if the chat message meets specific requirements for lead generation.
  3. Loops Over Items: If the condition is met, the workflow enters a loop, processing items in batches. This suggests it can handle multiple lead generation requests or data points.
  4. Processes with AI Agent: For each item, an 'AI Agent' (powered by LangChain) is invoked. This agent is likely responsible for understanding the request, gathering information, and formulating a strategy for lead generation and email drafting.
  5. Utilizes Anthropic Chat Model: The AI Agent uses the 'Anthropic Chat Model' (Claude AI) as its language model to generate human-like text, such as lead profiles or email content.
  6. Leverages Simple Memory: A 'Simple Memory' component is used by the AI Agent to maintain context during the conversation or processing, ensuring coherent and relevant outputs.
  7. Structures Output: A 'Structured Output Parser' ensures that the AI's output is formatted in a consistent and usable way, likely as JSON, for further processing.
  8. Executes Custom Code: A 'Code' node allows for custom JavaScript execution, which could be used to refine lead data, manipulate email content, or integrate with other services.
  9. Interacts with MCP Client Tool: The workflow uses an 'MCP Client Tool', indicating an integration with a "Model Context Protocol" service, likely for enriching lead data or accessing specific sales intelligence.
  10. Sends Personalized Emails via Gmail: Finally, the workflow uses the 'Gmail' node to send out the personalized email outreach messages to the identified leads.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Anthropic API Key: For the 'Anthropic Chat Model' (Claude AI).
  • Gmail Account: Configured as a credential in n8n for sending emails.
  • MCP Client Configuration: Access and credentials for the Model Context Protocol (MCP) client service, if external.
  • LangChain Credentials: Potentially, specific credentials for LangChain services if not self-hosted within n8n.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Anthropic API Key credential for the 'Anthropic Chat Model' node.
    • Configure your Gmail OAuth or API key credential for the 'Gmail' node.
    • Ensure any necessary credentials for the MCP Client Tool are properly set up.
  3. Review and Customize:
    • Examine the 'Chat Trigger' node to understand how it receives input and adjust as needed.
    • Review the 'If' node's conditions and modify them to fit your lead generation criteria.
    • Inspect the 'AI Agent' and 'Anthropic Chat Model' configurations to fine-tune the AI's behavior and prompt engineering for optimal lead generation and email drafting.
    • Adjust the 'Code' node if custom data manipulation or integration logic is required.
    • Verify the 'Gmail' node's settings, including recipient fields, subject lines, and email body, ensuring they correctly use the AI-generated personalized content.
  4. Activate the Workflow: Once configured, activate the workflow to start generating personalized sales leads and sending outreach emails 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.

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