Workflow Templates

Tagged with: LangChain - Example

No description available

Tagged with: LangChain - Example

No description available

Tagged with: , , , ,

Create Products in Shopify from Airtable This workflow creates products in your Shopify store from Airtable. It also enables inventory tracking and sets the quantity of an inventory item at your store's default location. This is a great way to keep shopify in sync with Airtable if Airtable is your primary source of data, Only records with the 'sync' column set to true are sync'd. Setup Airtable Automations so that if any records are created or updated then this flag is set to true. Records are matched using the 'slug' column which Shopify calls a handle. Airtable Setup Notes The Airtable products table has the following columns title - free text description - free text company - free text type - free text status - ACTIVE, DRAFT or ARCHIVE slug - used in the product url, text with no spaces, can also use hyphen. price - sale price of the products compare_at_price - compare at price for products sku - unique code for each product stock_on_hand - quantity of this item available for purchase. sync - boolean, set to true to sync this record. Update GraphQL nodes with your Shopify store URL 1) Replace the URL in all GraphQL nodes with the URL for your Shopify store. 2) All GraphQL requests all use the Shopify 2025-04 GraphQL Admin API.

No description available

This workflow triggers when a new opportunity is created in Go High Level (GHL), fetches the associated contact details, and initiates an outbound call using Vapi. The call is made by a Vapi assistant configured with the appropriate credentials. 🧾 Requirements Go High Level (GHL) A Go High Level account GHL developer private app and credentials enabled in n8n Webhook URL** from n8n added to your GHL private app Vapi A Vapi account with credit A connected phone number to make calls An assistant created and ready to make calls Your Vapi API key 🔗 Useful Links GHL Docs Vapi Docs n8n GHL Credentials Setup 🔄 Workflow Breakdown 1. Trigger: GHL Opportunity Created Triggered by a Webhook (POST) from Go High Level when a new opportunity is created. Webhook URL must be enabled in your GHL private app. 2. Get a GHL Contact Retrieves contact details from GHL CRM using the contact ID from the opportunity. Includes information such as phone number, name, and custom fields. 3. Wait 5 Minutes Introduces a short delay before making the call to avoid immediate outreach. Helps ensure data is synced and gives the system time for any follow-up automation. 4. Set Vapi Fields (Manual Step) Set the required fields for the Vapi API call: vapiPhoneNumberId – the number id making the call vapiAssistantId – the assistant who will handle the call vapiApi – your secure Vapi API key 5. Start Outbound Vapi Call Sends a POST request to https://api.vapi.ai/call Payload includes: Contact’s phone number Selected Vapi assistant Vapi phone number id to start the call ✅ Summary This n8n automation connects your CRM (Go High Level) with voice automation (Vapi) to immediately respond to new opportunities. Once a lead is created, they will receive a personalized voice call from a Vapi AI assistant. 🙋‍♂️ Need Help? Feel free to contact us at 1 Node Get instant access to a library of free resources we created.

Who’s it for This workflow is designed for organizations or services managing appointments, such as interview scheduling, class enrollments, or client meetings. It’s ideal for users who want to automate appointment creation, rescheduling, cancellation, and data retrieval from a single webhook endpoint. How it works / What it does ● Receives incoming appointment requests via a Webhook node. ● Processes requests in the Set Fields node, handling multiple actions: • Set Appointment: Adds a new appointment and assigns an available interviewer. • Reschedule: Changes the appointment date based on availability. • Cancel: Deletes an appointment and frees the interviewer’s slot. • Get List: Returns a user’s list of classes. • Get User Info: Retrieves detailed information about a specific user. All actions follow strict instructions to check tables, update rows, and return structured JSON responses. How to set up Add the Webhook node and set the HTTP method to POST. Connect it to the Set Fields node. Configure the Set Fields node with the desired assignments (set_appointment, reschedule, cancel, get_list, get_user_info). Ensure your database tables (interviewers, enrollers) are properly configured and accessible. Requirements • n8n environment • Database or table access for interviewers and enrollers • Properly formatted incoming JSON requests with necessary fields (e.g., name, nationality number, preferred date). How to customize the workflow • Add or modify assignment actions to handle additional appointment scenarios. • Adjust table names or database connections based on your environment. • Extend JSON responses for custom client-side handling.

