Skip to content
Teable logoVillage logo

Connect Teable to Village

Move data between Teable 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.

Teable triggers
2
Teable actions
17
Village triggers
0
Village actions
40

Automation ideas

What you can build with Teable and Village

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

  • New Record in Teable creates Get App Information in Village

    Triggers when a new record is created in a table.

  • New Record in Teable creates Check Company Paths in Village

    Triggers when a new record is created in a table.

  • New Record in Teable creates Refresh Companies in Village

    Triggers when a new record is created in a table.

  • Updated Record in Teable creates Get App Information in Village

    Triggers when a record is created or modified. The table must have a "Last modified time" field that shows the time.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

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