Workflow Templates

Tagged with: , , , ,

Tagged with: , , , ,

Overview This workflow automates the process of generating niche-specific business leads from Google Maps, leveraging the Google Places API and Google Sheets for seamless data collection and storage. Who Is This For? Business owners**, marketers, sales teams, or anyone needing to build targeted lead lists by business type and location quickly. Main Use Cases Building outreach lists for local marketing campaigns. Finding potential clients in a specific location and industry. Automating research for sales prospecting. How It Works Collect Inputs via Form: Gather your business type (search term), target location, desired number of results, and Google Maps API key using a simple built-in form. Geocode Location: The workflow automatically converts your location input into geographic coordinates. Search Businesses: It utilizes the Google Places API to search for businesses that match your criteria within a 10-km radius of your location. Extract & Validate Data: For each business found, it extracts key contact details (name, address, phone, website, etc.), validates for essential info, and automatically appends valid leads into your connected Google Sheet—ready for action. Prerequisites Google account connected to Google Sheets. Active Google Maps API key. Your target Google Sheet is set up to receive leads. Setup Steps Connect your Google Sheets account inside n8n. Obtain a Google Maps API key (usually takes a few minutes from the Google Cloud Console). Configure the workflow: Fill out the form inside the workflow with your business type, location, number of results, and your API key. Run the workflow and watch qualified leads flow into your Google Sheet in real-time. Customization Options Adjust the search radius or result count to match your needs. Extend extracted fields or add filters for advanced lead qualification. Change the Google Sheet structure as per your business process. Example Output Each row in your sheet contains: Business Name Address Phone Website Google Maps URL Ratings & Reviews Business Types Search Query & Location Scraped At timestamp > Tip: > For more details and advanced customizations, refer to the in-workflow sticky notes.

This n8n automation connects your Typeform forms with Vapi AI, allowing you to immediately call new form respondents with a personalized message from a Vapi AI assistant, as soon as a form submission is received. 🧾 Requirements Typeform A Typeform account Typeform personal access token and credentials enabled in n8n A Typeform form published that includes a phone number field 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 n8n Typeform Credentials Setup Vapi Docs 🔄 Workflow Breakdown 1. Trigger: Typeform Submission Triggered when a new response is submitted to your Typeform. The form must include a phone number field. 2. Wait 2 Minutes Adds a short delay before proceeding. Useful to ensure form data is fully synced or to give time for related automations. 3. Set Vapi Fields (Manual Step) Set the required fields for the Vapi API call: phone number id - connected in Vapi assistant id - the assistant enabled in the call Vapi API key - your secure API key 4. Start Outbound Vapi Call Sends a POST request to https://api.vapi.ai/call Payload includes: Respondent’s phone number (from Typeform) Vapi assistant id Vapi phone number id to initiate the call ✏️ Template Customization Guidance How to Adapt for Your Specific Needs Personalize the Call Content:** Include additional fields in your Typeform (e.g., first name, interest, location). In n8n, map these form fields into the payload sent to Vapi. Update your Vapi assistant’s prompt/script to reference these variables for a highly personalized experience. Conditional Call Logic:** Use n8n's logic nodes (e.g., IF, Switch) to, for example: Only trigger calls if a respondent checks a checkbox (e.g., consent or interest). Use a different Vapi assistant or phone number based on responses (e.g., language preference or location). Advanced Routing:** Configure the workflow to choose different assistants, phone numbers, or call scripts based on the respondent’s answers. Store assistant IDs or numbers as environment variables or reference them from a lookup table for dynamic selection. 📞 Examples: Using Form Data to Personalize Calls Greeting by Name:** If your Typeform collects first_name, map it into the Vapi payload. Your assistant script can begin, "Hi {{first_name}}, thanks for your interest in XYZ!" Custom Message Based on Product Interest:** Add a product_interest field in Typeform. Pass its value to Vapi and have the assistant mention the product, e.g., “I see you’re interested in our Premium Plan…” Reference Appointment Times or Locations:** Collect appointment_time and/or city fields, and tailor the call to reconfirm booking details using these inputs. 🛠️ Troubleshooting & Tips Call Not Triggering:** Ensure your Typeform webhook connection and credentials are correctly set up in n8n. Check that your workflow is active and the trigger node is configured for the correct form. Invalid Phone Number Format:** Vapi requires numbers in full international format (e.g., +11234567890). Use n8n expressions to clean or verify the incoming number if needed. Missing Data in the Call:** Confirm that additional fields (e.g., first_name) exist in the Typeform response and that your mapping in n8n matches the exact field names. Failed API Call:** Double-check your Vapi phone number id, assistant id, and API key. Use n8n’s execution logs to inspect the payload sent to Vapi for debugging. Duplicate Calls:** If your Typeform allows multiple submissions, add logic in n8n to check for and avoid duplicate calls, for example by maintaining a record of called numbers. 🙋‍♂️ Need Help? Feel free to contact us at 1 Node Get instant access to a library of free resources we created.

