Build and Edit Modules with the AI Agent

The AI agent lets you build and change BRYTER modules by chatting with an AI assistant. You can generate a new module from a description, change an existing module, or ask questions about how a module works.

The AI agent replaces the AI Module Builder. Everything the AI Module Builder did is still available in the agent's Create mode.

You can use the AI agent for a variety of workflows, such as leave request forms, compliance questionnaires or information intake forms.

Quick navigation

• Open the AI agent
• Create, Edit and Ask
• Create a new module
• Edit an existing module (beta)
• Ask about a module
• Attachments, capabilities and limits
• Tips for getting the best results
• Frequently asked questions

Open the AI agent

Open a module in the Module Editor and click the Agent tab in the editor header, next to Build and Inspect. You can also click the sparkles button on the narrow bar at the left edge of the canvas.

The chat panel opens on the left side of the canvas. To close it, click the Agent tab again or the sparkles icon at the top left of the panel. Switching to Build or Inspect also closes it.

Create, Edit and Ask

The agent has three modes, shown as tabs at the top of the chat panel. Only two tabs appear at a time, depending on whether your module is new.

When you open the agent on a new module, it starts in Create. On a module that already has content, it starts in Ask.

You can't switch tabs while the agent is working on a reply or a change.

Create a new module

Use Create on an empty module to generate a complete module from a short conversation. Create works in three phases: describe, refine and generate.

1. Describe your module idea

Open the agent on an empty module. The Create tab is selected. Describe the module you want to build. You can give a brief overview or describe the workflow in detail.

Examples:

• Build a leave request form that asks for the employee’s name, start date and end date, calculates the number of days, and emails the manager for approval.
• Create a compliance checklist for onboarding new vendors.
• I need a contract review workflow that collects key terms and generates a summary document.

You don't need to know BRYTER node types or technical terms. Describe what the workflow should do, and the assistant translates it into the right module structure.

2. Refine the workflow through conversation

The assistant asks follow-up questions, one at a time, usually over two to five exchanges. For example, it may ask:

• whether the module is a page for end users or a processing step that runs in the background
• which information the module should collect, and whether the flow should branch depending on the answers
• whether the module should send emails, generate documents or show a result page
• which database, integration or document template to use. The assistant names what it plans to use and waits for you to confirm.

3. Generate the module

When the assistant has enough information, it shows Here is the plan of the module:, followed by the plan and Ready to generate your module!

You have two options:

• Add more details – keep refining the workflow.
• Generate module – build the module based on the conversation.

If your application supports several languages, you're asked Which languages should this module support? Pick a default language and any additional languages. Languages marked with a warning icon can't be translated automatically and need to be translated manually.

You can follow the progress in real time: Analyzing your prompt, Preparing module blueprint, Generating module plan, Validating structure, Assembling module, and Translating if you picked additional languages. Generation can't be cancelled once it has started.

If generation fails, you see Sorry, the module could not be generated. Please try rephrasing your prompt or simplifying your request. Your conversation is kept, so you can adjust your request and try again.

4. Review and customize the generated module

When generation is complete, you see Module generated and the new module opens in the editor. In the version history, this version is labelled Generated by AI.

The generated module is a starting point. Common next steps include:

• Reviewing the generated nodes and workflow structure.
• Adjusting labels, texts or logic.
• Testing the module in the preview.
• Adding more details with Edit.

Edit an existing module (beta)

Use Edit to change a module that already has content, without rebuilding it.

1. Describe the change

Open the agent on a module with content and select the Edit (beta) tab. Describe the change you want to make.

Example: Add a question asking for the employee’s department after the name field, and include it in the manager email.

The assistant may ask a clarifying question. If something isn't supported yet, it tells you and suggests how to do it manually.

2. Let the agent apply the change

Once the assistant understands your request, it shares its plan and applies the changes.

While it works, the module is read-only. The header shows AI is thinking and then AI is applying changes, and the panel shows Editing your module. Larger changes can take several steps.

3. Review the summary

When the agent is done, the module reloads and a summary card lists what changed: Added, Edited, Deleted, Connections, Removed connections, Groups and Languages. Click a node or connection in the summary to jump to it on the canvas.

Use the thumbs up or thumbs down on the summary card to tell us how it went. If you choose thumbs down, you can add a comment.

What Edit can and can't do

Edit can:

• Add, change or delete nodes, and change a node's type.
• Add or change connections and their conditions.
• Organize nodes into groups.
• Change the module inputs and the module name.
• Add a language and translate content.
• Create a new database.

Edit can't yet move a node to a different place in the flow. Instead, the assistant can copy the node to the new position, update the references and delete the original.

If an edit fails, nothing in your module changes. For example, if someone else changed the module at the same time, you see This module was updated elsewhere. Reload the page and try your edit again.

Ask about a module

Use Ask to understand a module without changing it. Ask never edits your module, and you can keep working in the editor while it answers.

1. Open the agent and select the Ask tab.
2. Type a question, for example Which nodes use the start date variable? or Why does the flow skip the approval step for short requests?
3. The assistant answers based on your module and on how BRYTER works. Node and variable names in the answer are clickable and take you to that node on the canvas.

Ask can also draft documentation for a module or suggest how to restructure it.

If you ask for a change, Ask shows a Hand off to edit mode button. It switches to Edit, or to Create if the module is empty, and fills in your request. Review the request and click send to start.

Attachments aren't available in Ask.

Attachments, capabilities and limits

Attach files (Create and Edit)

Click the paperclip next to the message box, or drag files onto the chat. There are two kinds of attachments:

• Document template – a .docx file. The AI uses its structure and placeholders to set up document generation in your module.
• File – any supported file the AI should refer to, such as a PDF, spreadsheet, image or text file.

If you drop a .docx file, you're asked whether it's a template or a file to reference.

What the agent can build

Edit can also work with most other node types that already exist in your module.

Limits

• A single message can be up to 4,000 characters, and a conversation can have up to 50 messages. If a conversation gets too long, click Start over.
• Very large modules may be too big for the agent to edit. In that case, make the change in the editor.

Tips for getting the best results

Occasionally asked questions