Workflow examples
Two workflows as they look on the canvas: matching a candidate CV to a brief, and escalating a ticket that repeats a known outage.
In short
The people doing the work stay in the agent they already use. They describe the task, Hyperstruck finds the workflow, and returns a judged outcome. Two graphs below show the shape: what comes in, which insight it consults, and what comes back.
Names below are fictitious, the same kind of story the rest of these docs use. Swap in your desk, your briefs, and your tickets.
Candidate matching
A recruiter's firm already files hiring briefs as claims on a client-desk agent. candidate-company-match takes a CV, runs Candidate rediscovery for what the desk already knows about that person, then judges must-have skills, seniority, and overall match.
The graph is the whole workflow. Left to right: the request, the insight, three evals, then the answer (reasons and gaps).
They do not open Hyperstruck to start the work. They open Claude Code, with the MCP server connected, attach the CV, and type:
Check this CV against Juniper Labs' Founding CTO role.The brief is not in the message. It already lives in claims. The agent calls run_workflow and reports the verdicts Hyperstruck returned. It does not re-score them.
Must-have skills: met
Seniority: above
Overall match: 2.68 / 4
Reasons: hands-on applied AI, still writes code, salary inside the 220k to 320k band.
Gaps: founding-level CTO ownership should be checked against the brief.If a verdict looks wrong, they open the run and choose Correct this verdict. That correction is the label later training sees.
Repeat outage escalation
outage-escalation is the short version of the same shape. A ticket comes in. The Repeat outage accounts insight looks for a pattern this customer already has on file. The answer says whether to escalate, and why.
There is no eval on this graph. The outcome is the escalate decision and the reason, using whatever the insight found.
Support ticket triage
support-ticket-triage is a first-line desk with the same shape as the match workflow: a trigger, an insight for prior incidents on this account, then evals for routing, urgency and sentiment, then an answer. A quiet third outage can come back urgent because the insight found the pattern. A pricing question in all caps can come back low urgency when the account history says it is a question.
support-ticket-triage-enterprise-routing asks a narrower question on that desk: whether this customer should skip automated handling, and how urgent the ticket is.