Aidbase
Helpdesk & ITSMConnect AI agents to Aidbase, the AI support platform for SaaS startups. Agents query chatbots, add knowledge sources such as crawled sites, transcripts, and uploaded documents, set ticket status and priority, and poll connected email inboxes.
What This Integration Enables
Aidbase is not a ticketing tool with an assistant bolted on. Its centre of gravity is the knowledge layer, and the connector reflects that: a knowledge item is created from a crawled website, a transcribed YouTube video, an uploaded PDF or Word file, or a hand built FAQ collection, and that single item can then be attached to a chatbot, a ticket form, and an email inbox at once. Agents create knowledge, attach and detach it across those three surfaces, trigger indexing with Train Knowledge Item, and interrogate the result with Ask Chatbot before anyone else sees it. That last capability is the interesting one, because it lets an agent test what the assistant will say about a change while the change is still reversible.
On the support side the connector reads and works tickets submitted through Aidbase ticket forms and emails landing in connected inboxes, posting replies with Reply to Ticket and Reply to Email, adjusting state with Update Ticket and Update Email, and shutting down abuse with Block Ticket, Block Chatbot Chat, and Block Email Sender. Two boundaries are worth stating plainly rather than glossing. Update Ticket changes status and priority only, so this connector does not assign or route tickets to agents; routing stays inside Aidbase. And the knowledge objects are crawled and uploaded sources, not published help centre articles, so an agent grows what the assistant knows rather than authoring what customers read.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Documentation change that reaches the assistant on purpose
A product team ships a pricing change and edits three documentation pages. A scheduled agent adds each updated page with Create Website Knowledge, then runs Get Knowledge Sub-Pages to confirm the crawl picked up the sections that actually changed. Before training anything, it walks List Chatbot Knowledge, List Ticket Form Knowledge, and List Email Inbox Knowledge so it can state exactly which assistant surfaces the update will alter. It then runs Ask Chatbot against the live bot with the five questions the old pricing page answered, captures the current replies, and posts the whole package to the support lead: the changed sources, the surfaces affected, and what the bot says today. Training is held until the lead says go.
FAQ collection assembled from resolved tickets
Support closes a cluster of tickets about the same onboarding failure. An agent runs List Tickets filtered to Resolved over the last two weeks and Get Ticket to pull the full conversation history on each, uses a language model to draft a question and answer pair from the resolution, and writes them with Create FAQ Knowledge and Add FAQ Item. The draft collection sits untrained and unattached, so it changes nothing yet. A support engineer reviews the entries in Aidbase, and only then does the agent run Train Knowledge Item and Attach Knowledge to Ticket Form so the next person hitting the same failure is deflected before they file.
Escalation with the assistant transcript attached
A customer works through the chatbot, gets nowhere, and files a ticket. An agent picks the ticket up with Get Ticket, finds the matching chatbot conversation with List Chatbot Chats and Get Chatbot Chat, and now has both halves of the story: what the customer asked the bot, what the bot said, and what they wrote when that failed. It raises a linked issue in Jira with the transcript attached, posts the summary into the on call channel in Slack, and uses Update Ticket to raise priority. The engineer who picks it up starts from the assistant's failed answer rather than from a blank ticket, which is usually the fastest route to fixing the knowledge gap behind it.
Human-in-Loop Highlight
The dangerous call on this connector is not a reply to one customer. It is Train Knowledge Item, because a training run changes what the assistant tells every future customer on every surface the item is attached to, silently and all at once, and Delete Knowledge Item goes further: it removes the item from any chatbots, ticket forms, and email inboxes it was attached to and cannot be undone. So the agent never trains or deletes on its own judgement. It stages the change, enumerates the blast radius with List Chatbot Knowledge, List Ticket Form Knowledge, and List Email Inbox Knowledge, runs Ask Chatbot to capture the answers customers get right now, and then pauses in Slack with a concrete question: "Training the updated Billing FAQ will change answers on the Support chatbot, the Contact Us ticket form, and the help@ inbox. Today the bot answers the annual proration question like this. Train it, or hold?" A human decides what the assistant is allowed to start saying. That is the whole point of putting an orchestration layer above an AI support tool rather than trusting it to update itself, and it is why human-in-the-loop belongs on the knowledge write rather than on every individual answer.
Agent Capabilities
42 actionsChatbots
9- List Chatbots Retrieves all chatbots in the connected Aidbase account with their public ID, title, and allowed website domains. Used at the start of any knowledge workflow to establish which assistant surfaces exist before anything is changed.
- Get Chatbot Fetches a single chatbot by its public ID. Used to confirm a chatbot exists and its domain allowlist is what you expect before sending messages or attaching knowledge to it.
- Ask Chatbot Sends a message to a chatbot and returns an AI generated reply grounded in that chatbot's knowledge base. Used to test what the assistant currently says before a knowledge change is approved, and to continue a session by passing the returned session ID.
- List Chatbot Knowledge Lists the knowledge items attached to a chatbot along with their type and training status. Used to establish the blast radius of a proposed training run or deletion.
- Attach Knowledge to Chatbot Attaches an existing knowledge item to a chatbot so the bot can draw on it when answering. Used after a human has approved new content, never before.
- Detach Knowledge from Chatbot Removes the association between a knowledge item and a chatbot without deleting the item. Used to pull a source out of one assistant while leaving it available to forms and inboxes.
- List Chatbot Chats Lists conversations handled by a chatbot, optionally filtered by creation date range. Used to find the sessions that preceded an escalated ticket.
- Get Chatbot Chat Retrieves a single chatbot conversation with its full message history. Used to attach the assistant transcript to an escalation so the engineer sees where the bot went wrong.
- Block Chatbot Chat Blocks a specific chatbot conversation so the user cannot continue interacting in that chat. Used for abuse handling.
Knowledge Base
13- List Knowledge Items Lists all knowledge items in the account, with type and training status, paginated. Used to audit what the assistant is drawing on across the whole account.
- Get Knowledge Item Fetches a single knowledge item by UUID with its type, training status, and source details. Used to check whether an item is mid training before acting on it.
- Get Knowledge Sub-Pages Retrieves the crawled sub-pages of a website type knowledge item. Used to confirm that a re-crawl actually picked up the sections that changed.
- List FAQ Items Lists the question and answer entries inside an FAQ type knowledge item. Used to review a drafted collection before it is trained.
- Create Website Knowledge Adds a website as a knowledge source, which Aidbase crawls into a website type item. Used to keep the assistant aligned with published documentation on a schedule.
- Create Video Knowledge Adds a YouTube video as a knowledge source, which Aidbase transcribes. Used to turn recorded walkthroughs and webinars into answerable content.
- Create Document Knowledge Starts a document upload by creating the item and returning a signed upload URL for a PDF, Word, plain text, or CSV file. Used as the first step of the three step document flow.
- Finalize Document Knowledge Completes a document knowledge item after its bytes have been uploaded to the signed URL. Used to close out the document upload before training.
- Create FAQ Knowledge Creates a new FAQ collection as a knowledge item. Used to build a curated set of answers out of resolved tickets rather than raw source material.
- Add FAQ Item Adds a question and answer entry to an existing FAQ knowledge item, optionally with a source URL and categories. Used to draft answers for human review before training.
- Delete Knowledge Item Permanently deletes a knowledge item and removes it from every chatbot, ticket form, and email inbox it was attached to. This cannot be undone, which is why it sits behind an approval gate.
- Delete FAQ Item Removes a single question and answer entry from an FAQ collection, leaving the rest intact. Used to retract one wrong answer without dismantling the collection.
- Train Knowledge Item Triggers a training session so an item's latest content is indexed and usable by chatbots, forms, and inboxes. Training is asynchronous, so the agent polls the item's training flag to know when the new answers are live.
Ticket Forms and Tickets
10- List Ticket Forms Retrieves all ticket forms with their public ID, title, allowed domains, and configured fields. Used to map intake surfaces before attaching knowledge.
- Get Ticket Form Fetches a single ticket form with its field configuration. Used to understand what a submitter was actually asked before reading their ticket.
- List Ticket Form Knowledge Lists the knowledge items attached to a ticket form. Used to check which sources drive auto resolution on that intake path.
- Attach Knowledge to Ticket Form Attaches a knowledge item to a ticket form so Aidbase can suggest answers and auto resolve submissions. Used after approval to extend deflection to a new intake surface.
- Detach Knowledge from Ticket Form Removes the association between a knowledge item and a ticket form. Used to stop a source influencing auto resolution without deleting it.
- List Tickets Lists tickets submitted through a ticket form, filterable by status and creation date range. Used to build the resolved ticket set that seeds new FAQ content.
- Get Ticket Retrieves a single ticket with its status, priority, timestamps, and full conversation history. Used to pull the resolution language that becomes an FAQ answer.
- Update Ticket Updates a ticket's status and priority, recording the change in its history. This action does not assign or route tickets, so ownership stays with Aidbase's own rules.
- Reply to Ticket Posts a reply to a ticket on behalf of the ticket form owner, optionally as a configured persona. Used to deliver an answer a human has approved.
- Block Ticket Blocks a ticket so the submitter cannot add further messages. Used for abuse handling.
Email Inboxes
10- List Email Inboxes Retrieves all email inboxes with their ID, alias, title, and description. Used to establish which inboxes the assistant drafts against.
- Get Email Inbox Fetches a single inbox by ID or alias. Used to confirm the target before attaching knowledge.
- List Email Inbox Knowledge Lists the knowledge items attached to an email inbox. Used as the third leg of the blast radius check before a training run.
- Attach Knowledge to Email Inbox Attaches an already trained knowledge item to an inbox so Aidbase can draft and suggest replies to incoming mail. Used to extend approved content to email support.
- Detach Knowledge from Email Inbox Removes the association between a knowledge item and an inbox. Used to narrow what the inbox drafts from.
- List Emails Lists emails in an inbox, filterable by status and creation date range. This is the polling path that stands in for event delivery on this connector.
- Get Email Retrieves a single email with its status, priority, timestamps, and full conversation history. Used to read the thread before drafting or escalating.
- Update Email Updates an email's status and priority, recording the change in its history.
- Reply to Email Sends a reply to an email on behalf of the inbox owner. This is customer visible and irreversible once sent.
- Block Email Sender Blocks the sender of a specific email so future mail from that address is not processed by the inbox. --- The Aidbase connector exposes no FlowRunner triggers. Aidbase does not publish a webhook subscription API, so flows that need to react to new tickets, new emails, or newly finished training runs are driven by a schedule that calls List Tickets, List Emails, or Get Knowledge Item and compares against the last run. That is a polling pattern, and it is worth designing around deliberately rather than assuming events will arrive.
Frequently Asked Questions
What can FlowRunner do with Aidbase?
FlowRunner agents can run List Chatbots, Get Chatbot, and Ask Chatbot in Aidbase, plus 39 more actions.
Does connecting Aidbase to FlowRunner require OAuth?
No. Aidbase connects to FlowRunner with an API key, no OAuth flow required.
Can Aidbase trigger a FlowRunner workflow automatically?
Aidbase doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Aidbase
$100 in credits. No card required. Connect in minutes.