Draw the process once. It runs itself after that.
Charms are the automation builder for whoever owns the process: ops, finance, support, sales. Lay the steps out on a canvas, join them up, and watch each run move step by step. Wherever a person should decide, the run waits for one.
Your team already knows the process. Now it runs.
The person who chases renewals or matches supplier bills knows every step and every exception. Usually that knowledge sits in a doc while they wait for an engineer to find time. With Charms they draw it themselves, watch the first run, and fix it the same afternoon.
Describe it, then correct the draft
Write the process in a few plain sentences and Build with AI lays out a first canvas. You move, add and join steps from there instead of starting at an empty page.
Every run, in the open
Each run shows what every step received, what it produced, and what the run cost. When something breaks, you see the step that failed and why, in words a non-engineer can act on.
Your agents do the thinking
An AI step hands the work to one of your agents. Pick the agent, and the step runs as that colleague, with the connections you already gave it.
28 kinds of step, grouped the way you think about the work.
Start it, fetch the data, let an agent read it, decide, ask a person, file the result. Each group has its own colour on the canvas, so a Charm reads the same whether you built it or a colleague did.
The run waits for you when it should.
Three kinds of step hand the run to a person. It shows Waiting for you until they act, then carries on the second they do. Each request arrives as a link that works without an account, so a supplier or a customer can answer too.
- Approval. Nothing moves past this step until somebody says yes.
- Data input. Ask a person for the details the run is missing.
- AI review. An agent checks the work first, then a person signs off.
A Charm starts where the work shows up and ends where it gets done.
Charms are wired into the rest of JuhJuh. A row in a View can start one, an agent can run a step, and the result can land in your tracker as a ticket.
Started by a View
A watcher checks every new row against a saved condition. The moment one matches, the Charm runs.
Into Plan & Work
A Create ticket step files the follow-up in your tracker, where an agent or a person picks it up.
Started the way you need
By hand, on a schedule, from a web address another system calls, on an event, or from a public form anyone can fill in.
Templates to start from
Publish a Charm that works as a template, install one a colleague built, or import one from a file.
Each Charm carries its own limit on steps per run, how long a run may take, and how many tokens it may spend. A loop that misbehaves costs you a ceiling, not a quarter. Every publish is a version, and a run already under way keeps the version it started on. Keep a Charm private, share it with a project, or open it to the whole organization.
Draw the process your team repeats most.
Describe it in a sentence, correct the draft, and watch the first run.
Your process, written down once and run every time after. That's the juju.
