Workflow Templates

🔎 Automated Keyword Research Workflow with Google sheet logging & Semrush API Description: Easily collect keywords and country input, run automated keyword research via the Semrush Keyword Research API on RapidAPI, and store results in Google Sheets for seamless tracking and analysis. ⚙️ Node-by-Node Explanation 🟢 On form submission (formTrigger) Collects keyword and country inputs from the user via a simple form to start the research process. Triggers the workflow execution upon submission. 🌐 Keyword Research (httpRequest) Sends a POST request with user inputs (keyword and country) to the Semrush Keyword Research. Retrieves keyword suggestions, search volume, and related data for comprehensive keyword insights. 📄 Append Data to Google Sheet (googleSheets) Automatically appends the keyword research results into a connected Google Sheets document. Enables easy tracking, sharing, and further analysis of keyword data. 📈 Example Spreadsheet Structure | Keyword | Country | Search Volume | CPC | Competition | Keyword Difficulty | Related Keywords | Date of Research | |---------------|---------|---------------|------|-------------|--------------------|-------------------------------------|------------------| | keyword1 | US | 10,000 | $2.50| 0.75 | 45 | keyword2, keyword3 | 2025-09-09 | | example term | UK | 15,000 | $1.80| 0.60 | 38 | term1, example keyword | 2025-09-09 | 🌟 Benefits 🚀 Powered by **Semrush Keyword Research API on RapidAPI:** Reliable, up-to-date keyword insights accessible via a simple API integration. 🔄 Fully Automated: From user input to data storage, the process is seamless and requires no manual handling. 📊 Centralized Data Storage: Storing results in Google Sheets ensures accessibility and easy collaboration. 📈 Scalable & Repeatable: Run keyword research on-demand for multiple keywords and countries effortlessly. 🚀 Use Cases 🏢 SEO Agencies: Quickly gather keyword data for clients in different markets using the Semrush Keyword Research. 📱 Digital Marketing Teams: Monitor and expand keyword strategies by collecting keyword ideas and volume regularly through the Semrush Keyword Research. 🔎 Content Creators: Identify trending and high-traffic keywords tailored by country to optimize content via the Semrush Keyword Research API. 📅 Automated Reporting: Generate scheduled keyword research reports by integrating this workflow into larger marketing automation pipelines. 🔑 How to Get Your API Key for Semrush Keyword Research Visit the API Page: Go to the Semrush Keyword Research on RapidAPI. Sign Up/Login: Create an account or log in if you already have one. Subscribe to the API: Click "Subscribe to Test" and choose a plan (free or paid). Copy Your API Key: After subscribing, your API Key will be available in the "X-RapidAPI-Key" section under "Endpoints". Use the Key: Include the key in your API requests like this: -H "X-RapidAPI-Key: YOUR_API_KEY" 🛠 Customizing the Workflow To modify the automated workflow and adapt it to your specific use case, follow these guidelines: Adjust the Data Retrieval Process: You can modify the data you want to receive from the Semrush API. For example, if you’re only interested in search volume and CPC, you can filter out the other results in the API request. Add More Countries: If you work with multiple regions, modify the workflow to accept multiple country inputs. You could either pass in a list of countries or have a dropdown on the form that lets users select their country of choice. Expand Keyword Types: The workflow can be expanded to collect data for different types of keywords, such as long-tail or LSI (Latent Semantic Indexing) keywords, depending on your SEO needs. Set Up Scheduled Keyword Reporting: To automate reporting, you can schedule keyword research reports to run at regular intervals, such as monthly, using Google Apps Script or another task scheduler. This way, you’ll always have fresh data on hand for analysis. ✅ Tips for Smooth Workflow Integration Test Your API Integration: Run a test to check if data is properly flowing into your Google Sheet before automating the process. Set Up Notifications: Use Google Sheets' built-in notifications or an external automation tool (e.g., Zapier, Integromat) to notify you when new data is added or if there’s an issue with the workflow. Handle Errors Gracefully: Add error handling in your automated process to prevent issues like missing data or API request failures from disrupting your workflow.

