Integrations
Connecting plugins, deciding yourself what a plugin offers, views, catalogues and the connection with Claude or ChatGPT.
-
Plugins: overview of the integrations
What an integration in aishaa is, what the Plugins page looks like with a card per integration and the Connected chip, and what an integration gives you: records on the ticket, actions your team or the AI can carry out, and catalogues aishaa can search.
Organisation admin -
Set up an integration
How to create a connection with one of your systems on the plugin page: choose the card, set the availability and the connection method, fill in the details of the system, test the connection and save or sign in to the system, and then manage, reconnect or disconnect the connected accounts.
Organisation admin -
Plugin settings: customer data, catalogues and actions
Under every integration on the plugin page there are three setting blocks: under Customer records you choose when the integration looks up the customer, under Catalogues whether an agent may search them, and under Actions from which role each action may be run. What the AI may do with an integration is set in the skills of an agent.
Organisation admin -
View library
In the view library you manage your organisation's ticket views and action cards: open them, show them as a ticket tab or use them for an action, change the name and description, archive, restore earlier versions and lock a view. Designing and editing happens through the Claude connection.
Organisation admin -
Decide for yourself what a plugin offers (own wiring)
For some plugins you decide yourself which records aishaa shows on a ticket and which actions the plugin offers, with your own wiring for your organisation or your whole account. You write the wiring or have your AI assistant write it, aishaa tests it on a real customer before it is saved, and you can always go back to the standard.
Organisation admin -
Have Claude build a ticket view
A ticket view is an extra tab next to the ticket with data from a connected system. You have it designed by Claude through the aishaa MCP connection: Claude reads the contract and the available data sources, saves a draft, gives you a preview link, and only publishes once you approve.
Organisation admin -
Have Claude build an action card
An action card is how a plugin action is displayed on the ticket. You have it designed by Claude through the aishaa MCP connection: Claude reads the contract and the available actions, saves a draft, shows the card in every status, and only publishes once you approve.
Organisation admin -
Connect aishaa to Claude or ChatGPT (MCP)
Connect aishaa as an MCP connector to Claude, ChatGPT or another AI assistant and ask questions in plain language about your tickets, customers, figures, internal chats, documentation and what aishaa knows; admins can use the same connection to view the configuration and make proposals, have workflows designed as drafts, have ticket views and action cards built, save a plugin's own wiring, lock configuration and manage WhatsApp templates.
Viewer -
API, webhooks and Zapier: what is and is not available
aishaa has no public API, no webhooks and no Zapier integration. Read what is available: the MCP connection for AI assistants, workflows within aishaa, the import key for email history, plugins for your webshop or own system, and email as a universal entry point.
Organisation admin -
Catalogues of a connection
A catalogue is a searchable collection of records that a connected system offers and that aishaa keeps up to date. For each catalogue you choose whether an agent may search it, you start a sync and you see the status, the number of records and the date.
Organisation admin -
Messages from marketplaces
Messages from buyers on eBay and bol.com arrive through the marketplace. A reply to an eBay ticket is sent as a message in eBay instead of as an email, and messages from bol.com are kept apart per case and order number so that buyers' details never get mixed up.
Agent