Overview This workflow provides a universal webhook endpoint that dynamically routes incoming requests to different subflows. It allows you to manage multiple API-like endpoints from a single entry point, while ensuring proper error handling and consistent responses. How it works Webhook Receiver – A single URL accepts requests. Method Detection – Branches capture the request method. Route Resolver – Matches the action parameter and method against your route configuration. Execute Subflow – If valid, the matching workflow is executed. Error Handling – If invalid, the workflow responds with a clear status code and JSON error. About the action parameter The action query parameter is the key that controls routing: In your Routes Config, every route is defined with an action name, a list of allowed HTTP methods, and the target subflow ID. When a request comes in, the workflow looks up the provided action in this config. If the action is valid and the method is allowed, the corresponding subflow is executed. If not, the workflow returns a structured error. In other words: Config side** → map action → subflow ID Request side** → send ?action=... → determines which subflow runs This makes action both the mapping key in the configuration and the control key for triggering the correct logic. Setup steps Import the workflow into n8n. Define your routes in the Routes Config node. Each route contains: action name allowed HTTP methods target subflow ID This workflow is useful if you want to: Expose multiple clean API endpoints without creating many Webhook nodes Ensure consistent error handling across all endpoints Keep your n8n setup more structured and maintainable 👉 A practical solution to turn n8n into a flexible and maintainable API gateway.

This workflow provides automated access to the Black Forest Labs Flux Kontext Pro AI model through the Replicate API. It saves you time by eliminating the need to manually interact with AI models and provides a seamless integration for image generation tasks within your n8n automation workflows. Overview This workflow automatically handles the complete image generation process using the Black Forest Labs Flux Kontext Pro model. It manages API authentication, parameter configuration, request processing, and result retrieval with built-in error handling and retry logic for reliable automation. Model Description: A state-of-the-art text-based image editing model that delivers high-quality outputs with excellent prompt following and consistent results for transforming images through natural language Key Capabilities High-quality image generation from text prompts** Advanced AI-powered visual content creation** Customizable image parameters and styles** Tools Used n8n**: The automation platform that orchestrates the workflow Replicate API**: Access to the Black Forest Labs/flux-kontext-pro AI model Black Forest Labs Flux Kontext Pro**: The core AI model for image generation Built-in Error Handling**: Automatic retry logic and comprehensive error management How to Install Import the Workflow: Download the .json file and import it into your n8n instance Configure Replicate API: Add your Replicate API token to the 'Set API Token' node Customize Parameters: Adjust the model parameters in the 'Set Image Parameters' node Test the Workflow: Run the workflow with your desired inputs Integrate: Connect this workflow to your existing automation pipelines Use Cases Content Creation**: Generate unique images for blogs, social media, and marketing materials Design Prototyping**: Create visual concepts and mockups for design projects Art & Creativity**: Produce artistic images for personal or commercial use Marketing Materials**: Generate eye-catching visuals for campaigns and advertisements Connect with Me Website**: https://www.nofluff.online YouTube**: https://www.youtube.com/@YaronBeen/videos LinkedIn**: https://www.linkedin.com/in/yaronbeen/ Get Replicate API**: https://replicate.com (Sign up to access powerful AI models) #n8n #automation #ai #replicate #aiautomation #workflow #nocode #imagegeneration #aiart #texttoimage #visualcontent #aiimages #generativeart #flux #machinelearning #artificialintelligence #aitools #automation #digitalart #contentcreation #productivity #innovation

