Tleilax
GuideBuild a sample workflow

Build AI workflows with a human in the loop

Connect triggers, tools, agent steps, and approvals in one workflow you can inspect before it runs.

Build a sample workflow Browse templates
Tleilax / sample path A translucent three-way decision prism glowing in electric blue, orange, and violet
Workflow canvas · draftReviewable path
New requestTrigger
ClassifyAgent step
ApprovalHuman checkpoint
Ticket draftTool step

Workflow anatomy

See the handoffs in the workflow

Every sample path has a visible start, a set of steps, a human decision, and a recorded finish.

Trigger — start from an event or requestGive the path a clear starting point.
Agent step — interpret or prepareKeep the work between inputs and outputs.
Approval — pause for a personPut the decision on the path.
Tool step — take the next actionShow the handoff to a connected tool.
Run history — keep the path visibleFollow what happened at each step.
See the workflow path
Sample path / request review● visible handoff
TriggerRequest received
AgentPrepare context
ApprovalPerson reviews
ToolDraft ticket
HistoryRun recorded
One path, five observable handoffsConnectors show where the next step begins.

Workflow builder

Build the path, one step at a time

Start with a trigger, add the tools and agent steps it needs, then connect the handoffs.

Each step keeps its settings, inputs, and outputs close to the path so the workflow stays readable as it grows.

  • Add a Trigger, Agent, Tool, Condition, or Approval.
  • Connect each handoff before you review the run.
  • Inspect settings where the step sits.
Open the workflow builder
Abstract relay decision sculpture
sample-workflow / editor
Draft · unsaved changes
New requestTrigger / event
Classify requestAgent / context
Prepare ticketTool / draft
Human approvalCheckpoint / review
5 steps · 1 checkpoint● inspectable

Connection review

Give every tool a clear connection

Choose a credential at the step that uses it while keeping connection details in a dedicated panel.

Show where a credential is referenced and make environment changes visible before a workflow is deployed.

  • Credential picker
  • Usage visibility
  • Environment label
  • Review before deploy
Review credential setup
Tool connectionStep 03 / 05
CredentialTicket draft · selected reference
Support API
EnvironmentChanges are shown before deploy
Staging
Referenced byPrepare ticket / tool step
Review statusConnection details available
Ready to review
Review connection scope before the workflow is deployed.

Connection surface

Bring the tools into view

Choose the kind of system each step can read from or write to, then keep the credential and environment beside the workflow.

TriggerToolReviewDraft
INShared inboxRead a new request
CRMCustomer recordLook up approved fields
DOCKnowledge baseRetrieve source material
CALCalendarPrepare a schedule step
DBData tableRead or draft a row
MSGTeam channelPost a review request
TKTTicket queuePrepare a ticket draft
APICustom endpointUse a bounded connection
Approval checkpointWaiting for review

Request type: access change
Draft action: prepare a ticket
Source: new operations request

Reviewer actionDecide whether the run continues
Required

Human checkpoint

Pause before the consequential step

Add an approval checkpoint where a person should review context, edit a draft, or decide whether the run continues.

Make the handoff part of the workflow, not a message hidden outside it.

  • Context at the checkpoint
  • Approve
  • Reject
  • Request changes
Add an approval checkpoint

Run inspection

Trace a run when something changes

Run history lays out each step, its status, and the inputs and outputs available at that point.

When a step errors, surface the failed handoff and let the builder choose what to inspect or rerun. Keep recovery visible rather than promising a perfect run.

  • Step-by-step timeline
  • Input and output view
  • Error context
  • Rerun from a step
Explore run history
Abstract fast feedback relay object
Run / 0048Started 09:41
New requestInput received · 09:41:02
Done
Classify requestOutput available · 09:41:05
Done
Prepare ticketTool handoff · 09:41:08
Error context: connection response needs review.
Error
Next actionInspect step or rerun from here
Open

Template library

Start with a workflow pattern

Use a reusable starting point for common operations, then replace the steps, tools, and approval rules with the ones your team needs.

Support request → classify → approval → response draft

A clear starting path for requests that need context and a person before a response is prepared.

Use this pattern

New hire event → checklist → owner approval → handoff

Keep ownership visible as a request moves from an event into a reviewed handoff.

Use this pattern

Incident signal → summarize → review → ticket draft

Put a review point between the signal and the next draft action.

Use this pattern
Dim abstract deployment environment texture

Proposed deployment model

Choose how a workflow reaches its team

Keep a workflow in a hosted workspace for exploration, or move it into a controlled runtime when its operating boundary is part of the design.

Set the deployment target, review credentials and approval checkpoints, then make the active version visible in the workflow history.

Read deployment options
Abstract workflow trust infrastructure
Deployment targetVersion 0.3
Hosted workspaceExplore and review in one place
Controlled runtimeKeep the operating boundary explicit

Review before deploy

Selected target · Hosted workspace

Version to deploy0.3 draft
CredentialsReviewed
Approval checkpointIncluded
Open version review
Abstract connected workflow panels with a visible human decision point

Make the next workflow inspectable

Build a sample workflow with a trigger, an agent step, a tool, and one human checkpoint. Then follow the run from start to finish.

Build a sample workflow Read the workflow guide