Workflow Templates

🧼 Email Subscription Cleaner A fully automated workflow that cleans, validates, and restructures your subscriber list using Google Sheets and VerifiEmail. Perfect for marketers, SaaS teams, or anyone maintaining an email database. 🚀 What This Workflow Does In one automated run, it: Accepts a cleaning request via Webhook Extracts list settings, preferences, and options Fetches all subscribers from Google Sheets Normalizes emails and formats subscriber fields Performs real-time verification using VerifiEmail Classifies each subscriber as: remove (invalid / disposable / role), keep (valid & safe), tag (special cases) Deletes bad emails directly from the source sheet Stores all valid emails in a clean, curated CleanSubscribers sheet Returns a structured JSON summary to the caller 🔍 Why This Template Is Useful Improves deliverability Removes spam traps, bots, disposable domains Cleans and reorganizes messy lists Reduces bounce rates Builds a healthier mailing list for campaigns No CSV download/upload required — runs directly on Google Sheets 🧠 How It Works (In Simple Steps) Webhook receives batch-clean request Extract Inputs parses settings (listId, priority, options) Fetch Subscribers reads rows from Google Sheets Normalize each subscriber’s fields Validate Email quality (MX check, disposable, provider data) Merge subscriber info + validation results Classify each subscriber into keep/remove/tag Clean Up: remove → deletes the row keep → appends to clean list Respond with a clean JSON summary Fast, simple, reliable — perfect for weekly or on-demand cleanup. 🔧 Setup Required Connect 2 credentials: Google Sheets** (read / delete / append) VerifiEmail** (API key) Update: Sheet name (SubscriberList) Clean list sheet (CleanSubscribers) Optional tag rules in “Classify Email” No other configuration needed. 🏁 Perfect For Newsletters Marketing teams Event lists SaaS mailing lists CRM cleanup Lead verification Removing dead/invalid emails automatically 🏷️ Tags email, cleanup, validation, google-sheets, verifiemail, marketing, automation, list-cleaner, webhook

This n8n template demonstrates how to automatically generate personalized calendar views in Baserow, based on a chosen date field and a filter. Having a personalized view with only information that is relevant to you makes it easy to integrate with external calendar tools like Outlook or Google Calendar. Use cases are many: Task management (deadlines per staff member) Customer management (appointments per customer) Inventory management (delivery dates per supplier) Good to know You only need a Date field (e.g., a task deadline, due date, appointment date) and a Link to table field (e.g., a customer, employee, product) to make this work. The generated calendar views can be shared as .ics files and imported into any external calendar application. Authentication is done through a JWT token constructed from your Baserow username and password. How it works Set Baserow credentials**: Allows you to enter your Baserow credentials (username + password) and the API host path. The host is by default https://api.baserow.io, but you can change this in case you are self-hosting. The information is required to generate a JWT token that authenticates all future HTTP request nodes to create and configure the view. Create a token**: Generates a JWT token based on the information provided in the previous node. Set table and field ids**: Stores the generated JWT token and allows you to enter the ids of the tables and fields required to run the automation. Get all records from filter table** Gets all the records from the table you want to filter on. This is the table that has a Link to table field referencing the table with the Date field. Each record from this table will get it’s own view. Some examples: Customers, Employees and Products. Create new calendar view** Calls the API endpoint /api/database/views/table/{table_id} to create a new view. Check the Baserow API documentation for further details. The body of this requests configures the new view by setting among other things a name and the date field Create filter** Calls the API endpoint /api/database/views/{view_id}/filters/ to set a filter on the view so that it only shows the records that are relevant. This filter is based on the Link to table field that is set in earlier steps. Check the Baserow API documentation for further details. Set background color** Calls the API endpoint /api/database/views/{view_id}/decorations/ to set a a color on the background or left side of each item. By default, the color is based on a single select field, but it is also possible to use a condition. Check the Baserow API documentation for further details. Share the view** Calls the API endpoint /api/database/views/{view_id} to update the current view. It updates the ical_public property to true so that an ics link is created. Check the Baserow API documentation for further details. Update the url’s** Updates all the records in the table you want to filter on to fill in the url to the new generated view and the url to the ics file. This can be useful if you want to build an application on top of your database. How to use The Manual Trigger node is provided as an example, but you can replace it with other triggers such as a webhook The included Baserow SOP template works perfectly as a base schema to try out this workflow. Requirements Baserow account (cloud or self-hosted) A Baserow database with a table that has a Date field and a Link to Table field Customising this workflow Change the date field used to generate the calendars (e.g., deadline → appointment date). Adjust the filters to match your context (staff, customer, product, etc.). Configure which fields are shown using the /api/database/view/{view_id}/field-options/ endpoint. Check the Baserow API documentation for further details. Add or remove optional steps such as coloring by status or sharing the ics feed. Extend the workflow to notify staff when a new view has been created for them.