AWS Certificate Manager (ACM) Auto-Renew with Slack notify & approval Who’s it for SRE/DevOps teams managing many ACM certs. Cloud ops who want hands-off renewals with an approval step in Slack. MSPs that need auditable reminders and renewals on schedule. How it works / What it does Schedule Trigger – runs daily (or your cadence). Get many certificates – fetches ACM certs (paginate if needed). Filter: expiring in next 7 days – keeps items where: NotAfter before today + 7d NotBefore before today (already valid) Send message and wait for response (Slack) – posts a certificate summary and pauses until Approve/Reject. Renew a certificate – on Approve, calls the renew action for the item. How to set up Credentials AWS in n8n with permissions to list/read/renew certs. Slack OAuth (bot in the target channel). Schedule Trigger Set to run once per day (e.g., 09:00 local). Get many certificates Region: your ACM region(s). If you have several regions, loop regions or run multiple branches. Filter (IF / Filter node) Add these two conditions (AND): {{ $json.NotAfter.toDateTime('s') }} is before {{ $today.plus(7,'days') }} {{ $json.NotBefore.toDateTime('s') }} is before {{ $today }} Slack → Send & Wait Message (text input): :warning: ACM Certificate Expiry Alert :warning: Domain: {{ $json.DomainName }} SANs: {{ $json.SubjectAlternativeNameSummaries }} ARN: {{ $json.CertificateArn }} Algo: {{ $json.KeyAlgorithm }} Status: {{ $json.Status }} Issued: {{ $json.IssuedAt | toDate | formatDate("YYYY-MM-DD HH:mm") }} Expires: {{ $json.NotAfter | toDate | formatDate("YYYY-MM-DD HH:mm") }} Approve to start renewal. Add two buttons: Approve / Reject (the node will output which was clicked). Renew a certificate Map the CertificateArn from the Slack Approved branch. Requirements n8n (current version with Slack Send & Wait). AWS IAM permissions (read + renew ACM), e.g.: acm:ListCertificates, acm:DescribeCertificate, acm:RenewCertificate (plus region access). Slack bot with permission to post & use interactivity in the target channel. How to customize the workflow Window size:** change 7 to 14 or 30 days in the filter. Catch expired: add an OR path {{ $json.NotAfter.toDateTime('s') }} is before {{ $today }} → send a **red Slack alert. Auto-renew w/o approval:** bypass Slack and renew directly for low-risk domains. Multiple regions/accounts:** iterate over a list of regions or assume roles per account. Logging:** add a Google Sheet/DB append after Slack click with user, time, result. Escalation:** if no Slack response after N hours, ping @oncall or open a ticket. Notes The Slack node pauses execution until a button is clicked—perfect for change control. Time conversions above assume NotAfter/IssuedAt are Unix seconds ('s'). Adjust if your data differs.

