Skip to main content- What Are Automations?An automation is a managed AI agent that works inside your MSP stack. You give it a job description (a system prompt), a specific set of tools it may use, and a trigger that tells it when to run.…
- Automation AvailabilityAutomations are generally available and enabled by default for current StackJack tenants. New tenant records also default to enabled. You do not need to request enrollment or turn on a tenant-side…
- The Automations PageThe Automations page is the single home for the whole feature. A rail on the left switches between five sections:
- Creating an Automation with the Guided WizardThe guided wizard is a chat: you describe what you want to automate in plain language, and an AI interviewer asks clarifying questions until it has everything needed to build the automation for you.…
- Creating an Automation with the Advanced BuilderThe advanced builder is the single place you both create and edit an automation. It gives you full control over every part — identity and model, trigger, knowledge, capabilities, and guardrails — with…
- Using Automation TemplatesTemplates are ready-made automations you can install in seconds — the fastest way to see a real run. StackJack ships a set of curated templates, and your team (or the wider community, once published…
- Publishing Your Own TemplatesA template is a reusable automation — for your own use, to share with your team, or for the community marketplace (after a StackJack review). You can build one two ways: start from scratch, or save an…
- The Automation Detail PageEvery automation (a managed AI agent that runs on your behalf) has its own detail page — the hub where you run it, monitor it, repair it, and jump to every related tool. Open it by clicking an…
- Editing an AutomationYou edit an automation in the Advanced Builder — the same surface you use to create one. It is the single place to change everything about an existing automation: its identity, instructions, model,…
- How to set up on-demand and scheduled triggersA trigger decides when an automation runs. Every automation has exactly one trigger type, chosen in the Trigger section of the Advanced Builder — the one place automations are created and edited (the…
- How to set up webhook triggersA webhook-triggered automation runs whenever an external system sends an HTTP POST to the automation's unique URL. This is how you wire PSA/RMM alerts, monitoring tools, or automation platforms…
- Run HistoryEvery execution of an automation is recorded as a run. The run history page lists an automation's most recent runs so you can see at a glance what ran, when, with what outcome, and what it cost.
- Run Detail: Live Stream, Interrupt, and TranscriptsThe run detail page is the forensic view of a single run — and, while the run is still going, your live control panel. You land here automatically when you click Run now on an automation, or open any…
- Knowledge SourcesKnowledge sources give an automation durable facts it should know on every run — brand guidelines, escalation policies, SLA thresholds, product references. Knowledge is merged into the automation's…
- Automation Failure NotificationsStackJack can email you when one of your automations ends badly, so you don't have to watch Run History continuously. You turn notifications on per automation and choose the address that receives…
- Automation Version History and RollbackEvery automation keeps an immutable, partial version history of its execution configuration. Creating an automation and each configuration save normally records a version snapshot, and every run…
- Knowledge File UploadsYou can upload documents directly as knowledge sources, so an automation can reference runbooks, exported reports, or policy files without you pasting their contents by hand. Uploads are extracted to…
- Execution Identity and CredentialsAn automation needs two independent permissions before a connector call can succeed:
- Concurrency, Slots, and the Run QueueYour organization has a ceiling on how many automation runs can be going at once. When you hit it, work waits in a durable queue instead of being thrown away. This page covers where the ceiling comes…
- Automation memoryMemory lets an automation keep durable notes between runs. With it off, every run starts from the same system prompt, knowledge sources, and trigger payload, and remembers nothing from the run before.…
- Building and Maintaining Automations from Your AI AssistantThere are three ways to build an automation in StackJack: the advanced builder in the portal, the chat assistant, and your own connected AI assistant through StackJack's MCP tools. They now build and…
- Running automations on your Azure FoundryAn automation can run its model calls on Anthropic through StackJack (the default: your own Anthropic key if you added one, otherwise StackJack credits) or on a model deployed in your organization's…
- Deleting Run TranscriptsEvery automation run keeps a transcript: the conversation with the AI, the run's input, its final answer, and the inputs the automation sent to each tool. You can delete transcripts for one run, for…