Build on a canvas
A workflow is steps joined by edges. Each step runs a function, and an edge carries a value from one step to the next. Settings can use what earlier steps produced, and the editor offers those values as you type.
A workflow can start when a record is added, at a time, when a webhook arrives, or when somebody clicks Run now.
Released, not just saved
In CodeKasten, workflows are built in a workflow workspace and published as a release. The workspaces that should run one install it, and switch it on by making an instance. A change reaches them as a new version, so nobody edits the running copy by accident.
Calls to other services wait for review
Workflows that change records can run on a branch, where a person reviews the result. Their calls to other services are another matter, because an e-mail cannot be unsent. A connector action run on an agent's session branch is held: the merge sends it, once, and a branch closed without merging sends nothing.
That is the same review your data gets: see AI agent guardrails.
Connect other services
A connector teaches CodeKasten to talk to another service: how to sign in, which actions it offers, and which webhooks it sends. A workspace links the accounts its workflows should use, and credentials are stored encrypted, never synced to the browser and never shipped in a package.
- The Connector Action step calls an action with a linked account.
- The Connector Trigger starts a workflow when a webhook arrives.
- A connector can send a file, such as a video to a channel or a document to a drive.
Branches as steps
Workflows can work with versions themselves: create a branch, commit, merge and close it are functions you can use as steps. A workflow can make its changes on a branch and leave the merge to a person. The same record history covers it: see version control for business data.