Can DocsBot and Hedy talk in both directions?

Yes. Build one flow that starts in DocsBot and acts in Hedy, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect DocsBot to Hedy

Move data between DocsBot and Hedy the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore DocsBot Explore Hedy

DocsBot triggers: 0
DocsBot actions: 6
Hedy triggers: 5
Hedy actions: 19

Automation ideas

What you can build with DocsBot and Hedy

A few flows teams run between DocsBot and Hedy. Use one as a starting point, or build your own from scratch.

Session Created in Hedy creates Ask Question in DocsBot
Triggers when a new session is created in Hedy.
Session Created in Hedy creates Create Source in DocsBot
Triggers when a new session is created in Hedy.
Session Created in Hedy creates Upload Source File in DocsBot
Triggers when a new session is created in Hedy.
Session Ended in Hedy creates Ask Question in DocsBot
Triggers when a session is completed in Hedy.