Aitor | 1Node
Hi, I'm Aitor with 1 Node. We create practical AI solutions for businesses. Nothing fancy, just tools that solve real problems and help you scale. Always happy to have a conversation about how we might be able to help you grow
Categories
Templates by Aitor | 1Node
Build a personal assistant with Google Gemini, Gmail and Calendar using MCP
Talk to Your Apps: Building a Personal Assistant MCP Server with Google Gemini Wouldn't it be cool to just tell your computer or phone to "schedule a meeting with Sarah next Tuesday at 3 PM" or "find John Doe's email address" and have it actually do it? That's the dream of a personal assistant! With n8n and the power of MCP and AI models like Google Gemini, you can actually build something pretty close to that. We've put together a workflow that shows you how you can use a natural language chat interface to interact with your other apps, like your CRM, email, and calendar. What You Need to Get Started Before you dive in, you'll need a few things: n8n: An n8n instance (either cloud or self-hosted) to build and run your workflow. Google Gemini Access: Access to the Google Gemini model via an API key. Credentials for Your Apps: API keys or login details for the specific CRM, Email, and Calendar services you want to connect (like Google Sheets for CRM, Gmail, Google Calendar, etc., depending on your chosen nodes). A Chat Interface: A way to send messages to n8n to trigger the workflow (e.g., via a chat app node or webhook). How it Works (In Simple Terms) Imagine this workflow is like a helpful assistant who sits between you and your computer. Step 1: You Talk, the AI Agent Listens It all starts when you send a message through your connected chat interface. Think of this as you speaking directly to your assistant. Step 2: The Assistant's Brain (Google Gemini) Your message goes straight to the assistant's "brain." In this case, the brain is powered by a smart AI model like Google Gemini. In our template we are using the latest Gemini 2.5 Pro. But this is totally up to you. Experiment and track which model fits the kind of tasks you will pass to the agent. Its job is to understand exactly what you're asking for. Are you asking to create something? Are you asking to find information? Are you asking to update something? The brain also uses a "memory" so it can remember what you've talked about recently, making the conversation feel more natural. We are using the default context window, which is the past 5 interactions. Step 3: The Assistant Decides What Tool to Use Once the brain understands your request, the assistant figures out the best way to help you. It looks at the request and thinks, "Okay, to do this, I need to use one of my tools." Step 4: The Assistant's Toolbox (MCP & Your Apps) Here's where the "MCP" part comes in. Think of "MCP" (Model Context Protocol) as the assistant's special toolbox. Inside this toolbox are connections to all the different apps and services you use – your CRM for contacts, your email service, and your calendar. The MCP system acts like a manager for these tools, making them available to the assistant whenever they're needed. Step 5: Using the Right Tool for the Job Based on what you asked for, the assistant picks the correct tool from the toolbox. If you asked to find a contact, it grabs the "Get Contact" node from the CRM section. If you wanted to schedule a meeting, it picks the "Create Event" node from the Calendar section. If you asked to draft an email, it uses the "Draft Email" node. Step 6: The Tool Takes Action Now, the node or set of nodes get to work! It performs the action you requested within the specific app. The CRM tool finds or adds the contact. The Email tool drafts the message. The Calendar tool creates the event. Step 7: Task Completed! And just like that, your request is handled automatically, all because you simply told your assistant what you wanted in plain language. Why This is Awesome This kind of workflow shows the power of combining AI with automation platforms like n8n. You can move beyond clicking buttons and filling out forms, and instead, interact with your digital life using natural conversation. n8n makes it possible to visually build these complex connections between your chat, the AI brain, and all your different apps. Taking it Further (Possible Enhancements) This is just the start! You could enhance this personal assistant by: Connecting more apps and services (task managers, project tools, etc.). Adding capabilities to search the web or internal documents. Implementing more sophisticated memory or context handling. Getting a notification when the AI agent is done completing each task such as in Slack or Microsoft Teams. Allowing the assistant to ask clarifying questions if needed. Building a robust prompt for the AI agent. Ready to Automate Your Workflow? Imagine the dozens of hours your team could save weekly by automating repetitive tasks through a simple, natural language interface. Need help? Feel free to contact us at 1 Node. Get instant access to a library of free resources we created.
By Aitor | 1NodeBuild an MCP server with Airtable
Who is this for? This template is designed for anyone who wants to integrate MCP with their AI Agents using Airtable. Whether you're a developer, a data analyst, or an automation enthusiast, if you're looking to leverage the power of MCP and Airtable in your n8n workflows, this template is for you. What problem is this workflow solving? This template caters to MCP beginners seeking a hands-on example and developers looking to integrate Airtable MCP service. When integrating MCP with Airtable, manually updating AI Agents after changes to Airtable data on the MCP Server is time-consuming and error-prone. This template automates the process, enabling the AI Agent to instantly recognize changes made to Airtable on the MCP Server. In data management, for example, it ensures that record updates or additions in Airtable are automatically detected by the AI Agent. With detailed steps, it simplifies the integration process for all users. What this workflow does This workflow focuses on integrating MCP with Airtable within n8n. Specifically, it allows you to build an MCP Server and Client using Airtable nodes in n8n. Any changes made to the Airtable Base/Table on the MCP Server are automatically recognized by the MCP Client in the workflow. This means that you can make changes to your Airtable (such as adding, deleting, or modifying records) on the MCP Server, and the MCP Client in the n8n workflow will immediately detect these changes without any manual intervention. Setup Requirements An active n8n account. Access to Airtable API. A sample base and rows in Airtable that you can use to test. An API key from your preferred LLM to power the AI agent. Step-by-step guide Create a new workflow in n8n: Log in to your n8n account and create a new workflow. Add Airtable nodes: Search for and add the Airtable nodes to your workflow that you wish the MCP client to have access to. Set up the MCP Server and Client: Use the appropriate nodes in n8n to set up the MCP Server and Client. Connect the Airtable nodes to the MCP nodes as required. Activate and test the workflow: Talk to the chat trigger once all credentials have been updated and table data synced and try adding some rows, deleting or finding and updating cells. How to customize this workflow to your needs If you want to customize this workflow, you can: Modify the triggers: You can change the conditions under which the MCP Client detects changes. For example, you can set it to detect changes only in specific fields or based on certain record values in Airtable. Integrate with other services: You can add more nodes to the workflow to integrate with other services, such as sending notifications to Slack or triggering further actions based on the detected Airtable changes. --- Need help? Feel free to contact us at 1 Node. Get instant access to a library of free resources we created.
By Aitor | 1NodeTranscribe voice messages from Telegram using OpenAI Whisper-1
This n8n workflow processes incoming Telegram messages, differentiating between text and voice messages. How it works: Message Trigger: The workflow initiates when a new message is received via the Telegram "Message Trigger" node. Switch Node: This node acts as a router. It examines the incoming message: If the message is text, it directs the flow along the "text" branch. If the message contains voice, it directs the flow along the "voice" branch. Get Audio File: For audio messages, this node downloads the audio file from Telegram. Transcribe Audio: The downloaded audio file is then sent to an "OpenAI Transcribe Recording" node, which uses OpenAI's whisper-1 speech-to-text model to convert the audio into a text transcript. Send Transcription Message: Regardless of whether the original message was text or transcribed audio, the final text content is then passed to a "Send transcription message" node. Setup Requirements: Telegram Bot Token: You will need a Telegram bot token configured in the "Message Trigger" node to receive messages. OpenAI API Key: An OpenAI API key is required for the "Transcribe audio" node to perform speech transcription. Additional Notes: This workflow provides a foundational step for building more complex AI-driven applications. The transcribed text or original text message can be easily piped into an AI agent (e.g., a large language model) for analysis, response generation, or interaction with other tools, extending the bot's capabilities beyond simple message reception and transcription. 👉 Need Help? Feel free to contact us at 1 Node. Get instant access to a library of free resources we created.
By Aitor | 1NodeAuto-post breaking news content using Perplexity AI to X (Twitter)
Stay ahead of the curve and keep your followers informed—automatically. This n8n workflow uses Perplexity AI to generate insightful answers to scheduled queries, then auto-posts the responses directly to X (Twitter). --- ⚙️ What this workflow does Scheduled Trigger – Runs at set times (daily, hourly, etc.). searchQuery – Define what kind of trending or relevant insight you want (e.g. “latest AI trends”). set API Key – Securely insert your Perplexity API key. Perplexity API Call – Fetches a short, insightful response to your query. Post to X – Automatically publishes the result as a tweet. --- 🧩 Requirements An n8n account (self-hosted or cloud) A Perplexity API key A connected X (Twitter) account via n8n’s credentials --- ✅ Setup Steps Add this workflow into your n8n account. Edit the searchQuery node with a topic (e.g. “What’s new in ecommerce automation?”). Paste your Perplexity API key into the set API key node. Connect your X (Twitter) account in the final node. Adjust the schedule timing to suit your content frequency. --- 💡 Ideas to Improve 💬 Add a formatting step to shorten or hashtag the response. 📊 Pull multiple trending questions and auto-schedule posts. 🔁 Loop responses to queue a full week of content. 🌐 Translate content before posting to reach a global audience. --- 🆘 Need help? Feel free to contact us at 1 Node. Get instant access to a library of free resources we created.
By Aitor | 1NodeAutomate video content posting to multiple social platforms with Postiz
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. This workflow automates the distribution and scheduling of video content across multiple social platforms (TikTok, YouTube, Facebook, Instagram, Threads) through Postiz. Videos are collected from Google Drive, approved manually, and scheduled via the Postiz community node. --- 🧾 Requirements Google Drive account with access to the folder that will watch for new items uploaded. videos in mp4 format ready to be shared or, alternatively you can connect a community node from Cloud Convert to convert the format before uploading into Postiz. Postiz account with integrations for TikTok, YouTube, Facebook, Instagram, and Threads --- 🔗 Useful Links Postiz Docs Postiz Community Node --- 🔄 Workflow Steps Trigger: Google Drive File Added Watches your selected Google Drive folder for new file uploads. Download File Downloads the detected video from Drive. Upload to Postiz Video is uploaded to Postiz to prepare for social scheduling. Set Fields Manual setting of social options Extract Datetime (AI) Uses OpenAI to find/predict intended publish date & time, as the datetime format is required to schedule on Postiz Get Social Integrations Fetches a list of user’s connected platforms from Postiz. Split and Filter Integrations Splits the process per platform (TikTok, YouTube, Facebook, Instagram, Threads). Schedule Post For each enabled platform, schedules the video with chosen options. --- 🙋♂️ Need Help? Connect with 1 Node
By Aitor | 1NodeGenerate Daily E-Commerce Order Reports with Supabase, GPT-4.1 and Gmail
This n8n workflow automates the generation and delivery of a daily order summary via email. It leverages an AI Agent to fetch and summarize e-commerce order data from the last 24 hours stored in Supabase, providing a concise overview of the daily business operations. How it works Scheduled Trigger: The workflow is triggered every day at 8 AM. Sender Email Configuration: A manual step allows you to set the sender's email address. AI Agent: An AI Agent node acts as the central intelligence, interacting with various tools to gather and process data. Supabase Data Fetching: The AI Agent calls "Get Orders," "Get Order Items," "Get Clients," and "Get Products" tables to retrieve relevant e-commerce data from your Supabase database. OpenAI Chat Model: An OpenAI Chat Model with the 4.1 model is integrated to help the AI Agent understand and summarize the fetched data into a human-readable format. Gmail Summary: Finally, the workflow sends a summarized report to your specified email address using the "Send Gmail Summary" node. Set up steps This setup will take approximately 15-20 minutes. Download the workflow: Download this workflow and import it into your n8n instance. Configure the Daily 8am trigger: Ensure the "Daily 8am" trigger is active and set to your desired timezone. Set Sender Email: In the "Set Sender Email" node, manually enter the email address you wish to use as the sender for the daily reports. Configure AI Agent: Chat Model: Connect your OpenAI Chat Model credential. Memory & Tools: Ensure all the necessary nodes ("Get Orders", "Get Order Items", "Get Clients", "Get Products", "Send Gmail Summary") are correctly linked to the AI Agent. In our workflow we call data from 4 tables in Supabase. Configure Supabase Database Connections: For each of the "Get Orders," "Get Order Items," "Get Clients," and "Get Products" nodes, you will need to configure your Supabase credentials to access your e-commerce database. Select the tables (e.g., orders, order_items, clients, products) that you want the AI agent to pull data from in your Supabase schema. Configure Gmail Credentials: In the "Send Gmail Summary" node, connect your Gmail account credentials to allow n8n to send emails on your behalf. Test the workflow: Run the workflow manually to ensure all connections are working correctly and the email summary is generated as expected. Requirements n8n instance: An active n8n instance (self-hosted or cloud). Supabase Account: A Supabase account with your e-commerce order data accessible. OpenAI API Key: An OpenAI API key for the Chat Model. Gmail Account: A Gmail account credentials to send the daily summaries. Need help? Feel free to contact us at 1 Node. Get instant access to a library of free resources we created.
By Aitor | 1NodeAutomate outbound voice calls with Vapi from form submissions
This n8n automation connects your n8n form submissions to Vapi AI, enabling you to immediately call new respondents with a personalized voice AI assistant, as soon as the form is submitted. 🧾 Requirements n8n Form An n8n form node published and accessible to users. The form must include a phone number field: Accept full international phone number with + and country code. Example: +11234567890 (Optional) Add more form fields as needed for your use case. Vapi A Vapi account with credit. A connected phone number for outbound calls. An assistant created and ready to make calls. Your Vapi API key. 🔗 Useful Link Vapi calll endpoint --- 🔄 Workflow Breakdown Trigger: Form Submission (n8n Form) Starts when a submission is received from your form. Wait 2 Minutes Inserts a 2-minute pause before the next steps. Set Vapi Fields (Manual Step) Step-by-Step: Configuring Vapi Parameters in the ‘Set fields’ Node Open the ‘Set’ node where you map Vapi parameters. Add fields (if not present): phonenumberid: The sender phone number ID from your Vapi dashboard. assistant_id: The ID of the Vapi AI assistant you want to use. api_key: Paste your Vapi API key here (keep secure). (Optional) Add more fields for personalization, such as: first_name, product, reason, etc., if captured in your form. Start Outbound Vapi Call Sends a POST request to https://api.vapi.ai/call. Payload includes: Phone number from form Chosen assistant ID Vapi number ID Any additional info you choose to pass for customizing the call --- 🎨 Customization How to Adapt for Different Use Cases Collect More Info: Add fields to your n8n form for details such as name, product type, issue/context, preferred language, etc. Use Extra Data in Calls: In the HTTP request node, pass these fields in the API request body to Vapi. Tailor your assistant’s script to reference these for a personalized experience. Conditional Calls: Add n8n logic nodes to filter/categorize submissions (e.g., only call if a checkbox is ticked or if value matches certain criteria). Dynamic Assistant Selection: Select assistant or Vapi number based on user responses (e.g., route to different assistants by region or requested service). --- 📇 Using Additional Form Fields in Vapi Calls Any field collected on your n8n form can be included in the call payload, simply add it in the HTTP request payload. Vapi can use these variables for dynamically constructing prompts, personalizing the call flow, or branching logic in the interaction. Example: If your form collects firstname and appointmenttime, both can be sent to Vapi and referenced in the call script or as variables in your assistant’s logic. --- 🙋♂️ Need Help? Feel free to contact us at 1 Node Explore more free resources created for automating n8n and Vapi.
By Aitor | 1NodeAutomate outbound Vapi voice calls from new Google Sheets rows
This n8n automation connects your Google Sheets to Vapi, enabling you to automatically call new contacts as soon as their information is added to your spreadsheet. Instantly reach out with a personalized voice call from a Vapi AI assistant, based on any event that adds a new row to your sheet. 🧾 Requirements Google Sheets Google Sheets credentials enabled and tested in n8n. A table in your Google Sheet formatted as follows: Required Columns & Data Types | Column Name | Example Value | Data Type | Notes | |---------------|----------------|-------------------|-----------------------------------------------| | phone_number | +11234567890 | Text (String) | Must include the + and country code, no spaces or dashes. Mandatory for workflow. | | (optional) | first_name | John | Text (String) | For call personalization. | | (optional) | email | test@email.com | Text (String) | For follow-ups or records. | | (additional)| Any extra info | | | Can be used for advanced customization. | Ensure all columns contain data in plain text format. Phone number field must never be empty and follow the E.164 international format: + + country code + phone number. ---- Vapi A Vapi account with credit. A connected phone number (to originate calls). An assistant (AI voice agent) created and ready to make calls. Your Vapi API key. 🔗 Useful Link Vapi Docs --- 🛠️ Comprehensive Setup Instructions Prepare Your Google Sheet Create a Google Sheet with the required column names as listed above. Ensure your phone_number column is correctly formatted (international format, no spaces). Optionally, add columns such as first_name, email, or any field your workflow should use. Set Up Google Sheets Credentials in n8n In n8n, go to "Credentials" and create Google Sheets credentials. Authenticate with your Google account and test the connection. Configure the n8n Workflow Add a Google Sheets Trigger node: Set trigger mode to "New Row". Select your Google Sheet and worksheet. Add a Wait node: Configure a wait time (e.g., 4 minutes) between trigger and next action. Map & Set Vapi Fields Add a Set node: Create fields required by the Vapi API: phonenumberid: Copy from your Vapi dashboard. assistant_id: Use the ID of your AI assistant. api_key: Store securely (see n8n secret management). to: Set as the Google Sheet's phone_number value. Example: {{ $json["phone_number"] }} (Optional) Map extra fields from Sheet (e.g., first_name, email) for personalized calls. Add the HTTP Request to Vapi Add an HTTP Request node: Method: POST URL: https://api.vapi.ai/call Body parameters: Use all mapped fields from previous step. Test the Workflow Add a new row to your Google Sheet. Verify that, after the wait period, Vapi attempts the call and uses personalized information. --- 🎨 Customization Options Personalize Calls Further: Add additional columns like firstname, product, or appointmenttime in Google Sheets. Map these into the API call so Vapi can use them for dynamic greetings or contextual responses. Conditional Flows: Insert n8n logic nodes (IF, Switch) before making the Vapi call. For example, only call if a "Consent" column is TRUE, or select different assistants based on region or product interest. Multiple Assistants/Numbers: Store different assistant IDs or phone number IDs in columns, and dynamically route calls based on sheet data (e.g., region-specific assistants). Advanced Field Mapping: Pass any relevant sheet fields into the API payload and configure your Vapi assistant scripts to utilize these variables for high-touch, customized user interactions. --- 📇 Example Google Sheet Setup | phonenumber | firstname | email | product | consent | |--------------|------------|------------------|------------|---------| | +11234567890 | John | j@email.com | Widget A | TRUE | | +44207123456 | Maria | maria@x.co.uk | Widget B | FALSE | In n8n, map only those rows where consent=TRUE. --- 🙋♂️ Need Help? Feel free to contact us at 1 Node Get instant access to a library of free resources we created.
By Aitor | 1NodeAutomate outbound voice calls from Go High Level opportunities with Vapi
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 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. 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. 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. 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 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 Aitor | 1NodeAutomate Cal.com meeting attendee management with Google Sheets, Beehiiv & Telegram
This n8n workflow template automates the process of managing meeting guests booked through Cal.com. It captures attendee information, logs it in a Google Sheet, and subscribes new guests to your Beehiiv newsletter, while also notifying you in Telegram. How it Works This workflow is designed to streamline your post-booking process. When a new meeting is booked via Cal.com, the workflow automatically triggers. It extracts the attendee details, adds a new row with the guest's information to a designated Google Sheet, and then adds the guest as a subscriber to your Beehiiv newsletter. Finally, it sends a notification to a specified Telegram channel, keeping you informed of new subscribers. Features Automated Data Entry: Automatically log meeting guest details into Google Sheets. Newsletter Growth: Effortlessly add new meeting guests to your Beehiiv subscriber list. Real-time Notifications: Get instant alerts in Telegram for new subscribers. Seamless Integration: Connects Cal.com, Google Sheets, Beehiiv, and Telegram. Set Up To use this workflow, you will need the following: Cal.com: Set up a Cal.com account and configure a webhook to trigger the workflow on new bookings. You will need the webhook URL provided by the first node in this workflow. Google Cloud: A Google Cloud account with access to Google Sheets. You will need to specify the Sheet and the range where data should be added. Beehiiv: A Beehiiv account. You will need your Beehiiv API key and the publication ID of your newsletter. Telegram Account: A Telegram account and a channel where you want to receive notifications. You will need your Telegram Bot Token and the chat ID of the channel. Configure each node in the workflow with your respective API keys, IDs, and sheet details as required. The "Define your parameters" box in the workflow provides guidance on finding your Telegram chat ID and Beehiiv API key/publication ID. Additional Enhancements This workflow can be extended and customized further: Conditional Logic: Add filters to only subscribe guests based on certain criteria (e.g., specific meeting types). Data Enrichment: Integrate with other services to enrich guest data before adding to Google Sheets or Beehiiv. CRM Integration: Connect to a CRM to create or update contact records for new guests. Custom Notifications: Customize the content and format of the Telegram notification. Need Help? If you need assistance setting up this workflow, encounter any issues, or would like to explore setting up similar automation workflows tailored to your company's specific needs, please contact us at 1 Node.
By Aitor | 1NodeTrigger outbound Vapi AI voice calls from new Jotform submissions
This workflow connects JotForm submissions to Vapi AI, triggering a personalized outbound call via an AI voice assistant immediately after a user submits your form. Requirements JotForm A JotForm account JotForm API credentials enabled in n8n A published JotForm form with a phone number field Vapi A Vapi account with credit A connected phone number for making calls An assistant created and ready for outbound calls Your Vapi API key --- Workflow Steps JotForm Trigger Starts the workflow when a new form submission is received. Information Extractor Formats the phone number with a +, country code, and full number (e.g., +391234567890) for compatibility with Vapi. Set Fields for Vapi Configure these fields: phonenumberid: ID of the Vapi number used for the call assistant_id: ID of the Vapi assistant api_key: Your Vapi API key Start Outbound Vapi Call Sends a POST request to https://api.vapi.ai/call with: The formatted phone number All required Vapi fields Any additional info mapped from the form, for personalization --- Customization Add more form fields: Include extra data (such as name, appointment time) and add to the Vapi payload. Conditional logic: Use n8n filter nodes to control if/when calls are made. Dynamic assistant selection: Route submissions to different assistants or numbers based on user responses. --- Notes Ensure phone numbers are formatted correctly in the extractor node to prevent call errors. Any field from your form can be passed in the API payload and used in the assistant's script. --- Need Help? For additional resources or help, visit 1 Node.
By Aitor | 1NodeChat with uncensored Dolphin Mixtral 8x22B using Novita AI
This n8n workflow enables you to chat with the uncensored Dolphin Mixtral 8x22B large language model through the Novita AI inference. It provides a streamlined process for sending user messages to the model and returning its responses, making it easy to integrate into chatbots, automation, or internal tools. How It Works User messages are received from chat trigger The edit node prepares and formats the request for Novita AI's chat completion endpoint. The message is sent to Dolphin Mixtral 8x22B (uncensored) via the Novita API. The model's reply is extracted and returned as a clean string, ready for display or further automation. Set Up Steps Create a Novita AI account Sign up at Novita AI to access the API. Get your Novita API key Log into your Novita account and generate your API key. Configure the workflow in n8n Insert your Novita API key in the "Set fields" node, as well as additional endpoint parameters you might want to add to optimize your api (Optional) Customize or extend Add input triggers (chat, webhook, etc.), post-processing nodes, or error handling as needed. Useful links Novita chat completion docs Novita Privacy Policy Notes Dolphin Mixtral 8x22B is uncensored: The model is very permissive and does not have restrictive safety alignment, so ensure your use case is appropriate and consider adding your own safety checks, as well as reviewing Novita's privacy policy. You can review and adapt the workflow steps inside n8n to fit your requirements, such as saving chat logs, formatting responses, or integrating with other tools.
By Aitor | 1Node