Skip to main content
An Introduction to the Build Agent The Build Agent is where your integration logic is implemented. Using Versori’s SDK, you can define workflows, transform data between systems, and test your integrations before deploying them to production. Workflows are implemented inside a Project, where you can build integrations using code, a visual flow view, or the agentic chat interface.

​
Build Features:

​
Code

Use the in-browser IDE with AI assistance to implement workflows tailored to your integration. Focus areas include:
  • Workflows: Define triggers, actions, schedules, and branching logic for your integration.
  • Data Mapping: Transform and validate payloads between systems, handling the edge cases identified during planning.
  • Idempotency & Retries: Use stable keys and retry policies to prevent duplicate operations and ensure reliable execution.
  • Observability: Add logs and issue tracking to monitor each step of your workflow.
All workflows and transformations are implemented within a Project.

​
Chat

Use the chat interface to build and debug integrations agentically. You can generate workflows, modify existing logic, or troubleshoot issues through natural language prompts.

​
Flow View

Visualise your integration as a flow diagram showing each workflow step and the requests made during execution. This view helps you understand how data moves through your integration and inspect what happens at every stage. Features include:
  • Real-Time Testing: Run workflows using live or representative data, triggered by webhooks or scheduled events.
  • Debugger: Place breakpoints at specific workflow steps to inspect execution in detail.

​
Testing

Run end-to-end test executions through the visual flow diagram to validate your integration. You can:
  • Inspect executed data at each workflow step
  • Verify authentication and request behaviour
  • Validate pagination, rate limiting, and error handling
  • Testing helps ensure your integration behaves correctly before deployment.
Testing helps ensure your integration behaves correctly before deployment. See how testing works

​
Versions

Create versions to manage and track changes to an integration over time. Versioning allows you to safely update workflows while maintaining stability for existing deployments.

​
Environments

Deploy integrations across multiple environments, such as development, staging, and production. This allows you to test changes in a non-production environment before promoting them to production.

​
What to do Next

Once your workflows are implemented and tested, the final step is to deploy your integration. Continue to the Deploy Agent to release your integration to production and monitor its execution. Next: Deploy