My assistant does not use Gunnie.ai
- Check that the connector is switched on in this chat: + → Connectors in Claude.
- Ask about something specific, such as a ticket key, so the assistant sees that Gunnie.ai can help.
- If the connector shows an error, disconnect and connect it again in Settings → Connectors, and log in once more.
Logging in does not work
- Use the email address your admin added; another address has no access.
- An email link stops working after a while; ask for a new one if it no longer works.
- If the login says your account has no access, you were not added or were deactivated; ask your admin.
A call was refused
- Outside the projects, repositories or files allowed: the connection’s allow-list does not include it. An admin can add it on Systems.
- Not a tool for your role: ask your admin whether another role fits your work.
- A system is unreachable or rejects the token: an admin tests the connection on Systems, which says what to fix.
- Every refusal is in the call log with the reason.
Something about approvals
- It expired: ask your assistant again; nothing was written.
- It was approved but not written: the result on the card says why, for example that the ticket already held the text.
- Nothing changed in a demo organisation: that is by design.
A routine did not run
- Check that it is switched on, and that its schedule is in Amsterdam time.
- Its budget, or your organisation’s, may be used up for this month; Routines shows it.
- A status trigger only reacts to tickets that enter the status after you switched it on.
- A run marked Withheld: Gunnie.ai held its result back, so nobody sees it and it does not count as a result. Run it again; if it keeps happening, contact us.
Still stuck?
Ask your assistant to contact Gunnie, which sends us your message after you approve it, or contact us. Found a security problem? See reporting a vulnerability.