Can tl;dv and Village talk in both directions?

Yes. Build one flow that starts in tl;dv and acts in Village, 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 tl;dv to Village

Move data between tl;dv and Village 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 tl;dv Explore Village

tl;dv triggers: 2
tl;dv actions: 5
Village triggers: 0
Village actions: 40

Automation ideas

What you can build with tl;dv and Village

A few flows teams run between tl;dv and Village. Use one as a starting point, or build your own from scratch.

Meeting Ready in tl;dv creates Get App Information in Village
Triggers when a meeting has finished processing and is ready
Meeting Ready in tl;dv creates Check Company Paths in Village
Triggers when a meeting has finished processing and is ready
Meeting Ready in tl;dv creates Refresh Companies in Village
Triggers when a meeting has finished processing and is ready
Transcript Ready in tl;dv creates Get App Information in Village
Triggers when a meeting transcript has been generated