This n8n workflow automates the end-to-end proof-of-delivery process for logistics operations. It ingests POD data via webhook—including driver signatures, delivery photos, and GPS coordinates—performs AI-driven verification for package integrity and authenticity, updates ERP systems with delivery status, triggers automated invoicing for verified cases, and handles disputes by creating evidence-backed tickets and alerting teams. Designed for seamless integration, it minimizes errors in billing and reconciliation while accelerating resolution for mismatches. Benefits Reduced Manual Effort:** Automates verification and status updates, cutting processing time from hours to minutes. Enhanced Accuracy:** AI analysis detects damages, location discrepancies, and signature fraud with high confidence scores, preventing billing disputes. Faster Revenue Cycle:** Instant invoicing for verified deliveries improves cash flow and reduces DSO (Days Sales Outstanding). Proactive Dispute Management:** Generates high-priority tickets with linked evidence, enabling quicker resolutions and lower escalation costs. Audit-Ready Traceability:** Logs all decisions, AI outputs, and actions for compliance with logistics standards like ISO 9001. Scalability:** Handles high-volume deliveries without proportional staff increases, supporting growth in e-commerce fulfillment. Useful for Which Industry Logistics & Supply Chain:** Ideal for 3PL providers, freight forwarders, and courier services managing last-mile deliveries. E-Commerce & Retail:** Supports platforms like Amazon or Shopify sellers verifying customer receipts and automating returns. Manufacturing & Distribution:** Streamlines B2B shipments with ERP integrations for just-in-time inventory. Pharmaceuticals & Healthcare:** Ensures tamper-evident deliveries with photo verification for cold-chain compliance. Food & Beverage:** Tracks perishable goods with damage detection to maintain quality assurance. Workflow Process Webhook Intake:** Receives POD submission (driver ID, signature image, delivery photo, recipient, GPS) via POST/GET. Input Validation:** Checks for required fields; branches to error if incomplete. Parallel AI Verification:** AI Vision (OpenAI GPT-4): Analyzes photo for package condition, location match, and damage. Signature Validation: AI checks legitimacy, handwritten authenticity, and completeness. Merge & Decide:** Consolidates results with confidence scoring; routes to verified (true) or dispute (false). Verified Path:** Update ERP: POSTs status, timestamps, and coordinates to delivery system. Trigger Invoicing: Generates billable invoice with POD reference via billing API. Success Response: Returns confirmation to caller. Dispute Path:** Create Ticket: POSTs high-priority support ticket with evidence (images, scores). Alert Team: Notifies dispute team via email/Slack with issue summary and ticket link. Dispute Response: Returns status and next steps to caller. Error Handling:** Returns detailed feedback for invalid inputs. Setup Instructions Import Workflow: Paste JSON into n8n Workflows → Import from Clipboard. Configure Webhook: Set URL for POD submissions (e.g., from mobile apps); test with sample POST data. AI Setup: Add OpenAI API key to vision/signature nodes; specify GPT-4 model. Integrate Systems: Update ERP/billing URLs and auth in update/trigger nodes (e.g., https://your-erp.com/api). Dispute Config: Link support API (e.g., Zendesk) and notification service (e.g., Slack webhook). Threshold Tuning: Adjust confidence scores in decision node (e.g., >85% for auto-approve). Test Run: Execute manually with valid/invalid POD samples; verify ERP updates and ticket creation. Prerequisites n8n instance (v1.50+) with webhook and HTTP request nodes enabled. OpenAI API access for GPT-4 vision (image analysis credits required). ERP/billing APIs with POST endpoints and authentication (e.g., OAuth tokens). Support ticketing system (e.g., Zendesk, Jira) for dispute creation. Secure image storage (e.g., AWS S3) for POD uploads. Basic API testing tools (e.g., Postman) for endpoint validation. Modification Options Add OCR for recipient name extraction from photos in validation step. Integrate geofencing APIs for automated location alerts in AI vision. Support multi-signature PODs for group deliveries by expanding parallel branches. Add partial invoicing logic for mixed verified/disputed items. Incorporate blockchain for immutable POD records in high-value shipments. Extend alerts to SMS via Twilio for on-the-road driver notifications. Build analytics export to Google Sheets for delivery success rates.

Marker.io to ServiceNow Integration Automatically create ServiceNow incidents with full technical context when bugs are reported through Marker.io 🎯 What this template does This workflow creates a seamless bridge between Marker.io and ServiceNow, your IT service management platform. Every issue submitted through Marker.io's widget automatically becomes a trackable incident in ServiceNow, complete with technical details and visual context. This ensures your IT team can track, prioritize, and resolve bugs efficiently within their existing ITSM workflow. When a bug is reported, the workflow: Captures the complete Marker.io webhook payload Formats all technical details and metadata Creates a new incident in ServiceNow with the reporter information Includes comprehensive technical context and Marker.io links Preserves screenshots, browser info, and custom data ✨ Benefits Automated ticket creation** - No manual data entry required Complete context** - All bug details transfer automatically Faster triage** - IT teams see issues immediately in ServiceNow Better tracking** - Leverage ServiceNow's incident management capabilities Rich debugging info** - Browser, OS, and screenshot details preserved 💡 Use Cases IT Service Desks**: Streamline bug reporting from end users Development Teams**: Track production issues with full technical context QA Teams**: Convert test findings directly into trackable incidents Support Teams**: Escalate customer-reported bugs to IT with complete details 🔧 How it works N8N Webhook receives Marker.io bug report data JavaScript node formats and extracts relevant information ServiceNow node creates incident with formatted details Incident includes title, description, reporter info, and technical metadata Links preserved to both public and private Marker.io views The result is a fully documented ServiceNow incident that your IT team can immediately action, with all the context needed to reproduce and resolve the issue. 📋 Prerequisites Marker.io account** with webhook capabilities ServiceNow instance** with API access enabled ServiceNow credentials** (username/password or OAuth) Appropriate ServiceNow permissions** to create incidents 🚀 Setup Instructions Import this workflow into your n8n instance Configure the Webhook: Copy the production webhook URL after saving Add to Marker.io: Workspace Settings → Webhooks → Create webhook Select "Issue Created" as the trigger event Set up ServiceNow credentials: In n8n, create new ServiceNow credentials Enter your ServiceNow instance URL Add username and password for a service account Test the connection Customize field mappings (optional): Modify the JavaScript code to map additional fields Adjust priority mappings to match your ServiceNow setup Add custom field mappings as needed Test the integration: Create a test issue in Marker.io Verify the incident appears in ServiceNow Check that all data transfers correctly 📊 Data Captured ServiceNow Incident includes: Short Description**: Issue title from Marker.io Description** containing: 🐛 Issue title and ID 📊 Priority level and issue type 📅 Due date (if set) 📝 Full issue description 🖥️ Browser version and details 💻 Operating system information 🌐 Website URL where issue occurred 🔗 Direct links to Marker.io issue (public and private) 📦 Any custom data fields 📷 Screenshot URL with proper formatting 🔄 Workflow Components Webhook Node**: Receives Marker.io POST requests Code Node**: Processes and formats the data using JavaScript ServiceNow Node**: Creates the incident using ServiceNow API → Read more about Marker.io webhook events 🚨 Troubleshooting Webhook not triggering: Verify webhook URL is correctly copied from n8n to Marker.io Check that "Issue Created" event is selected in Marker.io webhook settings Ensure webhook is set to "Active" status in Marker.io Test with Marker.io's webhook tester feature Check n8n workflow is active and not in testing mode ServiceNow incident not created: Verify ServiceNow credentials are correct and have not expired Check that the service account has permissions to create incidents Ensure ServiceNow instance URL is correct (include https://) Test ServiceNow connection directly in n8n credentials settings Check ServiceNow API rate limits haven't been exceeded Missing or incorrect data: Screenshot URL broken: The workflow already handles URL formatting, but verify Marker.io is generating screenshots Custom data missing: Ensure custom fields exist in Marker.io before sending Due date formatting issues: Check your ServiceNow date format requirements JavaScript errors in Format node: Check webhook payload structure hasn't changed in Marker.io updates Verify all field paths match current Marker.io webhook schema Use n8n's data pinning to debug with actual webhook data Check for undefined values when optional fields are missing Connection issues: ServiceNow timeout: Increase timeout in node settings if needed SSL/Certificate errors: Check ServiceNow instance SSL configuration Network restrictions: Ensure n8n can reach your ServiceNow instance Authentication failures: Regenerate ServiceNow credentials if needed Testing tips: Use n8n's "Execute Workflow" with pinned test data Enable webhook test mode in Marker.io for safe testing Check ServiceNow incident logs for detailed error messages Monitor n8n execution logs for specific failure points

Sora 2 Video Generator - No Watermark (Minimal Setup) This n8n workflow enables you to generate professional AI videos using OpenAI's Sora 2 without watermarks. Create videos from text descriptions or animate your images with a simple web form interface - ready to use in just 5 minutes! Generate cinematic AI videos for social media, marketing campaigns, product demos, or creative projects. The workflow handles both text-to-video and image-to-video generation with automatic status polling until your video is ready. Good to know: • Kie.AI charges per video generation. Check their pricing page for current rates • Videos typically take 30-60 seconds for standard quality, 60-120 seconds for HD • The workflow automatically retries status checks every 30 seconds until completion • No watermarks on output videos How it works • Users submit video requests via a beautiful web form with description, aspect ratio, and quality options • The workflow detects if an image was uploaded and routes to either text-to-video or image-to-video • For image uploads, the file is automatically uploaded to ImgBB to generate a public URL • The request is sent to Sora 2 API via Kie.AI with your specifications (prompt, quality, aspect ratio) • The workflow waits 30 seconds, then checks if video generation is complete • If not ready, it automatically loops back and checks again every 30 seconds • Once complete, the video is downloaded and optionally sent via Telegram notification • Clean, watermark-free MP4 video output ready for use Set up steps Step 1: Get Kie.AI API Key • Sign up at kie.ai and navigate to your dashboard • Go to API Keys section and generate a new key • Copy the API key for the next step Step 2: Configure n8n Credentials • In n8n, go to Credentials → New Credential • Select "HTTP Header Auth" • Name: Kie Ai(Veo and more) (exact name required) • Header Name: Authorization • Header Value: Bearer YOUR_API_KEY • Save the credential Step 3: ImgBB Setup (for Image-to-Video) • Get a free API key from api.imgbb.com • Open the "Upload to ImgBB" node in the workflow • Replace the YOUR_ImgBB_API_KEY parameter with your ImgBB API key Step 4: (Optional) Telegram Notifications • Create a bot with @BotFather on Telegram • Get your Chat ID from @get_id_bot • Update YOUR_CHAT_ID in both Telegram nodes • Or delete Telegram nodes entirely if not needed Requirements • Kie.AI account with API access for Sora 2 • ImgBB account for image hosting (free tier available) • (Optional) Telegram bot for video delivery notifications Customising this workflow • Adjust wait times in the Wait nodes if generation takes longer in your region • Add email notifications instead of/in addition to Telegram • Modify the form to collect additional metadata (user info, project names, etc.) • Add error handling nodes for production deployments • Connect to cloud storage (Google Drive, Dropbox) instead of Telegram for video delivery • Integrate with your existing CMS or content management system For assistance and support: contact@bilsimaging.com

Website & API Health Monitoring System with HTTP Status Validation How it works Performs HTTP health checks on websites and APIs with automatic health status validation Checks HTTP status codes and analyzes JSON responses for common health indicators Returns detailed status information including response times and health status Implements conditional logic to handle different response scenarios Perfect for monitoring dashboards, alerts, and automated health checks Set up steps Deploy the workflow and activate it Get the webhook URL from the trigger node Configure your monitoring system to call the webhook endpoint Send POST requests with target URLs for health monitoring Receive JSON responses with health status, HTTP codes, and timestamps Usage Send POST requests to the webhook URL with target URL parameter Optionally configure timeout and status expectations in request body Receive JSON responses with health status, HTTP codes, and timestamps Perfect for monitoring dashboards, alerts, and automated health checks Use with external monitoring tools like Nagios, Zabbix, or custom dashboards Set up scheduled monitoring calls for continuous health validation Example request: Send POST with {"url": "https://your-site.com", "timeoutMs": 5000} Success response returns: {"ok": true, "statusCode": 200, "healthStatus": "ok"} Failure response returns: {"ok": false, "error": "Health check failed", "statusCode": 503} Benefits Proactive monitoring to identify issues before they impact users Detailed diagnostics with comprehensive health data for troubleshooting Integration ready - works with existing monitoring and alerting systems Customizable timeout settings, expected status codes, and health indicators Scalable solution to monitor multiple services with single workflow endpoint Use Cases E-commerce platforms: Monitor payment APIs, inventory systems, user authentication Microservices: Health validation for distributed service architectures API gateways: Endpoint monitoring with response time validation Database connections: Track connectivity and performance metrics Third-party integrations: Monitor external API dependencies and SLA compliance Target Audience DevOps Engineers implementing production monitoring System Administrators managing server uptime Site Reliability Engineers building monitoring systems Development Teams tracking API health in staging/production IT Support Teams for proactive issue detection

Watch Google Drive folder and use iLovePDF Compress Tool to save it in another Google Drive folder This n8n template shows how to upload a file in your Google Drive desired folder, compress it with the iLovePDF tool and move the compressed file to another folder. Good to know This is just an example of using it for you to know how the flow should start to work without issues. After the "combine" step, you can change it according your needs but always maintaining the four main steps of ILoveAPI's request workflow: start, upload, process and download (e.g., an step for sending an email with the compressed file instead of moving it to another folder) Use cases are many: With this template you can monitor a 'to-process' folder for large documents, automatically compress them for better storage efficiency, and move them to an archive folder, all without manual intervention. Then you can explore adapting it to have the functionalities that go best with you! How it works 1. Google Drive Trigger: The workflow starts when a new file is added to a specific Google Drive folder (the source folder). 2. Authentication: The Public Key is sent to the iLoveAPI authentication server to get a time-sensitive Bearer Token. 3. Start Task: A new compress task is initiated with the iLoveAPI server, returning a Task ID and Server Address. 4. Download/Upload: The file is downloaded from Google Drive and then immediately uploaded to the dedicated iLoveAPI Server using the Task ID. 5. Process: The main compression is executed by sending the Task ID, the server_filename, and the original file name to the iLoveAPI /process endpoint. 6. Download Compressed File: Download the compressed file's binary data from the iLoveAPI /download endpoint. 7. Save Compressed File: The compressed PDF is uploaded to the designated Google Drive folder (the destination folder). 8. Move Original File: The original file in the source folder is moved to a separate location (e.g., an 'Archived' folder) to prevent the workflow from processing it again How to use Credentials:** Set up your Google Drive and iLoveAPI credentials in n8n workflow. iLoveAPI Public Key:* Paste your iLoveAPI public key into the *Send your iLoveAPI public key to their server* node's body for authentication, and then in the *Get task from iLoveAPI server** node's body. Source/Destination Folders:* In the *Upload your file to Google Drive* (Trigger) and *Save compressed file in your Google Drive** (Action) nodes, select your desired source and destination folders, respectively. Requirements Google Drive** account/credentials (for file monitoring and storage) -see the docs provided in the node if needed. iLoveAPI** account/API key (for the compression service). An n8n instance (cloud or self-hosted). Need Help? See the iLoveAPI documentation

Overview This workflow uses the Defapi API with Google's Gemini AI to transform digital photos into authentic Polaroid-style vintage photographs. Upload your photos, provide a creative prompt, and get AI-generated vintage effects with that distinctive instant camera charm. Input: Digital photos + creative prompt + API key Output: Polaroid-style vintage photographs The system provides a simple form interface where users submit their images, prompt, and API key. It automatically processes requests through Defapi API, monitors generation status, and delivers the final vintage photo output. Ideal for photographers, content creators, and social media enthusiasts looking to add vintage charm to their digital photos. Prerequisites A Defapi account and API key: Sign up at Defapi.org An active n8n instance (cloud or self-hosted) with HTTP Request and form submission capabilities Digital photos for transformation (well-lit photos work best) Basic knowledge of AI prompts for vintage photo generation Example prompt: Take a picture with a Polaroid camera. The photo should exhibit rich saturation and vintage color cast, with soft tones, low contrast, and vignetting. The texture features distinct film grain. Do not change the faces. Replace the background behind the two people with a white curtain. Make them close to each other with clear faces and normal skin color. Setup Instructions Obtain API Key: Register at Defapi.org and generate your API key. Store it securely. Configure the Form: Set up the "Upload 2 Images" form trigger with: Image 01 & Image 02 (file uploads), API Key (text field), and Prompt (text field). Test the Workflow: Click "Execute Workflow" in n8n Access the form URL, upload two photos, enter your prompt, and provide your API key The workflow processes images, sends the request to Defapi API, waits 10 seconds, then polls until generation is complete Handle Outputs: The final node displays the generated image URL for download or sharing. Workflow Structure The workflow consists of the following nodes: Upload 2 Images (Form Trigger) - Collects user input: two image files, API key, and prompt Convert to JSON (Code Node) - Converts uploaded images to base64 and formats data Send Image Generation Request to Defapi.org API (HTTP Request) - Submits generation request Wait for Image Processing Completion (Wait Node) - Waits 10 seconds before checking status Obtain the generated status (HTTP Request) - Polls API for completion status Check if Image Generation is Complete (IF Node) - Checks if status equals 'success' Format and Display Image Results (Set Node) - Formats final image URL output Technical Details API Endpoint**: https://api.defapi.org/api/image/gen (POST request) Model Used: google/gemini (Gemini AI**) Status Check Endpoint**: https://api.defapi.org/api/task/query (GET request) Wait Time**: 10 seconds between status checks Image Processing**: Uploaded images are converted to base64 format for API submission Authentication**: Bearer token authentication using the provided API key Specialized For**: Polaroid-style vintage photography and instant camera effects Customization Tips Enhance Prompts**: Include specifics like vintage color cast, film grain texture, vignetting, lighting conditions, and atmosphere to improve AI photo quality. Specify desired saturation levels and contrast adjustments. Photo Quality**: Use well-lit, clearly exposed photos for best results. The AI can simulate flash effects and vintage lighting, but quality input produces better output. Note that generated photos may sometimes be unclear or have incorrect skin tones - try multiple generations to achieve optimal results.

Overview A cornerstone of your Order Management System, this workflow ensures seamless inventory control through fully automated stock checks, leading to a direct reduction in operational costs. It provides real-time alerts to the responsible personnel, enabling proactive issue detection and resolution to eliminate the financial damages associated with unexpected stock-outs. How it works Order Webhook Receives orders from external sources (e.g., website, form, or app) via API. Check Order Request Checks the validity of the order (e.g., complete product, valid customer details) Check Inventory Retrieve inventory information and compare it with the order request. Notifications Generate a notification to Slack for the manager indicating a successful order or an out-of-stock situation. Logging Log the process details to a Google Sheet for tracking. Set up steps Webhook Create a JSON request with the following format to call the Webhook Url { "id": "ORDER1001", "customer": { "name": "Customer", "email": "customer@example.com" }, "items": [ { "sku": "SKU001", "quantity": 2, "name": "Product A", "price": 5000 }, { "sku": "SKU002", "quantity": 2, "name": "Product C", "price": 10000 } ], "total": 30000 } Define the greater than or less than conditions on the inventory level to enter the corresponding branches. Google Sheet Clone the file to your Google Drive. (WMS Data Demo) Replace your credentials and connect. Access permission must be granted to n8n. Slack Replace your credentials and connect. A channel named "warehouse" needs to be prepared to receive notifications (if using a different name, you must update the Slack node).

Summary Automatically sync your Beex leads to HubSpot by handling both creation and update events in real time. How It Works Trigger Activation: The workflow is triggered when a lead is created or updated in Beex. Data Transformation: The nested data structure from the Beex Trigger is flattened into a simple JSON format for easier processing. Email Validation: The workflow verifies that the lead contains a valid email address (non-null), as this field serves as the unique identifier in HubSpot. Field Mapping: Configure the fields (via drag and drop) that will be used to create or update a contact in HubSpot. ⚠️ Important: Field names must exactly match the contact property names defined in HubSpot. Event Routing: The workflow routes the action based on the event type received: contact_create or contact_update. Branch Selection: If the event is contact_create, the workflow follows the upper branch; otherwise, it continues through the lower branch. API Request Execution: The corresponding HTTP request is executed POST to create a new contact or PUT to update an existing one both using the same JSON body structure. Setup Instructions Install Beex Nodes: Before importing the template, install the Beex trigger and node using the following package name: n8n-nodes-beex Configure HubSpot Credentials: Set up your HubSpot credentials with: Access Token (typically from a private app) Read/Write permissions for Contacts objects Configure Beex Credentials: For Beex users with platform access (for trial requests, contact frank@beexcc.com): Navigate to Platform Settings → API Key & Callback Copy your API key and paste it into the Beex Trigger node in n8n Set Up Webhook URL: Copy the Webhook URL (Test/Production) from the Beex Trigger Node and paste it into the Callback Integration section in Beex. Save your changes. Requirements HubSpot:* An account with a Private App Token and Read/Write permissions for *Contacts** objects. Beex:** An account with lead generation permissions and a Bearer Token configured in the Trigger Node. Event Configuration:* In the Beex platform's *API Key & Callback** section, enable the following events: "Update general and custom contact data" "Networking" Customization Options Contact Filtering:** Add filters to control which Beex leads should sync to HubSpot. Identifier Configuration:** By default, only leads with a valid email address are processed to ensure accurate matching in HubSpot CRM. You can modify this logic to apply additional restrictions. Field Mapping:** The "Set Fields Update" node is the primary customization point. Here you can map Beex fields to HubSpot properties for both creation and update operations (see Step 4 in How It Works). Field Compatibility:** Ensure that Beex custom fields are compatible with HubSpot's default or custom properties; otherwise, API calls will fail due to schema mismatches.

Transform Your Selfies into 3D Figurines with Nano Banana AI Overview This workflow utilizes the Defapi API with Google's Nano Banana AI model to transform your selfies into stunning 3D figurines, action figures, and collectible merchandise designs. Simply upload a selfie photo, provide a creative prompt describing your desired 3D figurine or action figure design, and watch as AI generates professional-quality product visualizations. Input: Your selfie photo + creative prompt + API key Output: AI-generated 3D figurine and action figure designs perfect for collectibles, merchandise, and product visualization Users can interact through a simple form, providing a text prompt describing the desired creative scene, a product image URL, and their API key. The system automatically submits the request to the Defapi API, monitors the generation status in real time, and retrieves the final creative image output. This solution is ideal for marketers, product designers, e-commerce businesses, and content creators who want to quickly generate compelling product advertisements and creative visuals with minimal setup. Perfect for creating 3D figurines and collectible merchandise designs. Prerequisites A Defapi account and API key: Sign up at Defapi.org to obtain your API key. An active n8n instance (cloud or self-hosted) with HTTP Request and form submission capabilities. Basic knowledge of AI prompts for product creative generation to achieve optimal results, especially for 3D figurines and collectible designs. Example prompt: Create a 1/7 scale commercialized 3D figurine of the characters in the picture, in a realistic style, in a real environment. The figurine is placed on a computer desk. The figurine has a round transparent acrylic base, with no text on the base. The content on the computer screen is the Zbrush modeling process of this figurine. Next to the computer screen is a packaging box with rounded corner design and a transparent front window, the figure inside is clearly visible. A product image for creative generation. Important Note: Avoid using dark photos as input, as the generated **3D figurine will also appear dark. Setup Instructions Obtain API Key: Register at Defapi.org and generate your API key. Store it securely—do not share it publicly. Configure the Form: In the "Upload Image" form trigger node, ensure the following fields are set up: Image (file upload), API Key (text field), and Prompt (text field). Test the Workflow: Click "Execute Workflow" in n8n. Access the generated form URL, upload your product image, enter your prompt, and provide your API key. The workflow will process the image through the "Convert to JSON" node, then send the request to the Defapi API. The system will wait 10 seconds and then poll the API status until the image generation is complete. Handle Outputs: The final "Format and Display Image Results" node formats and displays the generated creative image URL for download or embedding. Workflow Structure The workflow consists of the following nodes: Upload Image (Form Trigger) - Collects user input: image file, API key, and prompt Convert to JSON (Code Node) - Converts uploaded image to base64 and formats data Send Image Generation Request to Defapi.org API (HTTP Request) - Submits generation request Wait for Image Processing Completion (Wait Node) - Waits 10 seconds before checking status Obtain the generated status (HTTP Request) - Polls API for completion status Check if Image Generation is Complete (IF Node) - Checks if status equals 'success' Format and Display Image Results (Set Node) - Formats final image URL output Technical Details API Endpoint**: https://api.defapi.org/api/image/gen (POST request) Model Used: google/nano-banana (Nano Banana AI**) Status Check Endpoint**: https://api.defapi.org/api/task/query (GET request) Wait Time**: 10 seconds between status checks Image Processing**: Uploaded images are converted to base64 format for API submission Authentication**: Bearer token authentication using the provided API key Specialized For: **3D figurines, collectible merchandise, and product visualization Customization Tips Enhance Prompts: Include specifics like scene setting, lighting, style (e.g., realistic, artistic, cinematic), product placement, and visual elements to improve AI creative image quality. For **3D figurines, specify scale, materials, and display context. Form Fields*: The form accepts image files (image/), API key (text), and prompt (text) as required fields. Error Handling**: The workflow includes conditional logic to check for successful completion before displaying results. Best Practices for Nano Banana AI: Use detailed descriptions for **figurine designs, specify lighting conditions, and include environmental context for realistic 3D figurine generation. Photo Quality Tips: Use well-lit photos for best results. Avoid dark images as they will make the generated **3D figurine appear dark too.

Swap Tokens with Li.Fi The growing popularity of agentic payments has lead to the development of protocols like x402 where agents and humans can pay for internet resources over standard http protocols using stablecoins. This workflow lets you run your own swap relayer where callers can provide an x402-compatible payment header and a desired destination network to instantly receive gas tokens. This setup is trust minimized - user's have the following guarantees: They will be the receiver of the swap. Only the amount of tokens the authorized will be swapped. Setup In order to run this relayer workflow, you will need an account on 1Shot API. You must then import the 1Shot Gas Station contract into your business for any chain you wish to support with your relayer. Next, follow the directions in the worflow sticky notes to update the Payment Configs for the tokens you wish to support swaps for. Lastly, distrubute your webhook api endpoint to your users.