Discover relevant contacts from target accounts using Octave intelligent prospecting Who is this for? Sales development teams, account-based marketing professionals, and RevOps teams who are tired of generic job title filtering that misses the real decision makers. Built for teams that need to find the right people based on actual responsibilities and business context, not just titles on LinkedIn. What problem does this solve? Most prospecting tools are flying blind when it comes to finding the right contacts. You search for "VP of Engineering" but miss the "Head of Platform" who actually owns your use case. You filter by "Marketing Director" but the "Growth Lead" is the real buyer. Traditional prospecting relies on job title matching, but titles vary wildly across companies. This workflow uses Octave's context engine to find contacts based on who actually does the work your solution impacts, regardless of their specific job title. What this workflow does Target Account Processing: Reads target account lists from Airtable (or other data sources) Processes company domains for intelligent contact discovery Handles batch processing for multiple target accounts Context-Aware Contact Discovery: Uses Octave's prospector agent to find relevant stakeholders within target organizations Leverages your defined personas to identify the right people based on responsibilities, not just titles Analyzes organizational structure, role responsibilities, and KPIs to match contacts to your solution Discovers decision makers and influencers who might be missed by traditional job title searches Structured Contact Output: Returns discovered contacts with complete profile information Includes LinkedIn profiles, contact details, and role context Organizes contacts by relevance and decision-making authority Exports contact lists back to Airtable for sales team action Setup Required Credentials: Octave API key and workspace access Airtable API credentials (or your preferred contact management platform) Access to your target account list Step-by-Step Configuration: Set up Target Account Source: Add your Airtable credentials to n8n Replace your-airtable-base-id and your-accounts-table-id with your actual account list Ensure your account list includes company domains for prospecting Configure trigger method (manual, scheduled, or webhook-based) Configure Octave Prospector Agent: Add your Octave API credentials in n8n Replace your-octave-prospector-agent-id with your actual prospector agent ID Configure your prospector with relevant personas and role definitions Test prospecting with sample companies to verify contact quality Set up Contact Output Destination: Replace your-contacts-table-id with your target contact list table Configure field mapping between Octave output and your contact database Set up data validation and deduplication rules Test contact creation and data formatting Customize Contact Selection: Configure which personas to prioritize in your prospector agent Set relevance thresholds for contact discovery Define organizational levels to target (individual contributors vs. management) Adjust contact volume per account based on your outreach capacity Required Account List Format: Your Airtable (or data source) should include: Company Name Company Domain (required for prospecting) Account status/priority (optional) Target personas (optional) How to customize Prospector Configuration: Customize contact discovery in your Octave prospector agent: Persona Targeting:** Define which of your Library personas to prioritize when prospecting Role Responsibilities:** Configure the specific responsibilities and KPIs that indicate a good fit Organizational Level:** Target specific levels (IC, manager, director, VP, C-level) based on your solution Company Size Adaptation:** Adjust prospecting approach based on organization size and structure Contact Selection Criteria: Refine who gets discovered: Decision-Making Authority:** Prioritize contacts with budget authority or implementation influence Problem Ownership:** Focus on roles that directly experience the pain points your solution solves Technical Influence:** Target contacts who influence technical decisions if relevant to your offering Process Ownership:** Identify people who own the processes your solution improves Data Integration: Adapt for different contact management systems: Replace Airtable with your CRM, database, or spreadsheet system Modify field mapping to match your contact database schema Add data enrichment steps for additional contact information Integrate with email platforms for immediate outreach Batch Processing: Configure for scale: Adjust processing volume based on API limits and prospecting quotas Add scheduling for regular account list updates Implement error handling for accounts that can't be prospected Set up monitoring for prospecting success rates Use Cases Account-based marketing contact list generation Sales territory planning and contact mapping Competitive displacement campaign targeting Product expansion within existing customer accounts Event-based prospecting for specific personas Market research and competitive intelligence gathering

🚀 The Ultimate AI Sales Outbound Engine Stop wasting hours on manual dialing and listening to ringtones. This workflow transforms your *Airtable* into a high-velocity *AI Call Center* using *Vapi AI*. ⚡ TL;DR Automate lead qualification calls, handle voicemails like a pro, and sync every transcript back to your CRM without lifting a finger. 🧠 How it Works The Scout: Every minute, n8n scans your Airtable for leads marked TBC. The Dialer: It triggers a personalized Vapi AI call, passing along the lead’s name and context. The Reporter: Once the call ends, a Webhook catches the data, including the recording, transcript, and AI summary. The Strategist: * Success? Updates the lead to Called and logs the summary. Voicemail?* Automatically triggers a *double-dial** retry after 1 minute. Still nothing?* Schedules a final follow-up for the next day at the *optimal time (your time)**. 🛠️ Setup Guide Airtable:** Create a "Leads" table with fields for Status, Mobile, Attempt, and Summary. Vapi:** Plug in your Assistant ID and set the Webhook URL to this workflow's address. n8n:* Use the *Header Auth** credential for your Vapi API key to keep things secure. 💎 Why This Wins Aggressive Retries:** Includes a built-in "Double-Dial" strategy to increase connection rates. Clean CRM:** No more messy notes; get structured AI summaries for every call. Plug-and-Play:** Designed to be easily customized for any industry—from real estate to SaaS.

How it works This workflow automates the transfer of files from an FTP server to Google Drive. It runs on a schedule, lists files in a defined FTP directory, and processes them in batches. Each file is downloaded sequentially from the FTP server and uploaded to Google Drive. The workflow ensures filenames are preserved for consistency during the sync process. Step-by-step 1. Trigger the workflow Schedule Trigger** – Starts the workflow automatically at set intervals. 2. List files from FTP FTP (List Files)** – Retrieves a list of files from the FTP server path. 3. Batch process files Split in Batches** – Breaks the file list into smaller chunks for sequential handling. 4. Download file from FTP FTP (Download File)** – Downloads each file from the FTP server. 5. Upload to Google Drive Google Drive (Upload File)** – Uploads the file to Google Drive while keeping its original filename. Why use this? Automates repetitive FTP-to-cloud transfer tasks with no manual intervention. Reduces system overload by processing files in manageable batches. Ensures data backup from FTP servers directly into cloud storage. Maintains file structure and filenames for easy reference and retrieval. Provides reliable, scheduled synchronization between FTP and Google Drive.