# Chatbase + Make: Draft Support Replies from Your Agent > Use Make's Chatbase app to answer support emails from your own help docs, saved as Gmail drafts for a person to check. A how-to guide based on the docs. Source: https://learn.ynteractive.com/content/blog/chatbase-make-draft-support-replies · Updated 2026-10-20 · Free from Stepthrough (https://learn.ynteractive.com) Quick answer To answer support emails with your Chatbase agent in Make, build a scenario with three modules: **Gmail: Watch Emails** to catch new questions, **Chatbase: Send a Message** to ask your agent, and a [Gmail draft](https://learn.ynteractive.com/content/glossary/gmail-draft) step to save its answer for a person to review. The agent answers from the same help docs it already uses on your website, so email and chat give the same answers. You can build and train the agent free in the [Chatbase: Answer Customer FAQs with an AI Agent](https://learn.ynteractive.com/content/chatbase-ai-agent-answer-customer-faqs) lesson, and practice an AI step in Make in [Add AI to Make: ChatGPT Writes a Personal Reply](https://learn.ynteractive.com/content/make-com-chatgpt-gmail-personalized-reply). Last updated October 20, 2026 [Take the free module →](https://learn.ynteractive.com/courses/ai-apps-worth-knowing/36)Module 36 of the free [AI Apps Worth Knowing](https://learn.ynteractive.com/courses/ai-apps-worth-knowing) course, about 15 minutes. No account needed. By [Robert Breen](https://learn.ynteractive.com/content/about) · Published October 20, 2026 · Updated October 20, 2026 · 5 min read Chatbase · Make · Gmail · Integration guide **This is a guide, not a hands-on lesson.** It explains the idea and lists the setup steps from Make's and Chatbase's own documentation. There's no practice copy to click through here, and Stepthrough hasn't tested every screen on every plan. Screens change, so check the links in Sources if a module looks different. ## What business problem does this solve? Most support questions arrive twice: once in the website chat and again by email. A Chatbase agent trained on your FAQ pages answers the chat ones in seconds. The email ones still wait in a [shared inbox](https://learn.ynteractive.com/content/glossary/shared-inbox) until someone has time to type the same answer again. Take Northgate Payroll Services, a made-up eight-person payroll firm. Its inbox gets about 40 emails a week asking the same things: when payroll runs, how to add an employee, where to find a W-2. The firm's Chatbase agent already answers these on the website from the client handbook. The owner wants the inbox to get the same answers, but checked by a person before anything is sent. A [Make scenario](https://learn.ynteractive.com/content/glossary/make-scenario) gives every new support email a ready-made draft. Staff open the draft, check it, fix anything that's off, and click Send. The firm's estimate is about 3 minutes saved per email, or roughly 2 hours a week, and answers that match the handbook every time. ## What do you need before you start? 1. **A trained Chatbase agent.** If its website answers are good, its email answers will be too. 2. **Your Chatbase API key.** Make's Chatbase guide says to open **Settings** in Chatbase and click **API Keys**. Chatbase's newer docs put keys under **Workspace settings > API keys**. Copy a key, or create one, and keep it private. 3. **A Gmail label for support mail**, for example **Support**, so the scenario only reads support emails, not the whole inbox. 4. **A Make account.** The free plan is enough to try this. Chatbase's API, which Make uses, may need a paid Chatbase plan. Check your plan in Chatbase before you build. ## How do you connect Chatbase to Make, step by step? 1. In Make, click **Create a new scenario**. 2. Click the big plus, search for **Gmail** and choose **Watch Emails**. Connect your Google account and point it at the **Support** label. This is the scenario's [trigger](https://learn.ynteractive.com/content/glossary/trigger). 3. Add a module. Search for **Chatbase** and choose **Send a Message**. 4. Click **Create a connection**, give it a name such as "Northgate Chatbase", paste your API key and save. 5. Choose your agent. In the message field, map the email's subject and body text from the Gmail module, for example: "Customer question: {subject}. {text content}". 6. Add a third module: **Gmail: Create a Draft**. Set **To** to the sender's address from module 1, the subject to "Re: {subject}", and the content to the reply text from the Chatbase module. 7. Click **Run once**, send a test email to the Support label from another account, and check that a draft appears with a sensible answer. 8. Save the scenario and turn it on. Gmail's Watch Emails module checks on a schedule you set, for example every 15 minutes. Each module run uses Make operations, and every new email uses three: one per module. Check how many your plan includes per month. ## What can the Chatbase Make app do? Make's Chatbase app is verified and maintained by Chatbase. It has two modules and no triggers: | Module | What it does | | --- | --- | | Send a Message | Sends text to your agent and returns its reply | | Make an API Call | Calls any Chatbase API endpoint with your saved connection | The app has no trigger, so a Chatbase event can't start a Make scenario. Something else starts it: an email, a form, a new row or a [webhook](https://learn.ynteractive.com/content/glossary/webhook). To send new chatbot leads somewhere automatically, use Zapier's **Form Submission** trigger instead. See [Chatbase + Zapier: Send Chatbot Leads to Google Sheets](https://learn.ynteractive.com/content/blog/chatbase-zapier-leads-to-google-sheets). ## Why save a draft instead of sending the reply? Because the agent can be wrong, and a wrong email to a client is worse than a slow one. A draft keeps a person in charge: they read it, correct it and send it. Stepthrough lessons use the same rule for every AI reply. In practice: - **Start with drafts for a month.** Note which questions the agent gets wrong, and add those answers to its sources in Chatbase. - **Never auto-send anything about money, deadlines or legal matters.** A Make filter can route emails with words like "refund" or "late" to a person with no draft at all. [Filters and Routers in Make](https://learn.ynteractive.com/content/make-com-router-and-filters) shows how, hands-on. - **Keep personal data out of the prompt where you can.** Send the question, not the client's whole history. ## What usually goes wrong? - **The scenario reads the whole inbox.** Set the Gmail module to a label or a search filter, not "All mail". - **The answer quotes the email signature.** Map the email's plain-text body, not the full HTML, and trim long threads. - **Drafts land in the wrong account.** The Gmail connection in module 3 must be the shared support inbox, not a personal one. - **Operations run out.** A busy label can use many operations. Raise the check interval, or filter out newsletters first. ## Key takeaways - Make's Chatbase app has a **Send a Message** module and a **Make an API Call** module, but no triggers. - A **Gmail: Watch Emails > Chatbase: Send a Message > Gmail: Create a Draft** scenario answers support email from your own docs. - Connect with a Chatbase API key. Make's guide says it's under **Settings > API Keys**, and Chatbase's own docs say **Workspace settings > API keys**. - Save drafts, not sent emails, and keep a person reviewing every reply. - To react to new chatbot leads, use Chatbase's Zapier trigger, because the Make app can't start a scenario. ## Frequently asked questions **Does Chatbase have a Make trigger for new leads?** No. The Make app has only Send a Message and Make an API Call. For leads, use the Chatbase app on Zapier, whose Form Submission trigger fires for each new lead. **Can the scenario send replies automatically?** It can, by using Gmail's send module instead of a draft. Stepthrough recommends drafts, so a person checks every answer before a client sees it. **How much does this cost to run?** Make counts operations, about three per email here. Chatbase counts message credits for each Send a Message call. Both have plan limits, so check your usage after the first week. **Where can I learn Make from scratch?** Start with [Your First Make Scenario](https://learn.ynteractive.com/content/make-com-google-forms-to-google-sheets), or take the whole free [Make & Zapier Jump Start](https://learn.ynteractive.com/courses/make-zapier-jump-start) course. ## Sources - [Make: Chatbase app documentation](https://apps.make.com/chatbase) - [Make: Chatbase integrations](https://www.make.com/en/integrations/chatbase) - [Chatbase: API keys and integrations docs](https://www.chatbase.co/docs/user-guides/integrations/zapier) - [Chatbase in the Stepthrough AI tools directory](https://learn.ynteractive.com/content/ai-tools/customer-support-chatbots#tool-chatbase) ## Build it yourself, free **Chatbase: Answer Customer FAQs with an AI Agent**. A business case for a small firm that answers the same customer questions every week: build a Chatbase AI agent on your FAQ in the real app, make it say when it does not know, test it, get the chat… You do every step yourself in a practice copy of Chatbase, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts. [Start the free lesson](https://learn.ynteractive.com/modules/chatbase-faq-support-agent) [Or read the full step-by-step guide](https://learn.ynteractive.com/content/chatbase-ai-agent-answer-customer-faqs) ## Free lessons in this post - [Chatbase: Answer Customer FAQs with an AI Agent](https://learn.ynteractive.com/content/chatbase-ai-agent-answer-customer-faqs): A business case for a small firm that answers the same customer questions every week: build a Chatbase AI agent on your FAQ in the real app, make it say when it does… - [Add AI to Make.com: ChatGPT Writes a Personal Reply, Gmail Sends It](https://learn.ynteractive.com/content/make-com-chatgpt-gmail-personalized-reply): Connect OpenAI to your Make scenario, have ChatGPT write a personal reply from each patient's form answers, add the sender's real Signatoro signature, and send it with… - [Your First Make.com Scenario: Google Forms to Google Sheets](https://learn.ynteractive.com/content/make-com-google-forms-to-google-sheets): Build your first Make.com scenario: every new Google Forms response becomes a new row in Google Sheets. Trigger, connection, mapping, Run once and a schedule. ## Watch it in a free lesson: Gmail AI Triage: Auto-Label Every Email and Draft Replies ### Gmail AI Triage: Auto-Label Every Email and Draft Replies: video walkthrough Full walkthrough · 2:31 · with captions Build an n8n workflow that reads each new email, sorts it as a lead, a client or an invoice with a Text Classifier, adds the matching Gmail label, and drafts a reply to clients for you to check. The whole lesson narrated step by step, recorded in Stepthrough’s simulated practice environment. [Watch it with chapters and the full transcript](https://learn.ynteractive.com/content/gmail-ai-triage-labels-drafts-n8n#watch) From the free lesson [Gmail AI Triage: Auto-Label Every Email and Draft Replies](https://learn.ynteractive.com/content/gmail-ai-triage-labels-drafts-n8n) ## Related terms Plain-English definitions, each with an example from a free lesson. [Gmail draft](https://learn.ynteractive.com/content/glossary/gmail-draft) · [Shared inbox](https://learn.ynteractive.com/content/glossary/shared-inbox) · [Scenario (Make)](https://learn.ynteractive.com/content/glossary/make-scenario) · [Bundle (Make)](https://learn.ynteractive.com/content/glossary/make-bundle) · [Chatbot fallback response](https://learn.ynteractive.com/content/glossary/chatbot-fallback-response) · [Credits (Make)](https://learn.ynteractive.com/content/glossary/make-credits) · [Edge case](https://learn.ynteractive.com/content/glossary/edge-case) · [Error handler (Make)](https://learn.ynteractive.com/content/glossary/make-error-handler) [The full AI glossary](https://learn.ynteractive.com/content/glossary) ## Keep reading - [Chatbase + Zapier: Send Chatbot Leads to Google Sheets](https://learn.ynteractive.com/content/blog/chatbase-zapier-leads-to-google-sheets): Connect Chatbase to Zapier so every lead your website chatbot collects lands in a Google Sheet with a Slack alert. A how-to guide based on the docs. - [Docparser + Make: Invoice Data into Google Sheets](https://learn.ynteractive.com/content/blog/docparser-make-invoices-to-google-sheets): Connect Docparser to Make so every parsed invoice becomes a row in Google Sheets: vendor, number, date and total, with no typing. A how-to guide. - [tawk.to + Make: Track New Support Tickets in a Sheet](https://learn.ynteractive.com/content/blog/tawk-to-make-new-tickets-to-google-sheets): Connect tawk.to to Make with a webhook so every new ticket becomes a row in Google Sheets with an owner and a status. A how-to guide based on the docs. [All blog posts](https://learn.ynteractive.com/content/blog) · [All free tutorials](https://learn.ynteractive.com/content)