Overview This n8n workflow provides seamless integration with Cerebras' high-performance inference platform to leverage OpenAI's open-source GPT-OSS-120B model. With industry-leading speeds of thousands of tokens per second and ultra-low latency under 0.5 seconds, this template enables developers and businesses to build responsive AI applications without the complexity of managing infrastructure or dealing with slow response times that plague traditional AI integrations. How it works This streamlined workflow establishes a direct connection to Cerebras' inference API through four simple nodes. When a chat message is received, the workflow processes it through the configured API key, sends it to the Cerebras endpoint with your specified parameters (temperature, completion tokens, top P, reasoning effort), and returns the AI-generated response. Detailed Workflow Explanation 1. When chat message received: This trigger node initiates the workflow whenever a new chat message is detected. It captures the user's input and passes it to the next node in the chain, supporting various input formats and message sources. 2. Set API Key: A manual configuration node where you securely store your Cerebras API key. This node handles authentication and ensures your requests are properly authorized when communicating with the Cerebras inference API. 3. Cerebras endpoint: The core HTTP request node that communicates with Cerebras' chat completions API. This node is pre-configured to work with the GPT-OSS-120B model and includes parameter settings for temperature, completion tokens, top P, and reasoning effort that can be customized based on your specific needs. 4. Return Output: The final node that processes and formats the AI response, delivering the generated text back to your application or user interface in a clean, usable format. Who is it for Developers building real-time chat applications, conversational AI systems, or interactive web applications who need consistent sub-second response times without managing complex AI infrastructure. Content creators and marketing teams who require rapid text generation for blogs, social media content, product descriptions, or marketing copy, enabling faster content production cycles and improved productivity. Businesses implementing customer service automation, lead qualification systems, or interactive FAQ solutions where response latency directly impacts user experience and conversion rates. SaaS companies looking to integrate AI features into existing products without the overhead of training models or managing inference servers, allowing them to focus on core business logic. Researchers and data scientists experimenting with high-performance language models for prototyping, A/B testing different prompting strategies, or conducting performance benchmarks against other AI providers. Startups and small teams seeking enterprise-grade AI capabilities without the infrastructure costs or technical complexity typically associated with large language model deployment. Comprehensive Setup Instructions 1. Cerebras Account Setup Visit Cerebras and create a new account Complete email verification and profile setup Navigate to the API Keys section in your dashboard Generate a new API key and securely store it Review the rate limits for free tier accounts and upgrade if needed 2. N8N Workflow Configuration Import the template into your n8n instance Click on the "Set API Key" node and enter your Cerebras API key Configure the trigger node based on your input source (webhook, manual, scheduled) Test the workflow using the built-in execution feature 3. Parameter Customization Open the "Cerebras endpoint" node to access the parameter configuration Adjust temperature, completion tokens, top P, and reasoning effort based on your use case Save and test the workflow to ensure proper functionality Customization and Configuration Guide Model Parameters in the Cerebras Endpoint Node: Temperature** (0.0-2.0): Lower values (0.1-0.3) for factual, consistent responses; higher values (0.7-1.5) for creative, varied content Completion Tokens**: Set based on expected response length - 150 for short answers, 500+ for detailed explanations, 1000+ for long-form content Top P** (0.1-1.0): Controls response diversity; 0.9 works well for most applications, lower values for more focused responses Reasoning Effort**: Adjusts the model's computational effort for complex reasoning tasks; higher values for analytical or problem-solving queries Use Case Specific Configurations: Customer Support**: Temperature 0.2, moderate completion tokens, consistent helpful responses Creative Writing**: Temperature 1.0-1.2, higher completion tokens for diverse, imaginative content Technical Documentation**: Temperature 0.3, structured output with examples and code snippets Casual Conversation**: Temperature 0.7, balanced creativity and coherence Integration Scenarios: Connect the trigger to webhooks for external application integration Modify the output node to format responses for specific platforms (Slack, Discord, web apps) Add conditional logic to handle different types of user queries Implement input validation and sanitization for production environments Possible Enhancements Multi-model support: Extend the workflow to switch between different Cerebras models based on query complexity or specific requirements. Response caching: Add caching mechanisms to store frequently requested responses, reducing API calls and improving performance. Advanced error handling: Implement retry logic and fallback mechanisms for improved reliability in production environments. Content filtering: Integrate moderation capabilities to ensure appropriate responses in customer-facing applications. Analytics integration: Connect monitoring tools to track usage patterns, response quality, and performance metrics. Multi-channel triggers: Set up automated responses for various platforms like Slack, Discord, or custom webhooks. Template management: Create reusable prompt templates for different scenarios and use cases. Output formatting: Add post-processing for specific output formats (HTML, Markdown, JSON) based on integration requirements.

Example generated with this workflow: Simply upload a image and a watermark file, and the workflow will automatically combine them into a professional watermarked image. Use cases include adding logos to content, branding product photos, or protecting images with copyright marks. Good to know Completely free solution with no ongoing costs or subscriptions Processing typically takes 5-15 seconds depending on image size The workflow uses a polling mechanism to check job completion every 3 seconds Supports standard image formats (PNG, JPG, etc.) No credit card required to get started How it works The Form Trigger creates a user-friendly upload interface for two files: main image and watermark Both images are uploaded simultaneously to the API's file storage via parallel HTTP requests The uploaded file URLs are aggregated and used to create an image composition job The workflow polls the API every 3 seconds to check job completion status Once completed, the final watermarked image is downloaded and returned as a file download The watermark is automatically positioned in the bottom-right corner with 50% opacity, but this can be easily customized. How to use The form trigger provides a clean interface, but you can replace this with other triggers like webhooks or manual triggers if needed. The workflow handles all file processing automatically and returns the result as a downloadable file. Requirements Free account at jsoncut.com API key with full access (generated at app.jsoncut.com) HTTP Header Auth credential configured in n8n with header name x-api-key Setup steps Sign up for a free account at jsoncut.com Navigate to your dashboard at app.jsoncut.com → API Keys and create a new key with full access In n8n, create an HTTP Header Auth credential named "JsonCut API Key" Set the header name to x-api-key and the value to your API key Apply this credential to all HTTP Request nodes in the workflow Customising this workflow The watermark positioning, size, and opacity can be easily adjusted by modifying the JSON body in the "Create Job" node. You can change: Position coordinates (x, y values from 0 to 1) Watermark dimensions (width, height in pixels) Transparency (opacity from 0.1 to 1.0) Output image dimensions Fit options (cover, contain, fill) For more advanced image generation examples and configuration options, check out the documentation and image generation examples. For bulk processing, you could extend this workflow to handle multiple images or integrate it with cloud storage/database services.

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 template demonstrates how to use Blurit to anonymize faces and/or license plates in images or videos directly within your workflow. Use cases include: automatically anonymizing dashcam videos, securing photos before sharing them publicly, or ensuring compliance with privacy regulations like GDPR. How it works The workflow starts with a Form Trigger where you can upload your image or video file. An HTTP Request node authenticates with the BlurIt API using your Client ID and Secret. The file is then uploaded to BlurIt via an HTTP Request to create a new anonymization task. A polling loop checks the task status until it succeeds. Once complete, the anonymized media is retrieved and saved using a Write Binary File node. How to use Replace the placeholder credentials in the Set Auth Config node with your BlurIt Client ID and Secret (found in your BlurIt Developer Dashboard). Execute the workflow, open the provided form link, and upload an image or video. The anonymized file will be written to your chosen output directory (or you can adapt the workflow to upload to cloud storage). Requirements A BlurIt account and valid API credentials (Client ID & Secret). A running instance of n8n (cloud or self-hosted). (Optional) Access to a shared folder or cloud storage service if you want to automate file delivery. Need Help? Contact us at support@blurit.io, or visit the BlurIt Documentation. Happy Coding!

