Documentation

Workflow Builder pack

The Workflow Builder pack is for teams who want to go from “we should automate this” to a working workflow without staring at an empty canvas. It bundles skills (document playbooks), a guided workflow, and an agent that work together.

Import it from the pack catalog like any other pack, install it into your workspaces, then customise names and workspace references to match your account.

What you get

Typical contents (exact titles may vary by catalog version):

Item kindPurpose
Skill documentsShort SKILL: playbooks on scoping a process, choosing step types, wiring formulas, and reviewing drafts before go-live
WorkflowA multi-step flow that applies those skills—collect inputs, search relevant skill docs, run an agent step to propose step definitions, and output a checklist you can implement in the builder
AgentAn assistant whose instructions point at the skills workspace and emphasise safe, auditable automation (human approval gates, clear inputs/outputs)

Together, these pieces answer: What should this workflow do?, Which step kinds fit?, and What should we name and pass between steps?

Who it is for

  • First workflow — learn patterns by running the pack workflow and reading the included skills
  • Repeatable design — product or ops leads run the same “workflow design” flow for every new automation proposal
  • Enablement — hand the pack to a customer or internal team so they inherit your design standards

You still build the final production workflow in the app; the pack accelerates design and consistency, not replace workflow authoring.

How the pieces fit together

  1. Skills workspace — documents explain when to use agent steps vs tool steps, how to reference {{ workflow_inputs }} and {{ steps.<id>.outputs }}, and when to add human approval steps.
  2. Design workflow — you provide a plain-language description of the process you want (for example, “weekly lead enrichment” or “invoice exception routing”). Steps search skills, then the agent proposes a step list with suggested inputs and outputs.
  3. Agent — follows the skills workspace instructions so answers stay aligned with your organisation’s rules (no skipping approval on financial actions, always cite which skill was used, and so on).

After a run, use the proposal as a blueprint: create a new workflow in the UI, add steps one by one, and paste formulas from the agent output.

Suggested first run

  1. Add the pack from pack catalog and install it (note which workspace holds the skill documents).
  2. Open the included Workflow Builder workflow and run it manually with a small real example from your team—not a hypothetical mega-process.
  3. Read the skill documents the workflow retrieved; edit any step wording that does not match your policy.
  4. Create a new workflow in Workflows → Create workflow and implement the proposed steps.
  5. Point your production agent’s instructions at the same skills workspace ID if you want chat and automation to share the same playbooks (Creating agents).

Customise for your organisation

  • Rename skills — prefix with your team name or split one skill into two shorter documents
  • Tighten the agent — add rules about data residency, forbidden tools, or required approval roles
  • Extend the design workflow — add a step that writes the draft to a document in a “Workflow specs” workspace for audit
  • Export your version — once customised, export a .a1kh file so other environments get your standards, not the stock catalog copy

Related documentation