API, webhooks and Zapier: what is and is not available
In short: aishaa currently has no public API, no webhooks and no integration with Zapier or similar automation services. So you cannot create or read tickets yourself with an API key, and aishaa does not send messages to your systems when something happens. What is available: an MCP connection for AI assistants, workflows for automations within aishaa, an import key for importing email history, plugins for your webshop or own system, and email as an entry point that works with almost any system.
Where to find this
There is no page in aishaa for API keys, webhooks or external automations. This article answers that question and points you to what is available.
Who: from the Organisation admin role, because the alternatives (plugins, email settings) are managed at that level. Everyone from the Viewer role can use the MCP connection.
What is not available
| Looking for | Status in aishaa |
|---|---|
| Public REST API with an API key | Does not exist. You cannot create, change or retrieve tickets, contacts or messages through an API. |
| Webhooks (aishaa sends a message to your system when an event occurs) | Do not exist. There is no screen to set a webhook address. |
| Zapier, Make or similar services | Do not exist. aishaa has no integration with these services, and without an API or webhooks you cannot build one yourself either. |
| Slack or Teams notifications | Do not exist. Notifications arrive as push notifications, in aishaa itself or by email; see Notifications. |
Do you need a connection that does not exist here? Contact the aishaa team via the aishaa support chat in aishaa (menu Chat, conversation aishaa support) or via support@aishaa.nl.
What is available
Five options cover most of the needs behind a request for an API or Zapier.
MCP connection for AI assistants
With the MCP connection you connect Claude, ChatGPT or another AI assistant to aishaa. You sign in with your aishaa account and then ask questions in plain language about tickets, customers, figures and what aishaa knows. For the Viewer, Agent and Team lead roles the connection is read-only. Admins can also use it to give aishaa instructions, review proposals and have workflows designed as drafts. See Connect aishaa to Claude or ChatGPT (MCP).
Workflows within aishaa
If you want something to happen automatically when something comes in or changes, you create a workflow: “when this happens, do that”. A workflow can, for example, send a message to the customer, ask a colleague something, set a label, forward a message by email, or fetch or do something in your system via a plugin. A workflow cannot call an arbitrary web address; you only reach an external system via a plugin or by email. See What are workflows.
Import key for email history
There is an import key for importing existing emails from a Gmail mailbox with a Google script. The key only works for supplying email history; you cannot retrieve or create anything else with it. You get the key from the aishaa team. See Import email history.
Plugins
Data from your webshop, warehouse system, purchasing system or case system comes into aishaa through an integration. Every integration is built and hosted by aishaa, including one for a system that only you use, and it can offer actions your team carries out from a ticket as well as data. Which integrations are available to you is shown on Organisation > Plugins; see Plugins: overview of the integrations and Set up an integration. An integration is the way to connect a system to aishaa; building your own API connection is not possible.
Email as a universal entry point
Every organisation has its own aishaa Mail address. Everything that arrives at that address becomes a ticket. So if your system (website, contact form, till system, monitoring tool) can send email, it can create tickets in aishaa without an API. See Your aishaa Mail address and forwarding. For emails from a contact form, aishaa takes the customer’s real address from the message text; see Contact form senders.
Good to know
- aishaa handles the connections with WhatsApp, telephony, Gmail, Outlook and the systems behind the plugins on its side. You cannot use those connections yourself for other purposes.
- There is no export button for all tickets or contacts as a file. For overviews and figures, use the reports in aishaa or the MCP connection.
- The MCP connection does not use an API key; you sign in with your aishaa account and the connection works with your permissions.
- If a public API or webhook support becomes available in the future, you will read about it in this documentation.