Can Grist and Village talk in both directions?

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

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

Grist triggers: 2
Grist actions: 5
Village triggers: 0
Village actions: 40

Automation ideas

What you can build with Grist and Village

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

New Record in Grist creates Get App Information in Village
Triggers when a new record is added to the table.
New Record in Grist creates Check Company Paths in Village
Triggers when a new record is added to the table.
New Record in Grist creates Refresh Companies in Village
Triggers when a new record is added to the table.
Updated Record in Grist creates Get App Information in Village
Triggers when a record is updated in the table.

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.

More ways to automate Grist

View Grist

Grist + SimplyPrint

3D printer fleet management: monitor printers, manage the print queue, track filament, and automate print jobs.

Productivity

Grist + Google Sheets

Create, edit, and collaborate on spreadsheets online

Productivity

Grist + 0CodeKit

Ready-made utilities for automations: dates and calendar weeks, conversions, validation, PDF and QR tools, file storage, AI text and image analysis, code execution, crypto and short links.

Developer Tools