Beyond chat: put MSP work on autopilot.
The most powerful no-code automation tool in the industry. Automations are saved, reusable AI workers that run against your connected MSP stack — on demand, on a schedule, or from webhook events — with zero code and zero glue code between systems. Explicit tool scoping, dry-run rollout, and real run history turn recurring work into managed AI workflows your team can actually trust.
The most powerful no-code
automation tool in the industry.
Describe the outcome in plain English. The agent plans and executes it across your entire stack — zero code, zero glue code, zero node-wiring. If you can describe it, you can automate it.
Where workflow builders stop, agents start
Traditional builders make you wire every trigger, node, and field map by hand — then write glue code for the edge cases anyway. Each branch is your problem. Each API change is your breakage. The diagram grows until nobody wants to touch it.
An Automation replaces the diagram with judgment. It reads the goal, plans the steps, and calls the right tools across PSA, RMM, M365, documentation, security, and quoting — no mapping tables, no per-connector plumbing. Ambiguous data, unexpected branches, and messy in-between states are handled by reasoning, not by another node.
That’s how it achieves what no workflow builder could: the cross-system, judgment-heavy work that never fit in boxes and arrows — effectively infinitely powerful, bounded only by the tools you scope to it.
A saved AI worker, not a chat session.
An Automation is a persistent, saved AI worker. Configure it once — prompt, model, trigger, tools, guardrails, knowledge — and it runs repeatedly against your MSP stack. Closer to a managed workflow asset than a disposable AI conversation.
It’s a saved definition
Name, description, model, system prompt, trigger mode, scoped tools, runtime caps, and optional reusable knowledge — all versioned on every save.
It runs on its own schedule
Fire it on demand, on a cron schedule with timezone support, or from webhook payloads. Each run is tracked with a full execution record.
It’s bounded by design
Explicit tool allow-list, per-agent max runtime, per-run credit cap, dry-run mode, and server-side tenant validation — no implicit trust surface.
Every run is visible
Status, summary, token counts, tool-call count, credits consumed, duration, trigger payload, and full transcript — all retrievable after the fact.
From one-off chat to managed automation.
StackJack already gives your AI clients scoped MCP access to your MSP stack. Automations add the missing layer — triggers, guardrails, credits, and a run record — that turns a single tool call into a repeatable workflow.
From authoring to execution.
Every Automation moves through two phases: author & deploy, then execute & record. Both phases are inspectable end-to-end.
Author & deploy
Execute & record
MaxCreditsPerRun before long-running work begins. BYOK tenants skip this.Three ways to fire an agent.
Each mode is a real system, not a checkbox. Pick per agent based on how you want the workflow to run.
When to use it
- Operator-initiated triage or investigation
- One-click reporting at the moment you need it
- Ad-hoc “pull context” requests
- Testing a new agent before promoting out of dry-run
When to use it
- Daily ticket review, weekly briefings, nightly hygiene
- Recurring drift, backlog, or audit checks
- Anything where “always at 7am” matters
Timezone-aware cron. Startup reconciliation re-registers expected jobs after deploys. Silent skip if the tenant becomes ineligible — no double-billing.
When to use it
- Event-driven follow-up (new ticket, alert, PagerDuty)
- Kicking off context gathering right when something happens
- Bridging external systems into MSP workflows
Per-agent webhook secret, configurable payload modes (none / full / selected fields), payload size cap, and 10 hits/minute per-agent rate limit.
| On-demand | Scheduled | Webhook | |
|---|---|---|---|
| Fires from | Portal or API | Timezone-aware cron | Signed HTTP POST |
| Input payload | Operator context | None (instructions in prompt) | None / full / selected fields |
| Rate limit | Human-paced | Your cron | 10 / min per agent |
Control is what makes AI deployable.
MSPs don’t need more autonomy — they need more control. Automations are built for supervised rollout, not magic-button hype.
Dry-run mode
The runtime filters the agent’s tool access to read-only during dry-run. Not a label — it materially changes what the agent can do.
Explicit tool scoping
Agents cannot be created without a concrete tool list. Every requested tool is validated against your connector subscriptions and plan.
Tool policy & chains
Beyond a simple allow-list: tri-state policy (allowed / denied / required), plus optional ordered tool chains for multi-step workflows.
Runtime & credit caps
Max runtime and MaxCreditsPerRun are enforced at runtime, not reported after the fact.
Consent & sync checks
Runs are blocked if consent isn’t accepted or the agent’s remote state drifted. Silent failure isn’t an option.
Webhook hardening
Per-agent signed secret, payload size cap, 10/min rate limit, and payload mode control — full, selected fields, or none.
Two ways to run. both bounded.
Classic: pay-as-you-go credits on our hosted Anthropic runners — no subscription, packs never expire. BYOK: a flat monthly rate on your own Anthropic key with unlimited runs per concurrency slot.
Estimate up front
Before any run, credits are reserved up to the agent’s per-run cap. Complexity and expected runtime inform the estimate.
Live as it runs
Token usage, tool calls, and duration are tracked in real time. The estimate tightens as the run progresses.
Refund the difference
After the run, actual consumption is finalized. Unused reservation is refunded. Every transaction is in the ledger.
Classic · credit packs
One-time purchase. Credits never expire. Stack as many packs as you want.
MaxCreditsPerRun so a run can’t blow past your budgetBYOK · bring your own key
Flat rate · no creditsRun Automations on your own Anthropic API key (API Console). No credits consumed — you pay Anthropic for tokens and StackJack a flat monthly rate for the runner platform: triggers, scheduling, guardrails, audit trail, and run history. Priced by how many agents can run at once.
Automations BYOK Pro
$199/moFlat-rate Automations on your Anthropic key.
- 1 concurrent agent slot
- Unlimited runs · zero credits consumed
- Same guardrails, audit trail & run history
Automations BYOK Business
$299/moFor teams running several agents side by side.
- 3 concurrent agent slots
- Unlimited runs · zero credits consumed
- Same guardrails, audit trail & run history
Extra concurrency
+$99/slot/moAdd concurrent job slots to either BYOK plan — stack as many as you need.
- +1 concurrent agent slot each
- Purchase any quantity
- Add or drop as your workload changes
Azure AI Foundry BYOK — run on your own Foundry deployment with region pinning and enterprise-grade governance. Anthropic (API Console) keys are supported today.
Every run is inspectable.
No “it ran” mystery. Every execution gets a persistent record with status, timing, tokens, tool calls, credits, summary, and a transcript you can pull on demand.
| Started | Status | Duration | Tools | Tokens | Credits | Summary |
|---|---|---|---|---|---|---|
| Apr 19 07:00 | ✓ Completed | 47s | 9 | 16,384 | 212 | 12 priority, 3 SLA risk |
| Apr 18 07:00 | ✓ Completed | 52s | 11 | 18,120 | 244 | 15 priority, 1 client impact |
| Apr 17 07:00 | ! TimedOut | 120s | 14 | 22,004 | 304 | Hit max runtime — partial summary |
| Apr 16 07:00 | ✓ Completed | 41s | 8 | 14,290 | 188 | 9 priority, clean backlog |
| Apr 15 07:00 | ✓ Completed | 39s | 7 | 13,880 | 176 | 11 priority, 2 new escalations |
What MSP teams actually run.
Real workflows. Not hypotheticals. Each of these fits the Automation shape: recurring, cross-system, judgment-heavy, too messy for a script.
Daily priority queue review
Reviews open priority tickets, pulls cross-system context from PSA + RMM + docs, flags SLA risks, and drops a briefing in the team channel before standup.
High-priority ticket triage
When a P1 fires, the agent gathers recent related tickets, client contacts, known assets, and documentation in seconds — posted directly to the ticket.
Weekly service briefing
Generates per-client weekly summaries: ticket trends, SLA hits/misses, recurring issues, and asset changes. No more manual cross-tab assembly.
Documentation hygiene & drift
Checks IT Glue and Hudu for stale configs, missing passwords, expiring certs, and orphaned assets. Flags items before they become client-facing issues.
QBR prep brief
One click: the agent compiles a client’s ticket trends, asset posture, escalations, and open risks into a QBR-ready narrative with source citations.
M365 security response
On a CIPP alert, the agent looks up the affected tenant, correlates with user activity, recent mailbox changes, and admin actions — then summarizes suspected blast radius.
Warranty & lifecycle audit
Walks the N-central fleet for devices with warranties expiring inside 90 days, cross-references asset cost and vendor contracts, and opens a per-client renewal task — before anything lapses.
Attack-surface drift watch
Evaluates Liongard dataprints and metrics for new admin accounts, changed M365 posture, and fresh external exposure since yesterday — then escalates only material drift, with evidence.
Distribution spend reconcile
Pulls Pax8 subscriptions and usage, matches them against billed PSA agreements, and flags license drift and margin leaks so nothing ships under-billed at invoice time.
Chat is useful. Scripts are reliable.
automations sit in the middle.
Traditional automation is great for rigid tasks. Chat is great for exploration. Automations handle the recurring workflows that need context, summarization, and cross-system judgment.
| AI chat session | Scripts / RPA | Automation | |
|---|---|---|---|
| Persists between uses | No — one session | Yes | Yes — versioned definition |
| Handles context + summarization | Yes | No | Yes |
| Runs on schedule / webhook | No | Yes | Yes |
| Tool access is scoped & audited | Session-level | Script-specific | Per-agent MCP credential |
| Handles messy / judgment-heavy work | Yes | Brittle | Yes |
| Safe rollout / dry-run | Ad hoc | Staging envs | Built-in, read-only |
| Run history & spend caps | Chat log | Logs, if you build them | First-class, with credit ledger |
Start from a template. Publish your own.
Built-in templates, tenant-shared agents, and a moderated marketplace with versioning, risk badges, and safety scanning. Templates are parameterized, reviewable automation blueprints — not chaotic snippets.
Questions.
Do I need to pay for Automations separately from my connector subscription?
No. Automations are included free for any StackJack user — including Free-tier connector users. You only pay for credits, which cover the actual AI execution and tool calls. Credit packs never expire.
How do credits relate to actual usage?
Before every run, credits are reserved based on the agent’s complexity and expected runtime, up to the agent’s MaxCreditsPerRun cap. As the run executes, real token and tool-call usage is tracked. At the end the run finalizes: unused reservation is refunded, and every transaction shows in your ledger.
Which tools can an agent access?
Only the tools you explicitly pick when authoring the agent — and only if those tools are available via your connector subscriptions and plan. Each agent gets its own scoped MCP credential, so one agent cannot “borrow” another agent’s access surface.
What does dry-run mode actually do?
Dry-run is not a label — the runtime filters the agent’s tool access to read-only operations. That lets you verify behavior, review transcripts, and build trust before promoting an agent to live execution with write access.
How are scheduled agents rate-limited?
Scheduled agents run on your configured cron with timezone awareness. If the tenant becomes ineligible (e.g. insufficient credits) or capacity is unavailable, runs are silently skipped rather than piling up failures or double-billing. Startup reconciliation re-registers expected jobs after deploys.
How are webhook endpoints secured?
Each webhook-triggered agent gets its own signed secret baked into the URL. There’s a per-agent rate limit (10 / minute), a payload size cap, and three payload modes: none (prompt-driven), full payload, or selected fields. You control exactly what context the agent sees.
Can I bring my own Anthropic API key?
Yes. Enterprise BYOK is supported: runs and wizard turns bypass managed credit billing entirely. The platform still records audit transactions for every BYOK run so you have full operational traceability. Talk to us to set it up.
What knowledge sources can an agent use?
Today, Automations support reusable text snippets and URL-fetched content as knowledge sources. File-based knowledge is on the schema for legacy reasons but is not currently supported as a live runtime feature.
What happens if a run blows past its credit cap?
Runs have a MaxCreditsPerRun setting and the runtime enforces it — the run is marked CreditExhausted with whatever summary was produced to that point. If actual consumption exceeds reservation within the cap, the delta is recorded in the ledger rather than hidden. This preserves billing truth.
Can I see what an agent did during a run?
Yes. Every run has a record with status, timing, token counts, tool-call count, credits consumed, a summary, trigger payload, and a full transcript you can fetch on demand.
Can I share or publish agents?
Agents can be saved as templates (private, tenant-shared, or submitted to the marketplace). Templates are versioned, parameterized, and go through scanning + admin moderation with risk badges before publishing. So the marketplace is moderated, not a free-for-all.
Does StackJack see or store my data?
StackJack is a proxy — your business data passes through during runs and is not stored, cached, or retained. Run records store metadata (status, timing, token counts, summary) and transcripts so you can review what happened, but the underlying MSP data is never retained outside that. See the full security brief.
Recurring work, managed.
Automations are available today for every StackJack user. Buy a credit pack to start — packs never expire, and you’ll see real-time usage against your balance as your agents run.