Workflow Templates

📩 This n8n automation sends a personalized email to the person who booked a meeting via Calendly. It uses an AI agent to craft a helpful, human-sounding HTML email that includes your fake phone number (111-111-1111) and the meeting date. 📌 What This Workflow Does Triggers when someone books a meeting in Calendly (invitee.created event). Extracts user details like name, email, reason for meeting, and scheduled time. Uses OpenAI to generate a custom email response based on what the user shared. Sends the email to the user using Microsoft Outlook. ⚙️ Step-by-Step Setup Instructions 1. 🔗 Calendly API Setup Go to Credentials → Add Credential → Calendly API in n8n. Authenticate with your Calendly personal access token. Set your Calendly Trigger node to listen for invitee.created events. 2. 📧 Microsoft Outlook Setup Add credentials via Microsoft Outlook OAuth2 in n8n. Select the credential in the "Send a message" node. This node will send an HTML-formatted response to the user's email. 3. 🤖 OpenAI AI Agent Add your OpenAI key under Credentials → OpenAI API. The AI Agent prompt is already pre-configured to: Generate an HTML email Mention how you can help Include the user's question, meeting date, and your placeholder phone number (111-111-1111) 🧠 Node Breakdown | Node | Purpose | |------------------|----------------------------------------------------------| | Calendly Event | Trigger when someone books via Calendly | | Edit Fields | Extracts key details (name, email, question, start time) | | AI Agent | Writes a custom follow-up email using GPT | | Outlook Message | Sends the AI-generated HTML email to the user | 💌 Example Email Output (HTML) Thanks for Booking with Us! Hi Robert Breen, Thanks for booking a meeting with us! You mentioned: need help with n8n. We’d love to help you solve that. During our call, we’ll walk through your issue and explore automation strategies tailored to your setup. Your meeting is scheduled for August 11, 2025 at 3:00 PM EST. In the meantime, if you have questions, feel free to call us at 111-111-1111. Looking forward to chatting soon! 📞 Contact Information Robert , Ynteractive Website: https://ynteractive.com Email: robert@ynteractive.com LinkedIn: https://linkedin.com/in/robert-breen Top-rated n8n Expert & AI Automation Consultant

This n8n template from Intuz provides a complete and automated solution for deep-dive lead research and hyper-personalized email generation. It transforms a basic list of LinkedIn profiles into a campaign-ready database by first enriching contacts with detailed career data and then using AI to craft unique, context-aware emails based on each individual's professional journey. Who's this workflow for? Sales Development Representatives (SDRs) Account Executives (AEs) B2B Marketers & Growth Hackers Recruiters & Talent Acquisition Specialists Startup Founders How it works 1. Scheduled Data Fetch: The workflow runs automatically on a schedule, fetching a list of leads (containing LinkedIn URLs) from a Google Sheet. 2. Enrich Profiles with Apify: For each lead that hasn't been processed, it uses an Apify actor to scrape their LinkedIn profile, extracting key information like their "About" section and detailed work experience. 3. Update Central Database: The scraped career history is saved back into a "Profile Data" column in the original Google Sheet, creating a rich, centralized lead profile. 4. AI Email Personalization: The workflow sends the complete, enriched profile data to a Google Gemini AI model via LangChain, using a sophisticated prompt that instructs it to act as an expert B2B copywriter. 5. Craft a Unique Hook: The AI analyzes the lead's entire career journey to find unique "nuggets"—like long tenure, specific achievements, or unusual career paths—and uses them to write a compelling opening line. 6. Save the Final Email Draft: The AI-generated subject line and personalized email body are saved back into the Google Sheet, leaving you with a ready-to-send, hyper-personalized outreach campaign. Setup Instructions 1. Google Sheets Setup: Connect your Google Sheets account to n8n. In all three Google Sheets nodes, select your credentials and update the Document ID and Sheet Name to match your lead list. Populate your sheet with initial lead data, including at least their LinkedIn URL. 2. Apify Connection: Connect your Apify account in the Runs Profile Extraction Actor node. 3. Google Gemini AI Connection: Connect your Google Gemini (PaLM) API account in the Google Gemini Chat Model node. 4. Configure the Schedule: In the Schedule Trigger node, set the interval for how often you want the workflow to run and process new leads. 5. Activate Workflow: Save the workflow and toggle the "Active" switch to ON. Your automated research and personalization engine is now active. Key Requirements to Use This Template n8n Instance: An active n8n account (Cloud or self-hosted). Google Account & Sheet: A pre-made Google Sheet with columns for First Name, Last Name, LinkedIn, Profile Data, Subject, and Email Body. Apify Account: An active Apify account with a plan that supports the LinkedIn Profile Scraper actor. Google Gemini AI Account: A Google Cloud account with the Vertex AI API (for Gemini models) enabled and an associated API Key. Connect with us Website: https://www.intuz.com/services Email: getstarted@intuz.com LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Worflow Automation Click here- Get Started

