Can Human Input and Tables talk in both directions?

Yes. Build one flow that starts in Human Input and acts in Tables, 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 Human Input to Tables

Move data between Human Input and Tables 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 Human Input Explore Tables

Human Input triggers: 2
Human Input actions: 1
Tables triggers: 3
Tables actions: 9

Automation ideas

What you can build with Human Input and Tables

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

Web Form in Human Input creates Create Table in Tables
Trigger the flow by submitting a form.
New Record Created in Tables creates Respond on UI in Human Input
Triggers when a new record is added to the selected table.
Web Form in Human Input creates Delete Table in Tables
Trigger the flow by submitting a form.
Record Updated in Tables creates Respond on UI in Human Input
Triggers when a record is updated in the selected table.
Web Form in Human Input creates Create Record(s) in Tables
Trigger the flow by submitting a form.
Record Deleted in Tables creates Respond on UI in Human Input
Triggers when a record is deleted from the selected table.