This workflow creates a user-friendly web form to upload a file, which allows users to upload a single large file (up to 5Gb) through a custom web form and automatically send it via TransferNow, handling the complex multi-part upload process required for large files. Advantages ✅ No manual steps: The entire process from file upload to email delivery is fully automated. ✅User-friendly: Anyone can upload files via a simple web form, without needing to access TransferNow directly. ✅Supports large files: TransferNow’s API handles large files that are not suitable for email attachments. ✅ Secure file delivery: The workflow uses TransferNow’s secure, expiring download links. ✅Customizable: You can easily adjust the workflow to support multiple file types, multiple recipients, or different validity rules. ✅Scalable: Works for individuals, teams, or businesses that frequently need to share large documents. How It Works The workflow is triggered when a user submits the embedded web form. Here is the process: Form Trigger: A user accesses the form, fills in the required details (Title, Message, Recipient Email), and uploads a single PDF file. Submitting the form starts the workflow. File Processing: The workflow calculates the size of the uploaded file, which is a necessary parameter for the TransferNow API. Transfer Creation: It sends a request to the TransferNow API to create a new file transfer. The API responds with details needed for the upload, including a unique transferId and uploadId. Upload URL Retrieval: The workflow requests a pre-signed upload URL from TransferNow for the specific part of the file. File Upload: The binary file data from the form and the upload URL from the previous step are merged. The workflow then performs a direct PUT request to the secured TransferNow URL to upload the file's binary content. Upload Confirmation: After the upload, the workflow informs the TransferNow API that the file part upload is complete. Finalization: Once the entire upload is confirmed, the workflow finalizes the transfer on TransferNow's side. Data Retrieval & Response: The workflow fetches the final transfer data, constructs a public download URL, and sends a success message back to the user's browser, displaying the recipient's email and the download link. Set Up Steps To use this workflow, you need to configure the connection to the TransferNow API. Get TransferNow API Credentials: Create a free account on TransferNow developer portal to get your API key (a 14-day free trial is available). Configure Credentials in n8n: In the n8n editor, locate the HTTP Request nodes named "Set Transfer", "Get Upload Url", etc. These nodes use a credential called "Header Auth TransferNow". You need to create this credential. Go to Credentials > Add Credential and select "HTTP Header Auth". Give it a name (e.g., "TransferNow API Key"). In the Name field, enter x-api-key. In the Value field, paste your personal TransferNow API key. Save the credential. The existing nodes will automatically use it, or you can select it from the dropdown in each node's credentials section. Activate the Workflow: Save the workflow and click the Activate toggle to make it live. Once activated, the On form submission node will provide a unique public URL for your form. Share this URL with users to start uploading and sending files. Need help customizing? Contact me for consulting and support or add me on Linkedin.

This guide explains how to send form data from n8n to a JotForm form submission endpoint using the HTTP Request node. It avoids the need for API keys and works with standard multipart/form-data. 📌 Overview With this workflow, you can automatically submit data from any source (Google Sheets, databases, webhooks, etc.) directly into JotForm. ✅ Useful for: Pushing information into a form without manual entry. Avoiding API authentication. Syncing external data into JotForm. 🛠 Requirements A JotForm account. An existing JotForm form. Access to the form’s direct link. Basic understanding of JotForm’s field naming convention. ⚙️ Setup Instructions 1. Get the JotForm Submission URL Open your form in JotForm. Go to Publish → Quick Share → Copy Link. Example form URL: sample form Convert it into a submission endpoint by replacing form with submit: Example: submit url 2. Identify Field Names Each JotForm field has a unique identifier like q3_name[first] or q4_email. Steps to find them: Right-click a field in your published form → choose Inspect. Locate the name attribute in the <input> tag. Copy those values into the HTTP Request node in n8n. Example mappings: First Name → q3_name[first] Last Name → q3_name[last] Email → q4_email 3. Configure HTTP Request Node in n8n Method:** POST URL:** Your JotForm submission URL (from Step 1). Content Type:** multipart/form-data Body Parameters:** Add field names and values. Example Body Parameters: { "q3_name[first]": "John", "q3_name[last]": "Doe", "q4_email": "john.doe@example.com" } 4. Test the Workflow Trigger the workflow (manually or with a trigger node). Submit test data. Check JotForm → Submissions to confirm the entry appears. 🚀 Use Cases Automating lead capture from CRMs or websites into JotForm. Syncing data from Google Sheets, Airtable, or databases. Eliminating manual data entry when collecting responses. 🎛 Customization Tips Replace placeholder values (John, Doe, john.doe@example.com) with dynamic values. Add more fields by following the same naming convention. Use n8n expressions ({{$json.fieldName}}) to pass values dynamically.