Generates a wordlist of 1,000–15,000 subdomains created by an AI agent by correlating detected technologies and recurring patterns. Objective Assist security researchers, bug bounty hunters, and web pentesters in the reconnaissance phase by incorporating an AI agent that generates additional potential subdomains. This enables discovery of assets outside the scope of traditional scans and expands the analyzable attack surface. How it works The user uploads a list of domains to scan (scope). The workflow performs a passive, comprehensive scan using four sources (subfinder, assetfinder, crt.sh, Wayback Machine). The scan results and detected technologies are passed to an AI agent. The agent runs in a loop up to 20 iterations, generating new subdomains each pass (average output depends on input and model). Generated subdomains are validated and deduplicated. Syntax is checked and availability is tested (host active / httpx). Requirements SSH access with a root user and the following tools: Subfinder Assetfinder HTTPX It is recommended to use a VPS with SSH because if the scope is very large the workflow will take a long time.

What this template does Batch-evaluates compliance controls from Google Sheets using the CyberPulse Compliance API. Each control is scored, mapped to selected frameworks, enriched with crosswalk mappings, and summarized with AI-generated findings and recommendations. How it works Read from Sheets → Build control text (response_text + implementation_notes) → CyberPulse Compliance (scoring, mapping, AI summary) → Normalize → Append results to Sheets. Setup (5–10 min) Add Google Sheets + CyberPulse HTTP Header Auth credentials. Replace YOUR_SHEET_ID and sheet names. Provide your Crosswalk JSON URL (raw GitHub or API endpoint) or use this url: https://www.cyberpulsesolutions.com/xw.json Select frameworks to evaluate against. Run a small test, then full batch. CyberPulse API (required for production) Use hosted scoring/mapping (no local ML code). Create a CyberPulse HTTP Header Auth credential with API Key. In the node: paste Crosswalk URL, select frameworks, set credential. For large sheets, add a short Wait or reduce batch size. Input columns control_id control_description response_text implementation_notes evidence_url_1 … evidence_url_4 Output columns status evaluation score confidence rationale categories evidence_count mapped_count mapping_flat frameworks_selected engine_version ai_summary ai_findings (3 per control) ai_recommendations (3 per control) Troubleshooting No rows → check sheet ID and range. Empty mappings → verify Crosswalk URL. Write errors → confirm results sheet + permissions. Learn more about CyberPulse Compliance Agent: https://www.cyberpulsesolutions.com/solutions/compliance-agent Start free: https://www.cyberpulsesolutions.com/pricing Email: info@cyberpulsesolutions.com

Sync QuickBooks Chart of Accounts to Google BigQuery Keep a historical, structured copy of your QuickBooks Chart of Accounts in BigQuery. This n8n workflow runs weekly, syncing new or updated accounts for better reporting and long-term tracking. Who Is This For? Data Analysts & BI Developers** Build a robust financial model and analyze changes over time. Financial Analysts & Accountants** Track structural changes in your Chart of Accounts historically. Business Owners** Maintain a permanent archive of your financial structure for future reference. What the Workflow Does Extract** Every Monday, fetch accounts created or updated in the past 7 days from QuickBooks. Transform** Clean the API response, manage currencies, create stable IDs, and format the data. Format** Convert cleaned data into an SQL insert-ready structure. Load** Insert or update account records into BigQuery. Setup Steps 1. Prepare BigQuery Create a table (e.g., quickbooks.accounts) with columns matching the final SQL insert step. 2. Add Credentials Connect QuickBooks Online and BigQuery credentials in n8n. 3. Configure the HTTP Node Open 1. Get Updated Accounts from QuickBooks. Replace the Company ID {COMPANY_ID} with your real Company ID. Press Ctrl + Alt + ? in QuickBooks to find it. 4. Configure the BigQuery Node Open 4. Load Accounts to BigQuery. Select the correct project. Make sure your dataset and table name are correctly referenced in the SQL. 5. Activate Save and activate the workflow. It will now run every week. Requirements QuickBooks Online account QuickBooks Company ID Google Cloud project with BigQuery and a matching table Customization Options Change Sync Frequency** Adjust the schedule node to run daily, weekly, etc. Initial Backfill** Temporarily update the API query to select * from Account for a full pull. Add Fields** Modify 2. Structure Account Data to include or transform fields as needed.

