Learn about blocks in Zeus AI native tools

Adds two branches to your flow: one followed "During business hours" and one "Outside business hours". Click "Set up business hours" to adjust your hours.

The "By business hours" block

Use it to handle support one way during the day and another way at night.

Write custom JavaScript to decide which path the tool takes next, for example based on user data or conversation history.

• context and customer: The inputs, with data about the current conversation and the customer.
• return "BranchLabel": The decision. The text your code returns decides which output Zeus AI follows.
• Outputs: Your custom branches, one per value your code can return.
• Error branch: Followed if the code fails, for example because of a typo or a temporary glitch, so the tool never freezes.

For example, if your code checks a customer's VIP status and returns "VIP_1", route them to the "VIP_1" output (a premium support path).

1. Click "Edit configuration" and edit the "Code".
2. Click "Add Output" for each value your code can return. Each output becomes a branch.
3. Click "Confirm".

Code branching configuration with outputs

Runs custom JavaScript during a Zeus AI conversation, for example to perform calculations, change variables, format data or run logic no other block offers. The code can use the workflow data, such as the conversation, customer or context.

• If the code succeeds: The flow continues through the first branch.
• If the code fails: The flow continues through the second branch.

The Code block

Click "Edit configuration", edit the code, then click "Confirm".

Editing the Code block

Sends or retrieves information from another system, for example to check an order status, look up customer information or send data to another system.

The API block

• Configure: Opens the configuration of the API request. Configure a new API, select an existing one, or click "Edit API template" to change the HTTP method (GET, POST and so on), headers and payload. You can select any API created through "{ } New API Call...".
• Input variables: The information the API needs, for example an Order ID. In "Value", enter the value or variable from your flow to send.
• Output variables: In "Expression", isolate the piece of data you want from the response (usually with JSONPath, for example $.body.customer.name). In "Variable", name the container that stores it, so you can use it in later messages. Click "+ Add" to save several fields from one call, such as a tracking number and a delivery date.
• If the action succeeds: The API returned a successful response, such as 200 OK, and the flow continues through the success branch with the output variables available.
• If the action fails: The flow continues through the failure branch instead of stopping. For example, ask the user to try again later, retry the request or route the conversation to a human agent.