Bridge enables you to create intelligent agents that automate routine tasks, handle data operations, and interact with users — directly within your workspace and chats. Your AI agents can access and work with any entity in your workspace – from chat conversations and databases to tasks, documents, and even other AI agents. Chain these capabilities together to create powerful workflows that automate your processes end-to-end. If our skill library isn't enough, we'll help create any custom skill you need.
Each agent is built as a modular system, consisting of:
Variable types supported:
Text, date, number, money, list, file attachments, arrays.
The more detailed your variable descriptions are, the more effectively the agent can process and apply them.
Knowledge empowers the agent to reason and respond based on live documentation.
For example, if you upload internal policies or procedures to an agent, it can:
This turns documentation into a dynamic part of your operational intelligence.
Skills are the core building blocks of agent functionality. They define what an agent can do — either inside the platform or with external systems.
Bridge includes a visual skill editor — a flow-based automation builder.
Each skill is composed of logic blocks connected by data flows.
Examples:
The skill library is constantly evolving, and soon it will support integration with any external system via API.
Skills can be chained to create workflows like:
Fetch data → Save to database → Notify a user in chat
Each skill must have a clear name and description — this is how agents understand what the skill does.
Good descriptions help agents choose the right skill during execution.
Examples:
✅ “Save IT expenses to database”
✅ “Get all active deals this week”
❌ “Skill 1” or “Test”
Agents may use multiple skills dynamically based on their goals — descriptions determine relevance.
All of this can be configured visually — no code required.
With skills and agents, you can automate:
Each agent supports versioning:
Agents can be connected to:
Choose between models based on performance needs:
Model choice affects token consumption and performance.