Description  Automatically assigns new tasks from an Excel/Google Sheets source to the best-fit employee based on expertise, then creates issues in Jira. Gain fast, consistent routing that reduces manual triage and speeds delivery. 🧠📊➡️🗂️ What This Template Does  Fetches new task rows and related areas from Google Sheets/Excel. Analyzes each item with an AI Agent using Azure OpenAI. Selects the best-fit employee by matching the area to expertise stored in the sheet. Returns structured outputs (task, assignee, expertise, ID, bug/task) and creates the Jira issue. Applies rule-based handling for bugs vs tasks via a Switch node. Key Benefits  ⏱ Save time by automating task assignment from new entries. 🎯 Improve accuracy with expertise-based matching. 📋 Keep clean, structured outputs for downstream systems. 🔁 Seamless handoff from Sheets to Jira with no manual steps. Features  Google Sheets Trigger: Reads new task name and related area from the sheet. AI Agent (Azure OpenAI): Evaluates expertise fit and decides the best assignee. Structured Output Parser: Returns exactly five fields: task_name, assignee_name, expertise, employee_id, item_type (bug/task). Jira Create Issue: Creates issues in Jira using selected assignee and item type. Switch (Rules): Routes logic for bugs vs tasks for consistent categorization. Requirements  n8n instance: Cloud or self-hosted. Google Sheets access: Sheet containing employee roster with columns for Name, Expertise, and ID; connect credentials in n8n. Azure OpenAI (GPT-4o-mini): Configure the Azure OpenAI Chat Model credentials for the AI Agent. Jira credentials: Authorized account with permissions to create issues. Output Parser setup: Structured Output Parser configured to the five-field schema: task_name, assignee_name, expertise, employee_id, item_type. Target Audience  🧩 IT Support and Ops teams routing incoming work. 🧭 Project managers orchestrating assignments at scale. 🛠 Engineering managers seeking consistent triage. 📈 Business operations teams automating intake to delivery. Step-by-Step Setup Instructions  Connect Google Sheets credentials and map the task and area fields; ensure roster columns (Name, Expertise, ID) are present. Add Jira credentials and set the Create Issue node to your target project and issue type. Configure Azure OpenAI (GPT-4o-mini) for the AI Agent and provide credentials. Import the workflow, assign all credentials, and align the Structured Output Parser to the five-field schema. Run a test with sample rows; confirm assignee selection and Jira issue creation; then enable scheduling. Security Best Practices  Use least-privilege API tokens for Google Sheets and Jira. Restrict sheet access to only required users and service accounts. Validate and sanitize incoming task data before issue creation. Store credentials securely in n8n and rotate them regularly. Log only necessary fields; avoid sensitive data in workflow logs.