PDF to Markdown Converter (LlamaCloud) Description: How it works This workflow extracts structured content from complex PDFs using LlamaCloud's advanced parsing engine: Download PDF – Retrieves your PDF from Google Drive (or any source) Upload to LlamaCloud – Sends the PDF to LlamaCloud's parsing API and receives a job ID Poll for completion – Automatically checks parsing status every 30 seconds until complete Retrieve markdown – Fetches the clean, structured markdown output with preserved tables, layouts, and formatting The workflow handles complex PDFs with multi-column layouts, tables, and embedded images that traditional parsers struggle with. Set up steps Time estimate: ~5 minutes You'll need to configure one main integration: LlamaCloud API key – Sign up at cloud.llamaindex.ai, generate an API key, and create a Generic Header Auth credential in n8n with Authorization: Bearer YOUR_API_KEY Google Drive OAuth (optional) – Connect your Google account if using the Drive node, or replace with any PDF source Once configured, the workflow automatically handles parsing, retry logic, and markdown extraction. Output is ready for AI processing or content transformation workflows.

This n8n template automatically enriches HubSpot company records using CompanyEnrich and keeps your CRM data up to date without manual work. This workflow is ideal for RevOps, Sales Ops, and GTM teams who want cleaner CRM data for segmentation, scoring, and outbound workflows. Good to know Company enrichment is performed by domain, so a valid company domain is required. The workflow processes companies in batches to avoid rate limits. Enrichment is only applied when the API request is successful. How it works A Schedule Trigger runs the workflow on a recurring basis (weekly by default). The workflow fetches recently created or updated companies from HubSpot. The company domain is safely extracted, even if stored in different fields. Each domain is sent to the CompanyEnrich enrichment API. The workflow checks whether the enrichment request was successful. Enriched data is mapped into HubSpot-compatible fields. The corresponding HubSpot company record is updated. The workflow continues looping until all companies are processed. How to use Configure your HubSpot App Token with company read/write access. Add your CompanyEnrich API key as an HTTP credential. Adjust the schedule if you want the workflow to run daily or on-demand. Make sure your HubSpot companies have a domain set. Once active, the workflow will keep your company data enriched automatically. Requirements HubSpot account with App Token authentication CompanyEnrich account and API key n8n instance with HTTP and HubSpot nodes enabled Customising this workflow Change the schedule to run more frequently or trigger via webhook. Add filters to enrich only specific company segments or pipelines. Map additional enriched fields to custom HubSpot properties.

How it works This workflow automates FTP-to-Google Drive file transfers.It runs on a schedule, retrieves files in batches, downloads them from FTP, and uploads them to Google Drive while keeping original filenames.Batching ensures efficient, smooth processing without overloading the system. Step-by-step 1. Trigger and list files Schedule Trigger** – Starts the workflow at configured intervals. List Files from FTP** – Connects to the FTP server and retrieves a list of files from the target folder. 2. Batch processing setup Batch Files** – Splits files into small batches for sequential processing. 3. File handling Download File from FTP** – Downloads each file from FTP for further processing. 4. Cloud upload Upload to Google Drive** – Uploads the file to Google Drive, retaining its original name for consistency. Why use this? Eliminates manual FTP downloads and Google Drive uploads. Ensures smooth sequential processing with batch handling. Preserves original filenames for clarity and traceability. Runs automatically on a schedule, reducing human intervention. Scales easily to handle large volumes of files efficiently.

Who it’s for? Anyone calling a Google Cloud Run service from n8n who wants a small, reusable auth layer instead of wiring tokens in every workflow. What it does / How it works This sub-workflow checks whether an incoming id_token exists and is still valid (with a 5-minute buffer). If it’s good, it reuses it. If not, it signs a short-lived JWT with your service account, exchanges it at Google’s token endpoint, and returns a fresh id_token. It also passes through service_url and an optional service_path so the caller can hit the endpoint right away. (Designed to be called via Execute Workflow from your main flow.) How to set up Add your JWT (PEM) credential using the service account private_key. In Vars, set client_email (from your key) and confirm token_uri is https://oauth2.googleapis.com/token. Call this sub-workflow with service_url (and optional service_path). Optionally include a prior id_token to enable reuse. Inputs / Outputs Inputs: id_token (optional), service_url, service_path Outputs: id_token, service_url, service_path Notes Built for loops: pair with a Merge/Split strategy to attach id_token to each item. Keep credentials in n8n Credentials (no keys in nodes). Full write-up and context: Build a Secure Google Cloud Run API, Then Call It from n8n (Free Tier) — by Marco Cassar