TopolearnAutomations often need a front door where people submit requests; Forms give you one without a web developer.
Many automations start with a person asking for something: a time-off request, an IT ticket, a quote request. Zapier Forms lets you build that front door yourself. This product was called Interfaces until 2026; you'll still see the old name in some help links and older tutorials, and existing projects kept working after the rename.
You can start a form from an AI prompt, from an existing table, or from a blank template. Then:
- Add and edit fields (name, email, dropdowns, file upload).
- Add conditional logic to show or hide fields based on earlier answers.
- Choose what happens on submit: show a message, redirect to another page, open another page, or run a Zap.
- Connect the form to a table so every submission is stored as a record.
The usual pattern is Form -> Table -> Zap: the form saves a record, and a Zap triggered by the new record routes it, notifies someone, or creates a task. Forms can also give people editing access to a table without giving them a Zapier login to the table itself.
Preview and test the form before sharing its link, and check its access settings (public, or only people you invite).
Zapier also offers Chatbots: a chat window you can put on a website that answers from your own knowledge sources and can trigger Zaps. Chatbots, Forms and Tables can all be shown together in Canvas to document a full process.
Remember
- Zapier Forms is the new name of Interfaces
- A common pattern: Form saves to a Table, a Zap reacts to new records
- Use conditional logic and access settings before sharing
Watch out for
- Following an old Interfaces tutorial and not finding menus that were renamed.