Description This workflow automatically monitors and tracks SEC Form D filings (private placement offerings) by fetching data from the SEC EDGAR database every 10 minutes during business hours and saving new filings to Google Sheets for analysis and tracking. Who's it for Venture capitalists** tracking private funding rounds and market activity Investment analysts** researching private placement trends and opportunities Financial researchers** collecting data on private securities offerings Business development teams** identifying potential partnership or acquisition targets Compliance professionals** monitoring regulatory filings in their industry How it works The workflow connects to the SEC EDGAR RSS feed to fetch the latest Form D filings, parses the XML data, extracts key information including CIK numbers and filing links, filters out duplicates from previous runs, and automatically saves new filings to a Google Sheets document for easy analysis and tracking. What it does Automated scheduling - Runs every 10 minutes during business hours (6 AM - 9 PM, Monday-Friday) Fetches SEC data - Retrieves the 40 most recent Form D filings from SEC EDGAR RSS feed Parses filing data - Converts XML to structured data and extracts CIK numbers, titles, and links Filters duplicates - Only processes new filings that haven't been seen in previous executions Saves to sheets - Appends new filing data to Google Sheets with proper formatting Requirements Google Sheets API access** with OAuth2 credentials configured Google Sheets document** - Make a copy of this template sheet n8n instance** running continuously for scheduled execution How to set up Copy the template Google Sheet from the link above to your Google Drive Configure Google Sheets OAuth2 authentication in n8n credentials Update the Google Sheets document ID in the "Save to SEC Data Sheet" node to point to your copied sheet Customize the User-Agent header in the HTTP Request node with your contact information (required by SEC) Activate the workflow - The schedule trigger will start monitoring automatically Test manually by replacing the Schedule Trigger with a Manual Trigger for initial testing How to customize the workflow Schedule frequency**: Modify the cron expression in the Schedule Trigger (default: every 10 minutes) Business hours**: Adjust the time range (default: 6 AM - 9 PM EST) Working days**: Change from Monday-Friday to include weekends if needed Filing count**: Modify the SEC URL to fetch more than 40 filings (change count=40 parameter) Form types**: Update the URL to track different SEC forms (change type=D to other form types) Output format**: Customize the Google Sheets column mapping to include additional fields Notifications**: Add Slack, email, or webhook nodes to get alerts for new filings Output data includes CIK Number** - Central Index Key for the filing company Company Title** - Name of the company making the filing Form Type** - Type of SEC form (Form D for private placements) HTML Filing Link** - Link to view the filing in SEC EDGAR system TXT Filing Link** - Direct link to the raw text version of the filing Updated Date** - When the filing was submitted to SEC Key features Duplicate prevention** - Built-in deduplication ensures no filing is processed twice Business hours scheduling** - Respects SEC server load by running only during business hours SEC compliance** - Includes proper User-Agent header as required by SEC guidelines Automatic link generation** - Creates both HTML and TXT links for easy access to filings CIK extraction** - Automatically extracts company CIK numbers from filing titles Note: This workflow is designed for monitoring public SEC filings and complies with SEC EDGAR access guidelines. The User-Agent header must be updated with your contact information before use.

Description This n8n workflow automates the process of retrieving images from a specific Google Drive folder, resizing them, and inserting them into a Google Docs document. It ensures images are processed in numeric order, automatically resized to fit the document, and uploaded in batches to prevent timeouts. This template is designed for content creators, documentation teams, and businesses who need to automatically insert images (e.g., product photos, reports, or scanned documents) into Google Docs with minimal manual effort. How it works Retrieves image files from a Google Drive folder. Filters and sorts files based on numeric order in the filename. Generates direct image URIs and resizes them automatically (width & height). Inserts the resized images into the target Google Docs document via API. Uses a batch loop to avoid timeouts and ensure all images are uploaded successfully. Requirements / Pre-conditions An n8n instance (self-hosted or cloud). Connected Google Drive credential in n8n. Connected Google Docs credential in n8n. A target Google Drive folder containing supported image files. A Google Docs document ready to receive the images. Supported formats: PNG, JPG, JPEG, GIF, WEBP. Error handling: If a file is not an image or exceeds Google Docs API limits, the workflow will skip it and continue processing the rest. Setup Steps Google Drive Credential Connect your Google Drive account in n8n to grant access to the folder containing the images. Google Docs Credential Connect your Google Docs account to allow image insertion into the document. Folder & File Filter In the Search File node, replace the placeholder {{YOUR_FOLDER_ID}} with your Google Drive folder ID. Google Docs Document ID In the Insert Image (HTTP Request) node, replace {{YOUR_DOCUMENT_ID}} with your target Google Docs document ID. (Make sure you rename this node to something descriptive, e.g., Insert Image to Google Doc.) Batch Loop The workflow includes a batch processing loop to prevent timeout errors when dealing with large sets of images. You can adjust the batch size if needed. Run the workflow Execute the workflow, and images will be automatically retrieved, resized, and inserted into the document. Customization Resize Dimensions: Adjust the width/height in the Image Resize node to fit your document’s style. Ordering Logic: Modify the sorting step if you want alphabetical or upload-date order instead of numeric order. Error Notifications: Add an email or Slack node to notify you when an image fails to insert. Image Placement: By default, images are appended. You can adjust the insert logic (e.g., after specific headings).

