Can Baserow and Village talk in both directions?

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

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

Baserow triggers: 7
Baserow actions: 14
Village triggers: 0
Village actions: 40

Automation ideas

What you can build with Baserow and Village

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

New Row in Baserow creates Get App Information in Village
Triggers when a new row is created in a Baserow table.
New Row in Baserow creates Check Company Paths in Village
Triggers when a new row is created in a Baserow table.
New Row in Baserow creates Refresh Companies in Village
Triggers when a new row is created in a Baserow table.
Updated Row in Baserow creates Get App Information in Village
Triggers when an existing row is updated in a Baserow table.