Skip to content
TimeOps logoVillage logo

Connect TimeOps to Village

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

TimeOps triggers
4
TimeOps actions
6
Village triggers
0
Village actions
40

Automation ideas

What you can build with TimeOps and Village

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

  • New Customer in TimeOps creates Get App Information in Village

    Triggers when a new customer is created.

  • New Customer in TimeOps creates Check Company Paths in Village

    Triggers when a new customer is created.

  • New Customer in TimeOps creates Refresh Companies in Village

    Triggers when a new customer is created.

  • New Project in TimeOps creates Get App Information in Village

    Triggers when a new project is created.

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 TimeOps 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.