GitHub Bounty Issue Tracker & Alert System (Google Sheets + Email/WhatsApp) Overview Looking for a way to track GitHub bounty issues automatically and get notified in real time? This GitHub Bounty Tracker workflow monitors repositories for issues labeled 💎 Bounty, logs them in Google Sheets, and sends instant alerts via Email (HTML-styled) or WhatsApp. Perfect for developers, freelancers, and open-source contributors who want to discover and claim paid opportunities faster. What This Workflow Does 🔎 Automated Bounty Discovery Searches GitHub hourly for all open issues labeled with “💎 Bounty.” Filters duplicates to avoid re-tracking the same issue. 📢 Smart Notifications Sends styled HTML email alerts with GitHub-themed design. WhatsApp Business API integration (optional, disabled by default). Alerts only for bounties created within the last 5 days. 📊 Google Sheets Tracking Sheet1**: Complete bounty list (all tracked issues). Sheet2**: Recent notification log (for quick reference). 🔄 Status Updates Checks every 6 hours for issue changes (open/closed state, new comments). Includes bounty amount, issue details, and direct GitHub links. Use Cases 👩‍💻 Freelance developers hunting for paid open-source work. 🛠 Development teams tracking bounty opportunities for their stack. 🌍 Community managers monitoring open-source bounty program engagement. 🤝 Open-source contributors looking for compensated tasks. Requirements GitHub Personal Access Token (with repo access). Google Sheets (2 sheets required: Sheet1 = bounties, Sheet2 = notifications). Gmail account (OAuth2 for sending email alerts). WhatsApp Business API credentials (optional). Configuration Notes This workflow supports pagination for large result sets and includes filters to prevent duplicate notifications. You can customize the GitHub search query in the HTTP Request node to target: Specific repositories Custom labels Team/organization projects Frequently Asked Questions (FAQ) Q: How often will I get notifications? A: By default, new bounties trigger alerts once an hour. Updates on existing issues (status/comments) are checked every 6 hours. Q: Do I need WhatsApp integration? A: No, it’s optional. Email alerts work out-of-the-box. Q: Can I filter by bounty amount? A: Yes, the workflow extracts bounty details and you can add filters in your Google Sheets or notification logic. Why Use This GitHub Bounty Tracker? Unlike manual searches, this workflow ensures you never miss a paid GitHub issue. Whether you’re a freelancer looking for income, a team seeking funded tasks, or a contributor wanting recognition and rewards, this system keeps you updated automatically.

Error Handler: WhatsApp Alert & Gmail Report for Failed Workflows 🎯 What This Template Does / How it Works This template provides a robust, two-step system for handling critical errors in your n8n workflows. It ensures that no workflow failure goes unnoticed, immediately notifying your team via a fast, urgent channel and providing a detailed record via a formal channel. Instant Trigger & Data Capture: The Error Trigger automatically captures all necessary metadata when an assigned workflow fails, including the error message and ID. Contact Configuration: The Set node centralizes and prepares recipient contact information (email and phone number) from the error data. Rapid Response: An urgent notification is sent via WhatsApp for immediate team awareness. Traceability & Record-Keeping: A short Wait node introduces a delay to prevent notification spam. Following the pause, a comprehensive report is sent via Gmail, ensuring a detailed record of the incident is archived. This design guarantees high-priority alerts are handled rapidly, while still maintaining essential documentation. Who’s It For This template is ideal for Ops Teams, Developers, and Automation Engineers who rely on mission-critical n8n workflows (e.g., payment processing, lead capture, data synchronization). If a failure requires immediate human intervention, this system is essential. How to Set Up Setting up this robust error handler is quick and essential for workflow stability: Configure Credentials: Ensure you have the necessary credentials added to your n8n instance for: WhatsApp Business API (for the Send message node). Gmail (for the Send Email node). Define Recipients: In the set_recipient_EMAIL/NUMBER node, replace the placeholder values with the actual email address and phone number of your incident team. Activate the Listener: Open the settings of the primary workflow you wish to monitor.Go to settings ,navigate to the Error Workflow field and select the name of this template (the Error Handler). Save Changes: Save both this Error Handler workflow and the primary workflow. Done! Any failure in the primary workflow will now automatically trigger this alert system. Requirements Gmail Account (Configured as a resource). WhatsApp Business API Access (Configured as a resource and a pre-approved template available).

