Documentation

English

Français

English

Français

Your first steps in Studio ​

No technical prerequisites are required. Your first journey is to create a workflow, use the canvas, save it, and test it in Semantics Chat.

1. Create a workflow ​

  1. Open the workflow list. It displays every workflow in your organization and its status.
  2. Click Create a workflow.
  3. Give it a clear business name, such as HR Assistant or Level 1 Support, and a short description.
  4. The editor opens with the Start block, the required entry point for every conversation.

You can also start from the catalog and adapt a workflow to your needs.

2. Use the canvas ​

  • Add a block: drag it from the palette onto the canvas.
  • Connect blocks: draw a link from a block output to the next block.
  • Configure a block: select it to open its side panel.
  • Zoom: use the mouse wheel.
  • Pan: drag the canvas background.
  • Delete a block: select it and press Delete.

Block positions are purely visual; execution order is determined by the links.

3. Connect outputs ​

Most technical blocks offer two paths:

  • After success continues the normal path;
  • After failure leads to a fallback, usually a user-friendly Simple message.

4. Fix issues and save ​

Studio continuously validates required fields, JSON, variable references, and disconnected blocks. Issues appear next to their fields and in the problems panel at the top right of the screen.

Users do not see your changes until you save. Studio asks for confirmation if you leave with unsaved changes.

StatusMeaning
DraftUnder construction and hidden from users
ActiveUsed to answer messages in Semantics Chat
InactiveTemporarily suspended

5. Test in Semantics Chat ​

Every message triggers a full path starting from Start.

  1. Link a Semantics App to a workflow.
  2. Test the minimal workflow.
  3. Add blocks one at a time.
  4. To inspect a variable, temporarily add a Simple message containing {{codeblock myVariable}}.
  5. Deliberately trigger a failure, such as an invalid URL, and check that the error message is clear.
  6. Remove debug messages before production, especially when they could reveal a token or business data.

Test both routes

A working happy path is not enough. Also verify After failure outputs, the Else case of conditions, and responses when a variable is empty.