Can Teamhood and Village talk in both directions?

Yes. Build one flow that starts in Teamhood 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 Teamhood to Village

Move data between Teamhood 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 Teamhood Explore Village

Teamhood triggers: 3
Teamhood actions: 8
Village triggers: 0
Village actions: 40

Automation ideas

What you can build with Teamhood and Village

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

New Item in Teamhood creates Get App Information in Village
Fires when a new item (task) is created in Teamhood.
New Item in Teamhood creates Check Company Paths in Village
Fires when a new item (task) is created in Teamhood.
New Item in Teamhood creates Refresh Companies in Village
Fires when a new item (task) is created in Teamhood.
Updated Item in Teamhood creates Get App Information in Village
Fires when an existing Teamhood item is modified.