🗓 Preventive Maintenance Scheduler via ICS Email (n8n | Google Sheets | Gmail) This workflow automatically reads your daily preventive maintenance schedule from Google Sheets and sends each assigned team member a personalized calendar invite (.ICS) as an email attachment. No more manual reminders or copying events — your operations and field teams will always be on schedule with clear, actionable reminders! Who’s it For Maintenance teams at plants, renewable sites, factories. Facility and operations managers. Any field crew, service team or org using Google Sheets and email for coordination. Businesses wanting reliable, zero-touch preventive maintenance notifications. How it Works Daily Trigger: Workflow runs automatically every morning at 7:00 AM. Read Maintenance Tasks: Pulls all scheduled maintenance for today from Google Sheets. Generate ICS Data: Prepares universal calendar event details: summary, location, time, assignee, etc. Create ICS File: Converts event data into a standard .ics calendar invite file with correct timings and description. Send Calendar Invite Email: Sends a personalized email to each assignee, with the .ics file attached — ready to add to Outlook, Gmail or mobile calendar. How to Set Up Import the workflow JSON into your n8n instance. Set up connections in n8n: Authenticate Google Sheets (read access) and Gmail (send access). Format your Google Sheet with headers: date, asset, task, location, email Activate the workflow. It runs daily on schedule. You can test it manually for validation. Each day: Team members with tasks scheduled for that date are sent their personalized event invite. Requirements | Tool | Purpose | |-----------------|---------------------------------------| | n8n Instance | Run and schedule the automation | | Google Sheets | Source of maintenance schedule/tasks | | Gmail (or SMTP) | Email platform to send calendar files | How to Customize | Customization | How | |----------------------------------------|------------------------------------------------------------| | Change calendar invite/event wording | Edit title or description in the "Create ICS File" node | | Adjust event start/end times | Modify time logic in "Generate ICS Data" node | | Change daily send time | Tweak time in "Daily Trigger" node | | Use a different email provider (SMTP) | Swap Gmail node for SMTP node; link correct credentials | | Add extra notifications (SMS/Slack) | Add appropriate node after or before Send Email node | Add‑ons | Add-on | Description | |-------------------------|----------------------------------------------| | Recurring Tasks | Automate repeated tasks via your sheet/setup | | Email Logging | Log sent invites in another sheet/db | | WhatsApp/SMS Alerts | Add Twilio or WhatsApp for instant alerts | | Manager Summary | Send daily reports or dashboards to leads | | Pre-alerts | Add reminder emails 1hr / 1 day before event | Use Case Examples Wind turbine engineers receive daily calendar invites for inspections. Solar O&M operators are automatically reminded for inverter cleaning via calendar sync. Facility staff gets scheduled reminders for HVAC or safety checks without manual admin. Managers have a clear audit trail of which reminders were sent on time. Common Troubleshooting | Issue | Possible Cause | Solution | |-------------------------------------|---------------------------------------|-------------------------------------------------------| | No email received | Gmail/SMTP misconfigured | Check node credentials, token or SMTP settings | | Calendar file comes as .txt | Wrong file type/extension/MIME | Ensure "Create ICS File" outputs .ics and text/calendar | | No invites sent for today | No matching rows in Google Sheet | Check date/value format; add sample data for today | | Google Sheets returns error | Wrong Sheet ID/tab, access issue | Confirm correct Google Sheet is linked and shared | | Event time/zone is incorrect | Code node’s time logic not matching | Adjust start/end time settings in the code node | Need Help? Want guided setup, advanced reporting, Outlook synchronization or a full preventive maintenance dashboard? 👉 Contact WeblineIndia — Your n8n Automation partner for smart preventive maintenance and calendar-driven ops!

🤖 AI Contact Creator for LEDGERS (Works with Any Trigger) ### Before using this template: #### 👉 Search for LEDGERS in the nodes list and install it from Community Nodes (required for this workflow to run).== 🔧 What This Workflow Does: This smart n8n template automatically creates contacts in LEDGERS using AI, triggered by any node (like Google Sheets, Webhook, Airtable, Forms, etc.). It’s designed for teams who maintain contact data across platforms and want to auto-parse raw data using AI and sync it to LEDGERS—without manual entry. ⚙️ Flow Overview: Trigger Node – Can be anything: Google Sheets, Webhook, API call, etc. Chat Model (Claude / GPT-4o) – Uses AI to generate structured contact data from raw inputs. Structured Output Parser – Parses AI response into clean JSON. Form Loop & Iteration – Loops through fields in the structured output. Create a Contact – Sends the data to LEDGERS via API. LEDGERS Loop & Iteration – Supports bulk contact creation if needed. Success/Failure Path – Sends email notifications via Gmail node depending on the outcome. 💡 Use Case: Automate contact creation from form submissions, CRM exports, sheet updates, webhook data, etc. Clean and structure messy data with AI before syncing to LEDGERS. Save manual hours and reduce errors in contact data entry.