5.3Forms & portals (Tally, Typeform, Fillout)
The essentials in 30 seconds
- First link: Tally, Typeform, Fillout create professional forms (design, conditional logic, uploads).
- Clean data at entry: typed, required fields, choice lists — constrain at input rather than fixing afterwards.
- Connected trigger: each response feeds Airtable/Notion and triggers Make/Zapier (confirmation, routing, notification).
Running case — Lina closes the door on incomplete files
Partner files reach Oran as scattered e-mails: missing documents, fanciful formats, endless follow-ups. Lina creates a Tally «File submission» form: typed fields, required documents, conditional questions by partner type. Each response creates an Airtable row and triggers the confirmation of receipt. Continuation of cases 5.1-5.2 — Lina secures the entry of her chain.
Continuation of cases 5.1-5.2 — Lina handles the first link that conditions everything downstream.
1. Professional forms
Data collection is the entry point of most workflows (registration, request, order, survey). Tally, Typeform, Fillout create professional, polished forms: pleasant design, one question at a time (Typeform), conditional logic (showing questions based on answers), calculated fields, payments, file uploads. Lina replaces free-form e-mails with a single form: no more incomplete files.
Pointers: Tally = complete and easy to pick up; Typeform = conversational experience; Fillout = powerful and well integrated with Airtable. Choose on usage, not fashion.
2. The clean trigger of a chain
Above all, these forms connect to your tools: a response feeds an Airtable/Notion base, triggers a Make/Zapier scenario, sends a notification. The form becomes the clean trigger of a whole chain: confirmation of receipt, routing by answer, task creation. At Lina's, each submission creates the row, notifies the department and files the case.
Clean data right at entry makes everything downstream reliable: no painful cleanup later, dependable automations. This extends the Airtable principle (level 2): better to constrain at input than to fix afterwards.
3. Designing for cleanliness
Everything hinges on design: typed fields (date, e-mail, number) rather than free text, essential information required, choice lists rather than free input (to avoid ten spellings of the same word), validation (e-mail format, value ranges). Conditional logic avoids asking for the useless: Lina only shows the «renewal» questions to existing partners.
A form integrated into a system (base + scenario) deserves a dedicated tool; a quick one-off survey can stay simple. The question is not the tool, it is the form's place in the chain.
🔎 Concrete example — Lina's «File submission» form
From input to action, with no retyping.
Form: partner type (list) + e-mail (validated) + documents (required, upload).
Logic: «renewal» questions only for existing partners.
→ each response creates an Airtable row (status «To check»).
→ Make: confirmation to the submitter + notification to the department concerned.Reading: each response is complete, typed and routed.
Lesson: the form is a trigger, not a mere collector.
Section vocabulary
- Form
- Collection interface feeding a base or triggering a workflow.
Simple example: Lina's file submission creates one row per response.
What it is not: a free-form e-mail with attachments in bulk.
Reflex: does each recurring collection deserve a real form?
- Tally
- Simple, complete no-code form tool.
Simple example: Lina sets up her submission in one afternoon.
What it is not: a shared spreadsheet used as collection.
Reflex: simplicity + integrations: does Tally cover my need?
- Typeform
- Forms with a conversational experience, one question at a time.
Simple example: Lina considers it for a polished satisfaction survey.
What it is not: a massive 40-question form in one block.
Reflex: is the answering experience polished?
- Conditional logic
- Showing questions based on previous answers.
Simple example: Renewal questions only for existing partners.
What it is not: asking everybody every question.
Reflex: is each question useful to this respondent?
- Integration
- Connecting the form to the base and scenarios to route responses.
Simple example: Response → Airtable row → confirmation + notification.
What it is not: picking up responses by hand every week.
Reflex: does submission trigger the rest with no retyping?
In practice — Creating a connected form
- Create a form (Tally, Typeform or Fillout) for a real need: registration, request or survey.
- Add conditional logic: only show certain questions based on previous answers.
- Connect the form to an Airtable/Notion base: each response creates a clean record.
- Hook a Make/Zapier scenario to the submission (notification, confirmation of receipt, routing by answer).
Ready-to-say script — announcing the new submission channel
«In Oran, files now arrive through a single form: guided fields, required documents, immediate confirmation. Each submission creates the tracking row and notifies the right department. No more bulk e-mails: if a field blocks you, tell me and I'll adjust the form. »
Say to partners and departments to get the single channel adopted without antagonising.
Copy-paste template — form spec
FORM — SPEC
NEED: _______________
FIELDS (typed + required *) : 1) ___ 2) ___* 3) ___
LISTS (anti-duplicates): _______________
LOGIC: if ___ then show ___
INTEGRATION: → base ___ → scenario ___ (confirmation + routing)
TEST: 1 full test submission: YES / NOSolo / small budget
Lina alone: a short form (5 typed fields) connected to a base is enough to halve follow-ups.
Small business / small team
Registration or request: choice lists + 2 required fields, simple routing to an e-mail.
SME in Oran
Lina tests the form with three pilot partners in Oran before rolling out the submission link.
Team getting started
Two-person review: one fills in the form «playing naive», the other fixes fields and logic.
✓ Best practices
- Use typed, required fields and choice lists.
- Connect the form to the base and hook a scenario to the submission.
- Add conditional logic to only ask for what is useful.
✗ Common pitfalls
- Leaving everything as free input (ten spellings of the same word).
- Forgetting to make essential information required.
- Neglecting the quality of the first link (all downstream depends on it).
Key takeaways
- Tally/Typeform/Fillout create professional forms (design, conditional logic, uploads).
- They connect to Airtable/Notion and trigger Make/Zapier: the form becomes a clean trigger.
- Tally = simple and complete; Typeform = conversational; Fillout = powerful and Airtable-integrated.
- Clean data right at entry makes the whole automation chain reliable.
48h challenge — apply tomorrow
Take 1 collection done by e-mail and list its 5 typed fields + 1 list: does your form spec fit the template?
- I can explain «first link» in one sentence.
- My spec (fields + logic + integration) is written down.
- I know how to connect submission → base → scenario.
Frequently asked questions
Why not use a basic free form?
The basic one handles a quick survey, but dedicated tools bring: polished design, conditional logic, calculated fields, uploads, and above all native integrations to Airtable, Notion and Make/Zapier. Since the form is often the first link of a chain, its quality (typed data, direct routing) conditions everything else.
How to guarantee clean data right at input?
Through design: typed fields rather than free text, essential information required, choice lists wherever possible, validation (format, ranges), and conditional logic to avoid the useless. Clean data at entry = no downstream cleanup and reliable automations.
Why take care with a form (Tally, Typeform, Fillout)?