5 · Calling an AI
Guests write special requests in free text: “I use a wheelchair”, “we travel with a baby”, “we arrive after midnight”. A language model can read them, classify them for the front desk, and draft the confirmation email — as ordinary steps of the process, with the same retries, timeouts and visibility as any other.
The definition
Section titled “The definition”05-special-request.ec.yaml:
id: special-requestname: Handle the guest's special requeststeps: - id: start type: START name: Booking received
- id: classify-request type: LLM_CALL name: Understand the special request preconditionStepId: start timeout: PT60S retries: 2 llm: connection: assistant # workflow.llm.connections.assistant system: "You read hotel guests' special requests and classify them for the front desk." prompt: "Guest ${guest} wrote: ${specialRequest}" responseSchema: # the answer must be JSON valid against this type: object required: [category, needsStaff, summary] properties: category: { type: string, enum: [accessibility, family, arrival, other] } needsStaff: { type: boolean } summary: { type: string } output: requestCategory: "json.category" needsStaff: "json.needsStaff" usageVariable: classifyUsage
- id: draft-confirmation type: LLM_CALL name: Draft the confirmation email preconditionStepId: classify-request llm: connection: assistant prompt: | Write a short, warm confirmation email to ${guest}. Their special request (${requestCategory}) is being prepared. outputVariable: confirmationEmail
- id: notify-guest type: ACTION name: Send it to the guest preconditionStepId: draft-confirmation
- id: done type: END name: Done preconditionStepId: notify-guestresponseSchemamakes the answer structured: it must be JSON valid against the schema, or the step fails withLLM_INVALID_OUTPUTand is retried — models sometimes need a second try. Theoutputexpressions read fields of the parsed answer (json.category).usageVariablerecords the tokens the call spent, per run.- Prompts and answers are never logged: they carry the process’s data.
Run it
Section titled “Run it”scripts/start.sh special-request BOOKING-6 '{"guest": "Erin", "specialRequest": "I use a wheelchair, please make sure the room is accessible", "rooms": [{"number": "101", "type": "double"}]}'
Agents: the AGENT step
Section titled “Agents: the AGENT step”An LLM_CALL is one question and one answer. An agent plans, calls tools, and may take minutes — and an action whose effect is uncertain must be reviewed by a person before the process goes on. The AGENT step invokes an agent published in the IA catalogue, which owns its prompt, model and tools; the workflow only chooses the task and the input:
- id: prepare-request type: AGENT name: Prepare the special request preconditionStepId: start timeout: PT5M retries: 0 # an agent failure is final: a paid model call is not repeated agent: ref: front-desk-assistant # the published agent taskPrompt: "Prepare what the front desk needs for this request: ${specialRequest}" input: guest: "${guest}" request: "${specialRequest}" outputVariable: preparationWhen the agent reports REVIEW_REQUIRED, the process is paused until the agent runtime reconciles it — completing, retrying or migrating it by hand is refused meanwhile. See Agents in workflows.
- BOOKING-6 completed with
requestCategory = accessibilityand aconfirmationEmail. -
classifyUsageshows the model and the tokens spent.