How to read this reference
Gating values: Always on (every member, cannot be disabled) · Write toggle (on/off per tool; member must also pass the write-access level) · Admin-only · Integration (configured + toggle on; some are Limited release) · Platform (managed by Thread).
Tickets
Scheduling
Bounds for mass operations: chained requests run up to ~30 agent steps per message, and
search_tickets returns up to 100 tickets per call (20 by default; up to 10 when full message threads are included). Batch bigger jobs in chunks.What
search_tickets reads from a ticket’s thread: when search_ticket_notes is true, keyword matching and returned message text cover the last 10 client and technician messages on the ticket. It does not read internal notes (staff-only notes, including the internal notes written by log_time_entry) and it does not read PSA time-entry records. Super Magic has no read tool for time entries — log_time_entry writes them but nothing surfaces the existing entries back. If you need time-entry data (including internal time notes), pull it from your PSA directly.Search & lookups
IT Glue write (where enabled):
push_knowledge_to_itglue (Write) exports a resolved-ticket knowledge article into IT Glue. It only appears where IT Glue is connected, its Super Magic access is on, and IT Glue export is enabled for the workspace — so most workspaces see IT Glue as read-only search only.Intents — admin-only
Flows — admin-only
NinjaOne — integration (Limited release)
Requires: NinjaOne configured by an admin and the member signed in with their own NinjaOne account. Tools act with that member’s NinjaOne permissions.TimeZest — integration
Liongard — integration (Limited release)
Liongard tools are fetched dynamically from your Liongard instance, so the exact list depends on what Liongard exposes (environments, systems, metrics, alerts, detections, timelines, reports). All Liongard tools are reads. Liongard is also offered as a per-member connector.ImmyBot — integration (Limited release)
Requires: ImmyBot configured by an admin and its Super Magic access toggled on. ImmyBot is workspace-level — there is no per-member sign-in; every member sees the same ImmyBot context.Dispatch (where enabled)
See Super Magic and Integrations updates in the changelog.