Before you start building, review what Socrates Builder supports and its boundaries. This helps you plan sessions effectively and avoid spending iterations on tasks the Builder cannot do.

By design, the Builder works within a single workspace and focuses on building and maintenance. It does not reach into other workspaces in your organization or into operational data such as active cases or Auto Triage. For investigation and case work, use the Investigator.

For guidance on starting a session and working through Plan and Build modes, see Socrates Builder: Getting Started.

The Builder builds production-grade workflows from a plain-language description. You pick the model in the composer: Claude Sonnet 5, Claude Haiku 4.5, or Claude Opus 4.8 (default). You describe the use case, and the Builder creates the steps, conditions, triggers, error handling, and integration configurations. These workflows can range from a simple, single-step task to a multi-step process with branching logic and enrichment from multiple sources.

Load an existing workflow into the Builder and modify it through chat. Provide the workflow name or its ID, describe the changes, and the Builder applies them. This is useful for adding steps, changing integrations, or restructuring logic in workflows originally built on the Workflow Designer. Complex workflows may occasionally require manual corrections after loading.

The Builder can extract reusable logic into sub-workflows and reference them from a parent workflow. This helps break complex processes into modular, maintainable pieces.

The Builder can create multiple workflows in a single session to cover a complete use case. For example, a SOC shift-notification system might need separate workflows for new-case alerts, analyst-assignment tracking, and escalation timers. The Builder identifies the required components and builds each one.

The Builder can create AI Agents as part of a workflow. You describe the AI Agent's purpose and the tools it should use, and the Builder configures it: setting the model, defining the prompt, attaching the relevant step tools, and defining the JSON output schema.

Beyond assembling integration steps, the Builder writes JQ transformations, Transform Data logic, and conditional and loop logic to shape and route data between steps. It can also generate formatted output, such as HTML (for example, an HTML email summary produced by an AI step).

For vendors without an out-of-the-box integration, the Builder can build workflows using HTTP request steps against the vendor's API. Provide the vendor's API documentation or payload format, and the Builder constructs the appropriate API calls and parses the responses.

The Builder works with the integrations already connected in your workspace, and falls back to HTTP requests for vendors you have not connected.

The Builder is aware of your entire workspace: integrations, credential status, existing workflows, and execution history. It can make changes that span multiple workflows. For example, it can swap a Slack integration across all workflows, processing each one to apply the change.

Share a failed execution (its URL or logs), and the Builder analyzes the failure, explains what went wrong, and can apply fixes directly to the workflow. You can also ask the Builder to review recent executions across your workspace (for example, "review all failed executions from the past 24 hours"). It will find and triage them. This works on any workflow, whether it was originally built by the Builder or on the Workflow Designer.

Attach files to the chat for context during a session (up to 3 files per message, each up to 5 MB). Use the paperclip button in the input bar, drag and drop files into the chat, or paste from your clipboard.

The Builder generates workflows and steps, but cannot create or configure integrations. Set up the integrations you need in your workspace before starting a session. If you connect a new integration after starting, the Builder may not detect it during that session.

The Builder works with the steps available in its step catalog. If a specific vendor step is not available, ask the Builder to use an HTTP request step.

Chats are saved, so you will not lose your history. Even so, for complex use cases with many iterations, starting a fresh chat can help the Builder maintain accuracy. For tips on structuring a handoff summary, see Socrates Builder: Prompting and Iteration Guide.

The Builder sees which integrations and credentials are connected in your workspace and references secrets by name. It does not access or read credential values such as API keys, tokens, or secrets. Secrets are resolved at runtime.

Workflows the Builder creates or modifies are automatically recorded in the Activity Log.

Your chats are saved so you can return to them later and keep context across sessions. Chat history is available from the chat list in Socrates.