Magic LibraryThe course
Work these in order — each ends with a link to the next. Start where your leverage is highest today; most automation engineers begin in Flows and Intents before reaching for the API.1
Flows, status automations, and Triage Agent intents
Route and update tickets without a human, then teach the Triage Agent what to resolve on its own. Start here →
2
Thread MCP, the tool reference, and the API
Put the desk inside your own AI client, then drive Thread over webhooks, APIs, and Rewst. Read →
3
Build with Super Magic
Add external tools with connectors, author reusable Skill Library skills, and ship Automagically runbooks. Read →
Your starter kit
The Skill Library has a whole Automation & Flows category built for your role. Start with these — then press⌘K and search for any building block (“intent”, “flow”, “webhook”) to find the rest.
Flow Builder
Design a Flow from a plain-language description of the routing you want.
Intent Builder
Draft a Triage Agent intent — variations, arguments, and replies — from scratch.
Flow Debugger
Work out why a Flow didn’t fire, then fix the condition.
Automation Opportunity Finder
Mine your ticket history for the repetitive work worth automating next.
Skill Authoring Coach
Turn a working prompt into a clean, reusable Super Magic skill.
Notion Runbook Database
Wire a Notion runbook database into Super Magic through a connector.
Your build ritual
Automation is a loop, not a launch. Run it weekly: measure, build, verify.- Measure. Run Automation Opportunity Finder against last week’s tickets — where did humans do the same thing more than five times?
- Build. Ship the smallest automation that removes it: a status automation, a Flow, an Intent, or a Super Magic skill. One change at a time.
- Verify. Watch it for a few days. Use Flow Debugger and Automation Failure Watch to catch anything that fired wrong before your team does.
Pro tips & FAQ
Flows didn't fire — where do I start?
Flows didn't fire — where do I start?
Flows evaluate when a thread is updated (reply, note, status change, board change) after the flow exists. Add an internal note to nudge a thread through, confirm the condition actually matches, and remember webhooks are near-real-time but not 100% guaranteed. Flow Debugger walks the rest.
When do I reach for an Intent vs. a Flow?
When do I reach for an Intent vs. a Flow?
A Flow routes and updates tickets on defined conditions — no AI judgment. An Intent teaches the Triage Agent to handle a request type conversationally and resolve it unattended. Rule of thumb: deterministic routing → Flow; “understand and respond to this kind of ask” → Intent.
What's the difference between a Super Magic skill and a Super Magic Agent?
What's the difference between a Super Magic skill and a Super Magic Agent?
A skill is a saved prompt-first workflow a person runs in Super Magic. A Super Magic Agent is that same skill fired automatically by a Flow — Super Magic + Flows — so the workflow runs with no one in the composer. Author the skill first, prove it by hand, then wire the Flow.
Why is a tool missing from Super Magic and Thread MCP?
Why is a tool missing from Super Magic and Thread MCP?
Thread MCP exposes the same tool layer as Super Magic, so the same gating applies: write actions are controlled by your admin, intents and flows are admin-only, integration tools appear only once connected, and some connectors (NinjaOne, Linear, Notion, Zapier) need your own sign-in first. See the Super Magic admin guide.
Do I need code to automate Thread?
Do I need code to automate Thread?
No. Flows, Intents, status automations, and Super Magic skills are all built in-app with no code. Reach for the API and webhooks or Rewst only when automation has to reach outside Thread.