by Aitor | 1Node
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.
by Viktor Klepikovskyi
Simple REST API with Google Sheets Introduction This workflow template demonstrates how to quickly and easily create a simple REST API using n8n and a Google Sheet as a no-code database. It's a perfect starting point for building a backend for small applications, prototypes, or internal tools without writing any code. Purpose The purpose of this template is to provide a complete, ready-to-use n8n workflow that handles all fundamental CRUD (Create, Read, Update, Delete) operations. The workflow uses a single Webhook trigger to handle POST, GET, PUT, and DELETE requests, allowing you to manage data in your Google Sheet through standard API calls. Setup Instructions To get started with this template, follow these steps: Prepare your Google Sheet: Create a new Google Sheet and add the following column headers in the first row: name, email, and status. You can use this example Google Sheet as a starting point. This sheet will serve as your database. Authenticate: In the n8n workflow, connect your Google Account credentials to the Google Sheets nodes. Select your data: Choose the Google Sheet and the corresponding sheet name from the drop-down lists in each of the Google Sheets nodes. Activate: Save and activate the workflow. Test the API: Use a tool like curl, Postman, or Insomnia to test your new API endpoints. The base URL will be your n8n webhook URL followed by /items. Example curl Commands: POST (Create):** curl -X POST YOUR_N8N_WEBHOOK_URL/items -H "Content-Type: application/json" -d '{"name": "Alice", "email": "alice@example.com", "status": "active"}' GET (Read All):** curl -X GET YOUR_N8N_WEBHOOK_URL/items/all GET (Read Single):** curl -X GET YOUR_N8N_WEBHOOK_URL/items?id=2 PUT (Update):** curl -X PUT YOUR_N8N_WEBHOOK_URL/items?id=2 -H "Content-Type: application/json" -d '{"status": "inactive"}' DELETE (Delete):** curl -X DELETE YOUR_N8N_WEBHOOK_URL/items?id=2 For more detailed instructions, including building the workflow in n8n, check out the full blog post: Build a Simple REST API in 10 Minutes with n8n & Google Sheets
by KlickTipp
Community Node Disclaimer This workflow uses KlickTipp community nodes, available for self-hosted n8n instances only. Who’s it for Marketing teams, agencies, and content creators who want to turn Instagram post comments into automated conversations — capturing leads, sending personalized DMs, and enriching contacts in KlickTipp without manual work. How it works This workflow automates engagement between Instagram users and your marketing funnel. It listens for new Instagram comments, validates the Meta webhook, and sends personalized DMs with form links. The workflow then stores and syncs user data for tagging and enrichment in KlickTipp. When a new comment appears, it: Validates the webhook setup via the Meta hub.challenge Captures the commenter’s username and ID Sends a personalized DM with a form link for lead capture Stores the data in Google Sheets for tracking Updates or tags the contact in KlickTipp The result: every Instagram comment turns into a structured, tagged lead for your marketing automation. How to set up Connect accounts for Meta (Instagram), Google Sheets, and KlickTipp. Set up your Meta App webhook for Instagram comments, using your workflow’s webhook URL and verify token (e.g., KlickTipp). Create a Google Sheet as a matching table with the columns: Instagram username Instagram ID Authenticate KlickTipp with API credentials and ensure your subscriber fields are configured. Test by commenting on a connected Instagram post to trigger the workflow. 💡 Pro Tip: Customize the DM to include your brand’s tone and lead form link for higher engagement. Requirements Meta (Instagram) Business Account Facebook Graph API with pages_messaging permission Google Sheets OAuth connection KlickTipp account with API access How to customize Replace the default form link with your own JotForm or landing page URL. Adjust DM content to fit your tone and campaign messaging. Add logic to send different DMs based on comment keywords. Integrate with KlickTipp tags for automatic segmentation. Expand the workflow to handle repeat commenters or trigger follow-ups.
by Yves Tkaczyk
Use cases Ensure that the calls to the workflow's webhook are (a) originating from the correct GitHub repository and (b) haven't been tampered with. How it works When a secret is provided in a GitHub webhook configuration, a x-hub-signature-256 header is added to the webhook. Compute HMAC256 computes the HMAC256 signature similarly to how it was computed by GitHub. Validate HMAC256 tests for the equality of the computed value and the value provided by the header. If the values are equal then 200 is returned to GitHub and the workflow continues If the values are NOT equal then 401 is returned and the workflow ends. Note: The Stop and Error step is optional and can be removed. Removing it means that the workflow completes successfully while still returning 401 to GitHub. This means that you will not be able to easily track malicious or incorrect calls to your webhook from n8n. How to use Add the steps (1) and (2) of the workflow to your current workflow receiving webhook calls from GitHub. Update the Secret field in the Compute HMAC256 node with the same value as the secret stored in the Secret field in the GitHub webhook definition. Requirements GitHub account and repository. GitHub webhook setup with a Secret key. Key can be of any length and should be generated with a key or password generator. Who’s it for Developers or DevOps engineers who want to ensure secure webhook communication between GitHub and n8n. How to customize the workflow This is a building block for your own workflow. If you use this workflow as a base, replace step (3) with your own business logic. You can modify the Stop and Error node to log unauthorized requests or trigger alerts. ⚠️ Warning The secret is stored in plain text in the workflow. You should take this into consideration if the workflow is committed to source control or shared in any other way. Need Help? Reach out on LinkedIn or Ask in the Forum!
by Lucas Walter
AI Influencer Ad Creative Generator Generate authentic-looking influencer marketing content by automatically combining your product images with reference photos of potential brand ambassadors. This workflow uses Google's Gemini AI to create realistic promotional images showing influencers naturally using your products in casual settings, perfect for social media campaigns and marketing materials. How it works Upload your product image** through a simple web form interface Automatically processes reference influencer photos** stored in your Google Drive folder AI generates realistic promotional images** using Gemini 2.5 Flash, showing each influencer naturally holding/using your product in cafe settings Saves all generated images** to your designated Google Drive output folder with organized naming Batch processes multiple influencer images** to create a complete campaign asset library The workflow creates candid, authentic-looking photos that appear as if a friend took a picture of the influencer enjoying your product - perfect for social media advertising that doesn't look overly promotional. Set up steps Connect Google Drive account to n8n for accessing influencer reference images and saving outputs Set up Google Gemini API credentials for AI image generation capabilities Create two Google Drive folders: one for storing your reference influencer photos, another for generated campaign assets Configure folder IDs in the workflow nodes to point to your specific Drive locations Upload reference influencer images to your source folder (headshots or casual photos work best) Deploy the form trigger to get your webhook URL for product image uploads Requirements: Google Drive account, Google Cloud account with Gemini API access, collection of reference influencer photos.
by Nalin
Discover relevant contacts from target accounts using Octave intelligent prospecting Who is this for? Sales development teams, account-based marketing professionals, and RevOps teams who are tired of generic job title filtering that misses the real decision makers. Built for teams that need to find the right people based on actual responsibilities and business context, not just titles on LinkedIn. What problem does this solve? Most prospecting tools are flying blind when it comes to finding the right contacts. You search for "VP of Engineering" but miss the "Head of Platform" who actually owns your use case. You filter by "Marketing Director" but the "Growth Lead" is the real buyer. Traditional prospecting relies on job title matching, but titles vary wildly across companies. This workflow uses Octave's context engine to find contacts based on who actually does the work your solution impacts, regardless of their specific job title. What this workflow does Target Account Processing: Reads target account lists from Airtable (or other data sources) Processes company domains for intelligent contact discovery Handles batch processing for multiple target accounts Context-Aware Contact Discovery: Uses Octave's prospector agent to find relevant stakeholders within target organizations Leverages your defined personas to identify the right people based on responsibilities, not just titles Analyzes organizational structure, role responsibilities, and KPIs to match contacts to your solution Discovers decision makers and influencers who might be missed by traditional job title searches Structured Contact Output: Returns discovered contacts with complete profile information Includes LinkedIn profiles, contact details, and role context Organizes contacts by relevance and decision-making authority Exports contact lists back to Airtable for sales team action Setup Required Credentials: Octave API key and workspace access Airtable API credentials (or your preferred contact management platform) Access to your target account list Step-by-Step Configuration: Set up Target Account Source: Add your Airtable credentials to n8n Replace your-airtable-base-id and your-accounts-table-id with your actual account list Ensure your account list includes company domains for prospecting Configure trigger method (manual, scheduled, or webhook-based) Configure Octave Prospector Agent: Add your Octave API credentials in n8n Replace your-octave-prospector-agent-id with your actual prospector agent ID Configure your prospector with relevant personas and role definitions Test prospecting with sample companies to verify contact quality Set up Contact Output Destination: Replace your-contacts-table-id with your target contact list table Configure field mapping between Octave output and your contact database Set up data validation and deduplication rules Test contact creation and data formatting Customize Contact Selection: Configure which personas to prioritize in your prospector agent Set relevance thresholds for contact discovery Define organizational levels to target (individual contributors vs. management) Adjust contact volume per account based on your outreach capacity Required Account List Format: Your Airtable (or data source) should include: Company Name Company Domain (required for prospecting) Account status/priority (optional) Target personas (optional) How to customize Prospector Configuration: Customize contact discovery in your Octave prospector agent: Persona Targeting:** Define which of your Library personas to prioritize when prospecting Role Responsibilities:** Configure the specific responsibilities and KPIs that indicate a good fit Organizational Level:** Target specific levels (IC, manager, director, VP, C-level) based on your solution Company Size Adaptation:** Adjust prospecting approach based on organization size and structure Contact Selection Criteria: Refine who gets discovered: Decision-Making Authority:** Prioritize contacts with budget authority or implementation influence Problem Ownership:** Focus on roles that directly experience the pain points your solution solves Technical Influence:** Target contacts who influence technical decisions if relevant to your offering Process Ownership:** Identify people who own the processes your solution improves Data Integration: Adapt for different contact management systems: Replace Airtable with your CRM, database, or spreadsheet system Modify field mapping to match your contact database schema Add data enrichment steps for additional contact information Integrate with email platforms for immediate outreach Batch Processing: Configure for scale: Adjust processing volume based on API limits and prospecting quotas Add scheduling for regular account list updates Implement error handling for accounts that can't be prospected Set up monitoring for prospecting success rates Use Cases Account-based marketing contact list generation Sales territory planning and contact mapping Competitive displacement campaign targeting Product expansion within existing customer accounts Event-based prospecting for specific personas Market research and competitive intelligence gathering
by KlickTipp
Community Node Disclaimer: This workflow uses KlickTipp community nodes. Introduction This workflow listens to Zoom webinar.ended events, validates the webhook (HMAC), fetches the past webinar details/participants, and tags each participant in KlickTipp based on attendance thresholds (e.g., ≥90%, ≥60%). It supports routing by webinar topic (Anfänger vs. Experten) so you can run differentiated follow-ups automatically. Benefits Hands-off segmentation** based on real attendance Accurate follow-ups** (full, partial, or no attendance) Scales to multiple webinars** with simple rule extensions Key Features Webhook validation** for Zoom URL registration (HMAC SHA256) Zoom API calls** to retrieve past webinar & participants by UUID Routing by webinar name** (Beginner/Expert) Attendance thresholds** via IF nodes (≥90% full, 60–89% partial) KlickTipp tagging** for engagement-driven campaigns Tags (KlickTipp Setup) Zoom webinar E-Mail Zustellung für Anfänger Zoom webinar E-Mail Zustellung für Anfänger attended Zoom webinar E-Mail Zustellung für Anfänger attended fully Zoom webinar E-Mail Zustellung für Anfänger not attended Zoom webinar E-Mail Zustellung für Experten Zoom webinar E-Mail Zustellung für Experten attended Zoom webinar E-Mail Zustellung für Experten attended fully Zoom webinar E-Mail Zustellung für Experten not attended Important Note This workflow is based on the companion workflow “Automate Webinar Registration with Zoom & KlickTipp Form Integration”. ➡️ Both workflows must be activated together for the automations to function correctly. In KlickTipp you should: Create a landing page for webinar registration. Set up an email campaign for invitations and follow-ups. Manually create the necessary tags based on list above** Testing & Deployment End a Zoom webinar tied to this flow. Confirm the webhook triggers and participants are fetched. Verify the correct attendance tags appear on contacts in KlickTipp. > 💡 Tip: Use test emails and tweak duration to simulate different attendance bands. Customization Adjust thresholds (e.g., 80% for “full”) in IF nodes. Duplicate routing/tag blocks to support more webinar topics. Add error handling (e.g., retries or alerts) for API edge cases. Resources: Use KlickTipp Community Node in n8n Automate Workflows: KlickTipp Integration in n8n
by Aitor | 1Node
This workflow triggers when a new opportunity is created in Go High Level (GHL), fetches the associated contact details, and initiates an outbound call using Vapi. The call is made by a Vapi assistant configured with the appropriate credentials. 🧾 Requirements Go High Level (GHL) A Go High Level account GHL developer private app and credentials enabled in n8n Webhook URL** from n8n added to your GHL private app Vapi A Vapi account with credit A connected phone number to make calls An assistant created and ready to make calls Your Vapi API key 🔗 Useful Links GHL Docs Vapi Docs n8n GHL Credentials Setup 🔄 Workflow Breakdown 1. Trigger: GHL Opportunity Created Triggered by a Webhook (POST) from Go High Level when a new opportunity is created. Webhook URL must be enabled in your GHL private app. 2. Get a GHL Contact Retrieves contact details from GHL CRM using the contact ID from the opportunity. Includes information such as phone number, name, and custom fields. 3. Wait 5 Minutes Introduces a short delay before making the call to avoid immediate outreach. Helps ensure data is synced and gives the system time for any follow-up automation. 4. Set Vapi Fields (Manual Step) Set the required fields for the Vapi API call: vapiPhoneNumberId – the number id making the call vapiAssistantId – the assistant who will handle the call vapiApi – your secure Vapi API key 5. Start Outbound Vapi Call Sends a POST request to https://api.vapi.ai/call Payload includes: Contact’s phone number Selected Vapi assistant Vapi phone number id to start the call ✅ Summary This n8n automation connects your CRM (Go High Level) with voice automation (Vapi) to immediately respond to new opportunities. Once a lead is created, they will receive a personalized voice call from a Vapi AI assistant. 🙋♂️ Need Help? Feel free to contact us at 1 Node Get instant access to a library of free resources we created.
by Stephan Koning
Master Outbound WhatsApp: Baserow & WasenderAPI This workflow integrates with your Baserow 'Messages' table, triggering on 'Sent' status. Messages fire via WasenderAPI, rigorously logged as 'Outbound' in Baserow. Gain total control; drive results. How it works Monitors Baserow 'Messages' table for 'Sent' status. Sends messages via WasenderAPI. Logs outbound details in Baserow. Who's it for For teams dominating outbound WhatsApp and centralizing Baserow logging. Demand communication efficiency? This is your solution. Setup Steps Rapid implementation. Action plan: Activate all critical workflow nodes. Copy Sent_whatsapp webhook URL. Configure Baserow automation (on 'Sent' status) to trigger webhook. Ensure Baserow 'Messages' table includes 'Status' ('Sent' option), linked 'WhatsApp Number', and 'Message Content' fields. (Optional: Baserow Message Form for input). Embed WasenderAPI and Baserow API tokens in n8n Credentials. Security is non-negotiable. Requirements Active n8n instance (self-hosted/cloud). WasenderAPI.com trial/subscription. Baserow account with pre-configured 'Contacts' (link) and 'Messages' (link) tables.
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: , , , ,
by System Admin
Tagged with: Workflows