HumationHuman + Automation
Back to Catalog

Create a pizza ordering chatbot with GPT-3.5 - Menu, orders & status tracking

Irfan HandokoIrfan Handoko
7544 views
2/3/2026
ExportDailyAWS S3Error HandlingCSV
Official Page

Pizza Ordering Chatbot with OpenAI - Menu, Orders & Status Tracking

Introduction

This workflow template is designed to automate order processing for a pizza store using OpenAI and n8n. The chatbot acts as a virtual assistant to handle customer inquiries related to menu details, order placement, and order status tracking.

Features

The chatbot provides an interactive experience for customers by performing the following functions:

  1. Menu Inquiry: When a customer asks about the menu, the chatbot responds with a list of available pizzas, prices, and additional options.
  2. Order Placement: If a customer places an order, the chatbot confirms order details, provides a summary, informs the customer that the order is being processed, and expresses gratitude.
  3. Order Status Tracking: If a customer asks about their order status, the chatbot retrieves details such as order date, pizza type, and quantity, providing real-time updates.

Prerequisites

Before setting up the workflow, ensure you have the following:

Configuration Steps

Step 1: Set Up OpenAI API Credentials

  1. Log in to OpenAI's website.
  2. Navigate to API Keys under your account settings.
  3. Click Create API Key and copy the key for later use.

Step 2: Configure OpenAI Node in n8n

  1. Open n8n and create a new workflow.
  2. Click Add Node and search for OpenAI.
  3. Select OpenAI from the list.
  4. In the OpenAI node settings, click "Create New" under the Credentials section.
  5. Enter a name for the credentials (e.g., "PizzaBot OpenAI Key").
  6. Paste your API Key into the field.
  7. Click Save.

Step 3: Set Up the Chatbot Logic

  1. Connect the AI Agent Builder Node to the OpenAI Node and HTTP Request Node.
  2. Configure the OpenAI Node with the following settings:
    • Model: gpt-3.5-turbo
    • Prompt: Provide dynamic text based on customer inquiries (e.g., "List available pizzas," "Place an order for Margherita pizza," "Check my order status").
    • Temperature: Adjust based on desired creativity (recommended: 0.7).
    • Max Tokens: Limit response length (recommended: 150).
  3. Add multiple HTTP Request Node:
    • For Get Products: Fetch stored menu data and return details.
    • For Order Product: Capture order details, generate an order ID, and confirm with the customer.
    • For Get Order: Retrieve order details based on the order ID and display progress.

Step 4: Testing and Deployment

  1. Click Execute Workflow to test the chatbot.
  2. Open the Chat Message node, then copy the chat URL to access the chatbot in your browser.
  3. Interact with the chatbot by asking different queries (e.g., "What pizzas do you have?" or "I want to order a Pepperoni pizza").
  4. Verify responses and adjust prompts or configurations as needed.
  5. Deploy the workflow and integrate it with a messaging platform (e.g., Telegram, WhatsApp, or a website chatbot).

Conclusion

This n8n workflow enables a fully functional pizza ordering chatbot using OpenAI's GPT-3.5. Customers can view menus, place orders, and track their order status efficiently. You can further customize the chatbot by refining prompts, adding new features, or integrating with external databases for order management.

🚀 Happy automating!

n8n Pizza Ordering Chatbot with GPT-3.5

This n8n workflow demonstrates how to create a conversational AI agent for a pizza ordering chatbot using GPT-3.5. It leverages LangChain nodes to manage chat interactions, memory, and provide tools for calculations and HTTP requests, simulating a real-world ordering system.

The workflow allows users to interact with a chatbot that can understand their pizza orders, answer questions, and potentially integrate with external services (like a menu API or order status checker).

What it does

This workflow sets up a sophisticated AI agent with the following capabilities:

  1. Listens for Chat Messages: The Chat Trigger node initiates the workflow whenever a new chat message is received, acting as the entry point for user interaction.
  2. Manages Conversation History: The Simple Memory (Buffer Window Memory) node keeps track of the conversation history, allowing the AI agent to remember previous interactions and maintain context throughout the chat.
  3. Processes User Input with an AI Agent: The AI Agent node, powered by a OpenAI Chat Model (GPT-3.5), is the core of the chatbot. It interprets user messages, decides on the appropriate action, and utilizes available tools.
  4. Provides Calculation Capabilities: The Calculator tool allows the AI agent to perform mathematical operations, which could be useful for calculating order totals, discounts, or other numerical queries.
  5. Enables External API Calls: The HTTP Request Tool empowers the AI agent to make HTTP requests to external services. This is crucial for a pizza ordering bot, as it could be used to:
    • Fetch menu items and prices from a database or API.
    • Submit new orders to an order management system.
    • Check the status of an existing order.
    • Retrieve customer information.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • OpenAI API Key: An API key for OpenAI to use the GPT-3.5 chat model. This needs to be configured as an n8n credential.
  • LangChain Nodes: Ensure the @n8n/n8n-nodes-langchain package is installed and enabled in your n8n instance.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • OpenAI Chat Model: Create an n8n credential for OpenAI and link it to the OpenAI Chat Model node.
  3. Customize Tools (Optional but Recommended):
    • HTTP Request Tool: Modify the HTTP Request Tool to point to your actual pizza menu API, order submission endpoint, or status tracking service. You will need to define the API endpoints, methods (GET/POST), and any required headers or body parameters.
    • Calculator: The Calculator tool is generally ready to use, but you can adjust its description if needed.
  4. Activate the Workflow: Once configured, activate the workflow.
  5. Interact with the Chatbot: Use the Chat Trigger to send messages to the bot (e.g., via a test chat interface or by integrating with a messaging platform like Telegram, Slack, etc., which would require additional trigger nodes).

This workflow provides a robust foundation for building an interactive and intelligent pizza ordering chatbot. By extending the HTTP Request Tool and potentially adding more specialized tools, you can create a fully functional and integrated ordering experience.

Related Templates

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.

gotoHumanBy gotoHuman
353

Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution

AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) 🧠 AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative — all powered by AI logic, sir. --- 💡 Key Advantages ⚡ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. 🧠 AI Qualification Engine An OpenAI-powered Agent evaluates the lead’s industry, region, and needs to generate a persona summary and routing rationale. 📊 Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. 💬 Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. 🔁 Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- ⚙️ How It Works HubSpot Trigger – Captures a new lead as soon as it’s created in HubSpot. Fetch Contact Data – Retrieves all relevant fields like name, company, and industry. Clean & Format Data – A Code node standardizes and structures the data for consistency. Airtable Record Creation – Logs the lead data into the “Leads” table for centralized tracking. AI Agent Qualification – The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update – Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification – Sends a real-time message tagging the rep with lead info. Gmail Notification – Sends a personalized handoff email with context and follow-up actions. HubSpot Sync – Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- 🛠️ Setup Steps Trigger Node: HubSpot → Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the “Leads” table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- 🔐 Credentials Required HubSpot OAuth2 API – To fetch and update leads. Airtable Personal Access Token – To store and update lead data. OpenAI API – To power the AI qualification and matching logic. Slack OAuth2 – For sending team notifications. Gmail OAuth2 – For automatic email alerts to assigned reps, sir. --- 👤 Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- 💬 Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular — perfect for scaling across global sales teams, sir.

MANISH KUMARBy MANISH KUMAR
113