Can Wrike and Village talk in both directions?

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

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

Wrike triggers: 3
Wrike actions: 9
Village triggers: 0
Village actions: 40

Automation ideas

What you can build with Wrike and Village

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

New Task in Wrike creates Get App Information in Village
Fires when a new task is created in Wrike (optionally within a folder).
New Task in Wrike creates Check Company Paths in Village
Fires when a new task is created in Wrike (optionally within a folder).
New Task in Wrike creates Refresh Companies in Village
Fires when a new task is created in Wrike (optionally within a folder).
New Folder in Wrike creates Get App Information in Village
Fires when a new folder (or project) is created in Wrike.