Zoho Forms
FormsConnect AI agents to Zoho Forms. Agents push new form entries from other systems, read a report's submission records, fetch a single entry by ID, and discover an application's forms and reports for downstream routing.
What This Integration Enables
Most form connectors read. This one also writes, and that changes what Zoho Forms can be in a workflow. Reading, agents use List Forms to discover an application's forms and their link names, List Report Entries to drain any report on a schedule, and Get Entry to pull one record's full detail. Writing, Add Entry pushes a new submission into a form as structured data keyed by field link names, which makes Zoho Forms a destination: a place other systems' records can land and pick up everything the form carries with it, its validation, its assignment rules, its notifications, its approval flows. That dual direction is what lets Zoho Forms sit in the middle of a process instead of only at its start. - Route new submissions from any report into CRMs, sheets, and notification channels within minutes - Push leads, orders, and event records from other systems into Zoho Forms with Add Entry - Fetch a single record's full detail by ID when a downstream decision needs the source - Discover forms and their link names programmatically, so workflows survive form additions - Gate bulk writes with a human, because a form submission in Zoho Forms is never just a row
Without FlowRunner
With FlowRunner
Use Case Scenarios
The registration report that empties into the CRM
Event registrations collect in a Zoho Forms report. Every fifteen minutes, an agent pages through List Report Entries, matches respondents against [HubSpot](/integrations/hubspot), creates the new ones as contacts with session preferences attached, and logs registrations from existing accounts as activities for their owners. A [Slack](/integrations/slack) digest gives the field marketing team a running count. The report stays pristine in Zoho Forms; the pipeline runs everywhere else.
The spreadsheet that became five hundred proper submissions
A team migrating from ad hoc spreadsheet intake wants historical records inside Zoho Forms, where their approval flow now lives. An agent reads the rows from [Google Sheets](/integrations/google-sheets), maps columns to the form's field link names discovered via List Forms, and pushes each record with Add Entry, logging the returned reference ID back to the sheet. Because five hundred submissions means five hundred trips through the form's rules, a person reviews a five-record test batch and confirms which notifications should be disabled before the full run gets approval.
The high-intent answer that found a human in minutes
A pricing-page form asks for company size and timeline. When the sweep sees "this quarter" in the timeline field, Get Entry pulls the full record and the agent posts it to the sales channel with the respondent's answers laid out. The SDR replies while the prospect is still reading the pricing page, instead of three days later when the report gets its weekly look. The form did not change; the latency between answer and action did.
Human-in-Loop Highlight
Add Entry does not append a row to a table; it submits the form. Every record pushed through it runs the gauntlet Zoho Forms attaches to that form: validation, assignment rules, notification emails, approval flows. That is the point of writing into a form instead of a database, and it is also the risk. A bulk push of five hundred migrated records with the wrong field mapping does not just store bad data, it can fire five hundred notification emails and open five hundred approval requests before anyone notices the first one is wrong. So FlowRunner treats bulk Add Entry runs as gated: the agent maps the fields, runs a small labeled test batch, and presents the rendered result plus the full batch size and the form's active rules to a person. Single-record pushes with validated mappings flow on their own. The batch that will make the form act five hundred times waits for approval.
Agent Capabilities
4 actionsDiscovery
1- List Forms Lists all forms in a Zoho Forms application with each form's display name and link name. Link names are the identifiers every other operation addresses, so this is the first call in any new workflow.
Reading Entries
2- List Report Entries Retrieves the submitted records of a report, addressed by application and report link names, with start index and result count for paging through large sets. The sweep operation that turns any report into a scheduled feed.
- Get Entry Retrieves a single submitted record from a report by its record ID. The detail pull for high-intent routing, enrichment, and settling exactly what a respondent answered.
Writing Entries
1- Add Entry Adds a new submission to a form, addressed by application and form link names, with field values keyed by field link names. The write that makes Zoho Forms a destination, and the operation this page's human gate governs when it runs in bulk.
Frequently Asked Questions
What can FlowRunner do with Zoho Forms?
FlowRunner agents can run List Forms, List Report Entries, and Get Entry in Zoho Forms, plus 1 more action.
Does connecting Zoho Forms to FlowRunner require OAuth?
Yes. Zoho Forms connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Zoho Forms trigger a FlowRunner workflow automatically?
Zoho Forms doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Zoho Forms
$100 in credits. No card required. Connect in minutes.