Have Claude build an action card
In short: An action card is how a plugin action is displayed in aishaa: what the action does, with which data, and what status it is in. You do not build such a card in aishaa itself: you design it together with Claude through the aishaa MCP connection. Claude writes the card, shows it in every status, and only publishes it once you approve. After that, you manage the card in the View library.
Where to find this
The design work happens in Claude, not in aishaa. First connect aishaa to Claude as a connector; see Connect aishaa to Claude or ChatGPT (MCP). Then ask Claude for an action card in plain language.
The result appears in aishaa under Organisation > View library, with the chip Action card. For a new version, you ask Claude again.
Who: from the Organisation admin role. The card applies to the organisation Claude creates it for. If you have access to several organisations, mention in your request which organisation it is for.
You need at least one integration with an action. See Set up an integration.
What an action card is for
As soon as there is a plugin action on a ticket, whether an agent suggested it, a workflow prepared it, it was started from a view or a colleague created it, aishaa shows it as a card. Without a card of your own, aishaa uses a standard display with the action’s input form. With your own card, you decide what stands out: the amount, the address, the line in question, and what a colleague must check before clicking Execute.
The buttons (Execute, Reject), the input fields and the result of the action are connected automatically; the card does not need to create them itself. How your team reviews proposals is described in To do.
An action card on the Activity tab of a ticket, with the status chip, the Applies to line showing the record, and the Execute and Reject buttons.
Which statuses a card can be shown in
The same card must be right in every phase of an action. Claude can show it in five states:
| Status | What the card shows |
|---|---|
| New action | The form a colleague uses to start the action themselves. A card can replace that form. |
| Pending | The action is waiting for a decision: execute or reject. |
| Executed | The action has been executed, with the result from your system. |
| Failed | Executing the action did not succeed, with the error message. |
| Rejected | A colleague rejected the action, with the reason. |
Look at the card in all five, and at the desktop, tablet and mobile screen widths. A card is only finished when every state is easy to read. If you want to check it against reality, Claude can also show the card with a real action from a ticket.
One card for several actions
An action card does not have to belong to a single action. You can ask Claude for one card that serves several actions of the same plugin, for example “change address” and “add note” for an order. You then publish one card, and it becomes the card for every action it serves, wherever those actions appear.
If an action works on a record, for example an order or a file, the card can also show that record’s data, just as a ticket view does. The card then shows the line Applies to with the record the action concerns.
How it works, step by step
You do not carry out these steps yourself; Claude does. They are listed here so you know what is happening.
- Claude reads the contract first. There is a fixed writing guide for action cards: the statuses, the record an action works on, combining actions and what a card is allowed to do.
- Claude checks which actions are available. For each connected plugin, Claude retrieves which actions exist, what data they ask for, who may execute them and what they return, including sample responses. No customer data is used for this.
- You say what you want to see. Describe in plain language what should be on the card and what a colleague should pay attention to.
- Claude saves a draft. The draft appears in the view library straight away with the chip Draft. Nothing changes yet in what your team sees.
- You review the card in every status and screen width. Claude shows the card for each state; you get a link to the card’s detail page in aishaa, where you can also view it per status yourself.
- Adjust until it is right. Say what needs to change. Claude writes a new version of the draft.
- Publish. Claude only publishes the card once you approve. It then becomes the card for every action it serves, wherever those actions appear.
Which role you need
You need at least the Organisation admin role. With a lower role, the view functions in the connection are not available.
If another organisation in the same account uses the version you want to replace, that is an account decision. Publishing then only works with the Account admin role. Claude tells you when this is the case.
What you do yourself in the view library afterwards
Designing and adjusting happens through Claude; you manage the card in aishaa, under Organisation > View library:
- choose the card for its action with Use for this action, or release the choice with Automatic fallback, and as an Account admin for all organisations in the account;
- Change name and description, without affecting the design;
- Archive view and Restore from archive;
- Delete draft if you no longer want a draft;
- view the Version history and go back to an earlier version with Restore this version;
- lock the card once it has been checked and is correct.
See View library.
Good to know
- Each action has one card per organisation. If you do not choose one, aishaa chooses one automatically: the chip Active · automatic in the view library. A card from your own account takes precedence over a card supplied by aishaa, and the most recent publication takes precedence.
- An action card does not change who may execute or approve the action. You set that for the integration with Minimum role. See Plugin settings: customer data, catalogues and actions.
- Nothing is executed in your system while designing and reviewing. The examples show what the card looks like, not a real execution.
- Publishing never happens automatically. Claude only publishes after you have said it is right.
- Every publication is a new version. Earlier versions are kept in the Version history on the detail page in the view library.
- Once a card is locked, nobody can change it, not even aishaa or the assistant, until an Account admin unlocks it in the app.