Skip to content
Automation Squad
TfGSTMade to order

Notifications & alerts

Typeform response → Google Sheets tally → Teams alert at capacity

Teams tells the organiser when a form reaches the number you set, and not before.

Each Typeform submission is written to a Google Sheet and counted. At a warning number, and again at the limit, a message goes to a Microsoft Teams channel naming the form, the count and the latest respondent. Nothing posts in between. Built for event organisers, trainers and survey teams who cap places or quotas and currently learn the form overfilled from the complaints.

How it works

  1. Tf

    Trigger

    Form response submitted (Typeform webhook)

    Typeform

  2. GS

    Step 1

    Append the response to the tally sheet

    Submission time, respondent name, email and the answers you map go onto a sheet tab for that form, one row per response.

  3. GS

    Step 2

    Read the tally back

    Reads the rows for that form and counts them, so the total survives n8n restarts and can be checked by eye in the sheet.

  4. if

    Step 3

    Compare the count to the warning number and the limit

    Two numbers set in workflow variables; the run stops unless the count has just reached one of them, so each threshold posts once.

  5. T

    Step 4

    Post the alert to the Teams channel

    A channel message carries the form name, the current count, whether it is the warning or the limit, and the name of the respondent who tipped it over.

What changes once it runs

  • Within a minute of the submission that reached the number, the message is in Teams.
  • Two thresholds, a warning and a limit, each post once; the sheet shows exactly which response tipped it.
  • The tally sheet doubles as the attendee or applicant list, one row per response with the answers you chose.
  • Add a second form by duplicating the trigger; each form keeps its own sheet tab and its own pair of numbers.

What you get

  • The n8n workflow export with the Typeform trigger, the Sheets append and read, the threshold check and the Teams post
  • One tally spreadsheet template with the column layout the workflow expects
  • Setup guide covering the Typeform token, the Google and Microsoft credentials and the two threshold variables
  • A recorded walkthrough submitting test responses until both alerts fire
  • 30 days of email support for setup questions

Before you start

  • Typeform: an account, a form you own and a personal access token for the trigger
  • Google: an account with edit access to the tally spreadsheet
  • Microsoft 365: a work or school account with a Teams channel you can post to
  • A Microsoft Teams OAuth credential in n8n; self-hosted instances need an Azure app registration for it, and the guide walks through that

Built for

Questions before you buy

Can it close the form when the limit is reached?
Not in this package; the alert tells you and you close it. Unpublishing a form by API is a bigger action than an alert should take unattended. The guide marks where that step would go if you decide you want it.
Does it work with Google Forms or Jotform instead of Typeform?
Jotform, yes, with its own trigger node swapped in. Google Forms, yes, by watching the response sheet with a Google Sheets trigger, in which case the append step is dropped. Both are small swaps and the field mapping stays the same.
What if two people submit at the same moment?
Each submission runs the workflow on its own, so two arrivals a second apart both append and both read the count. The check fires only for the response whose read hits the exact number, so you still get one message per threshold. Rarely, both reads see the same count and you get two messages; the sheet shows the truth either way.
Can it run on Make or Zapier?
Make, yes; a Make blueprint is included and the count uses Make's aggregator. Zapier can do it with Storage by Zapier holding the counter, but then the sheet stops being the source of truth, so we ship n8n and Make only.

Nearby on the shelf

Whole catalog