Integrations

A flow rarely lives in isolation — it reads from and writes to the tools your team already runs. Workbench ships integration nodes for that: drop one onto the canvas, configure it, and the flow can pull a record, post a message, or file an issue as part of its run.

The catalog spans the usual surfaces:

• Issue trackers & project tools — create and update issues, read tickets.
• Docs & wikis — read and write pages.
• CRMs — look up and update records.
• Messaging — post messages into team channels.
• Email — send transactional mail.
• Search & scraping — web search, page fetching.
• Data stores & vector DBs — read, write, and query.

The palette in the editor is the live list of what's available; configure each node with the credentials or workspace integration it needs.

Agents that use tools

Beyond fixed integration nodes, an agent flow can call tools dynamically — built-in web use, or other flows attached as sub-tools — deciding at run time which to invoke. That's the difference between a flow that always posts to one place and an agent that figures out what to do. See Nodes for the agent/tool building blocks.