Available process steps
From starting points and agents to approvals, actions and notifications. The company calendar is one of those steps — an appointment in the calendar, not an engineering shortcut.
- Starting point
- Agent
- Knowledge
- Decision
- Tool
- Approval
- Result
Appointment in the calendar
Appointment in the calendar
Someone asks for a time. An appointment is written: a visit, a meeting, a booking. Then confirmation goes out — a person can still say yes before it is saved.
MCP Fabric / Calendar
- Chat
- Appointment in the calendar
- Confirmation
Start by hand
Start a run from admin, a schedule or chat when you do not need a mailbox or a form.
From email
A new message in the connected mailbox starts the process. Attachments are stored with the run.
From WhatsApp
A customer message on WhatsApp Business can start or continue the same process.
From Teams
A message in your Teams channel can start or continue the process after the organization is connected.
From a form or webhook
A website form or an HTTP call starts the process. You can check the submitted data, publish the address and replay a received request.
AI agent
Runs a specialized agent with your knowledge, tools and rules — as a step in the diagram.
AI review
Evaluates prior output with a model step before the process diagram branches or continues.
Branch
Routes on an expression to named branches. The route is drawn, not hidden in a request.
Decision
If/else style routing on a decision variable with an otherwise branch.
Knowledge search
Search organization knowledge before later steps see the passages.
Connector tool
Invokes a governed connection through sensitive credential references and organization policy.
MCP tool
Calls a tool or capability on a organization MCP server — the same layer AI clients use.
Start another automated process
This process can start another named automated process and pass it what it needs. The other run is a real process, not a hidden shortcut.
Call a automated process
Start a automated process in the same project as a nested run you can follow — wait for it, then continue.
Automated process action
Generic catalog action selected from step type and operation keys.
Validate fields
Checks required fields on state and can respond when values are missing.
Collect variables
Asks for missing typed values and can loop until the set is complete.
Form / interactive UI
Emits an interactive form, can pause for a reply, then writes values back to state.
Map fields
Copies and transforms object fields with explicit target ← expression mappings.
Set state
Writes paths on run state from literals or $step expressions.
Wait
Pauses the run for a duration or until a timestamp in a chosen timezone.
For each
Iterates a list in run state with a cap on iterations. The loop is orchestrated, not client-side.
Loop back
Returns to an upstream step until a condition or iteration limit is hit.
Human approval
Stops the run until a person approves, then continues.
Notification
Sends e-mail, Teams or WhatsApp through the organization's channels.
Appointment in the calendar
Creates, changes or removes an appointment in the company calendar — a visit, a meeting, a booking.
Email campaign
Launches a named campaign through notification-service, optionally behind approval.
Response
Sends the process diagram result back on the inbound channel or as an HTTP body.
Fallback reply
A dedicated failure or unmatched-path reply, still limited to the organization.
Service handoff
Pass the run to another automated process or service. You can wait until that work finishes.
Query data
Builds and runs a governed PostgreSQL query against organization data, not a raw laptop connection.
HTTP request
Sends an explicit http(s) call from the process diagram. No connection object is required for this step type.
Code
Runs a bounded JavaScript or Python snippet in the automated process sandbox, not on the operator laptop.
Ready to move beyond the chatbot?
Build AI that understands your business, works with your knowledge, follows your processes and can actually finish the job. You decide which actions are allowed, when a person must step in and how much AI usage your organization can consume.