This n8n template makes it easy to perform DNS lookups directly within your n8n workflow using dns.google, without any API credentials. Use Cases Track changes:** Schedule execution and log DNS answers to track changes to records over time. Monitoring and alerts:** Schedule execution for DNS monitoring to detect misconfiguration and to trigger immediate alerts. Prerequisite checks:** Use in more extensive workflows to ensure DNS resolves correctly before running a website crawl or other sensitive tasks. Good to Know Requires no API credentials. You do not need to sign up for any third party service for DNS resolution. Can easily be modified to use with a webhook instead of the default Forms node for external triggering. By default performs lookup for: A CNAME AAAA MX TXT NS How It Works The workflow checks the input for a specified DNS type. If none is found, it uses all types in a predefined list. It splits the data into separate items for each DNS type. It loops through all items and executes DNS resolution via the highly reliable dns.google service. It aggregates all results into a single, easy-to-use output structure. How to Use Import the template and execute the workflow to enter the domain you want to look up in the Form interface. Connect the final output node to your specific use case (logging, alerting, subsequent workflow steps, etc.).

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

Description This automation publishes to 9 social platforms daily! Manage your content in a simple Google Sheet. When you set a post's status to "Ready to Post" in your Google Sheet, this workflow grabs your image/video from your Google Drive, posts your content to 9 social platforms, then updates the Google Sheet post status to "Posted". Overview 1. Trigger: Check Every 3 Hours Check Google Sheet for posts with Status ""Ready to Post"" Return 1 post that is ready to go 2. Upload Media to Blotato Fetch image/video from Google Drive Upload image/video to Blotato 3. Publish to Social Media via Blotato Connect your Blotato account Choose your social accounts Either post immediately or schedule for later Includes support for images, videos, slideshows, carousels, and threads Setup Sign up for Blotato Generate Blotato API Key by going to Settings > API > Generate API Key (paid feature only) Ensure you have "Verified Community Nodes" enabled in your n8n Admin Panel. Install "Blotato" community node. Create credential for Blotato. Connect your Google Drive to n8n: https://docs.n8n.io/integrations/builtin/credentials/google/oauth-single-service Copy this sample Google Sheet. Do NOT change the column names, unless you know what you're doing: https://docs.google.com/spreadsheets/d/1v5S7F9p2apfWRSEHvx8Q6ZX8e-d1lZ4FLlDFyc0-ZA4/edit Make your Google Drive folder containing images/videos PUBLIC (i.e. Anyone with the link) Complete the 3 setup steps shown in BROWN sticky notes in this template Troubleshooting Checklist your Google Drive is public column names in your Google Sheet match the original example file size < 60MB; for large files, Google Drive does not work, use Amazon S3 instead 📄 Documentation Full Tutorial Troubleshooting Check your Blotato API Dashboard to see every request, response, and error. Click on a request to see the details. Need Help? In the Blotato web app, click the orange button on the bottom right corner. This opens the Support messenger where I help answer technical questions

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.