Zapier. Your AI agent in 8,000 apps.
The SimplyBoost app for Zapier connects your AI customer support agent to your CRM, helpdesk, Slack, Google Sheets and thousands of other apps: start a Zap when a conversation is handed to your team, a lead comes in or a question goes unanswered, and ask your agent or update its knowledge from any Zap. AI assistants can use the same actions through Zapier MCP.
By Santhul Joseph, AI EngineerUpdated
On this page
Get the SimplyBoost app on Zapier
- 1Open the SimplyBoost invite link while you are signed in to Zapier, and choose Accept Invite & Build a Zap.
- 2In the Zap editor, search for SimplyBoost as the trigger or action app.
The app is in Zapier's review. Until Zapier lists it in its app directory, the invite link is how you add it; your Zaps keep working when it is listed. Triggers and actions work on Zapier's free plan in two-step Zaps. A Zap with more steps, such as a search before an action, needs a paid Zapier plan.
Connect your SimplyBoost account
- 1In SimplyBoost, open Settings → API and create a token. Only the account owner can create tokens; the API is part of the Growth, Pro and Enterprise plans.
- 2Give the token the permissions your Zaps use (see the table below). Triggers need a token that covers all your AI agents.
- 3In Zapier, choose Sign in under Account, paste the token and continue. Zapier shows the connection as your account name and email.
| To use | Token permissions |
|---|---|
| Triggers | webhooks:read, webhooks:write, plus read access for the records they send |
| Ask the AI Agent | conversations:write |
| Add or Update Knowledge Text, Refresh Website Knowledge | knowledge:read, knowledge:write |
| Reply in Conversation, Resolve or Reopen, Find Conversation | conversations:read, conversations:write |
| Update Lead, Find Lead | leads:read, leads:write |
| Choosing an AI agent from a list | chatbots:read |
Which SimplyBoost events can start a Zap?
| Trigger | When it starts the Zap |
|---|---|
| New Escalated Conversation | The AI agent hands a customer conversation to your team and a support ticket opens, for example because the customer asked for a person. Includes the reason, category and urgency when the agent recorded them. |
| New Resolved Conversation | A customer conversation is marked as resolved, by your team, your helpdesk or the API. |
| New Lead | A lead first has an email address or phone number, for example when a customer gives one to the AI agent in a chat. |
| New Unanswered Question | A customer asks a question the AI agent could not answer from its knowledge base (a new entry in Missing answers). |
| Knowledge Source Processed | A knowledge source (a file, website or text) has finished processing, or failed. |
All triggers are instant: SimplyBoost sends a signed event the moment it happens, and the app checks the signature before the Zap runs. Pick one AI agent or leave the field empty for all of them. Test chats from your dashboard are left out unless you switch on Include Test Chats.
What can a Zap do in SimplyBoost?
| Action or search | What it does |
|---|---|
| Ask the AI Agent | Sends a question to your AI agent and returns its answer, the knowledge sources it used and a thread ID to continue the conversation. The agent answers in the language of the question unless it is set to one language. |
| Add or Update Knowledge Text | Adds a text source to the agent's knowledge, or updates the one with the same title. Unchanged text is not processed again. Mark it Source of Truth when it should win over other knowledge, such as a current price list. |
| Refresh Website Knowledge | Reads a website source again now, for example after you publish a page. The current knowledge keeps answering meanwhile. |
| Reply in Conversation | Replies as a person in a conversation that was handed to your team. The customer gets it on the channel they wrote on. |
| Resolve or Reopen Conversation | Marks a conversation as resolved, for example when your helpdesk closes the ticket, or reopens it. |
| Update Lead | Changes a lead's name, email, phone or company, or marks it converted. Empty fields keep their value. |
| Find Conversation (search) | Finds a conversation by its thread ID, with its messages and a ready-to-use transcript for your helpdesk or CRM. |
| Find Lead (search) | Finds a lead by email address among an agent's 500 most recent leads. |
Example Zaps
- Handover to your helpdesk: New Escalated Conversation → Find Conversation → create a ticket with the transcript in Zendesk, Freshdesk or HubSpot.
- Lead to CRM: New Lead → create or update a contact in HubSpot, Pipedrive or Salesforce.
- Close the loop: your helpdesk closes a ticket → Resolve or Reopen Conversation in SimplyBoost.
- Missing answer to an expert: New Unanswered Question → a Slack message to the product specialist, who adds the answer.
- Price lists in step: a new row or file in Google Sheets or Drive → Add or Update Knowledge Text.
- Fresh website knowledge: Schedule by Zapier every week → Refresh Website Knowledge.
- Answer the inbox: a new email or form entry → Ask the AI Agent → send the answer or save it as a draft.
Can AI assistants use SimplyBoost through Zapier?
Yes. Zapier MCP turns the SimplyBoost actions and searches into tools for Claude, ChatGPT, Cursor and other AI assistants. Add SimplyBoost under Apps in your Zapier MCP server, connect your account with an API token, and ask your assistant, for example, what your AI agent answers about a product or whether a customer is already a lead.
Zapier counts two tasks for each tool call. If you only need SimplyBoost, connect your assistant to the SimplyBoost MCP server directly: it has more tools and costs no Zapier tasks.
Limits and good practice
- Each Ask the AI Agent is one message of your monthly allowance, like a chat on your website.
- The API allows 120 requests a minute per token. An account can have 25 webhooks; each Zap with a SimplyBoost trigger uses one while it is on.
- Ask the AI Agent and Reply in Conversation take an Idempotency Key: use the ID of the email or ticket you are answering, and a step that runs again never asks or sends twice.
- Keep one title per document for Add or Update Knowledge Text, for example
Price list 2026 - spare parts.
Everything the app does goes through the public API. See the API reference for the full details, or the n8n guide if you build your workflows in n8n.