Form Intake Agent
Writes every form submission into your intake sheet as a clean row in your column order, and pings Slack only for the ones that cannot wait until tomorrow.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
New response
Internal request form: new starter kit
Submitted 08:41. Request type: IT equipment. Site: Leeds head office. Who is it for: two new starters in payroll, both starting 1 September 2026. What do you need: two laptops, docking stations, and headsets. Needed by: 28/08/2026. Contact number: 0113 496 0182. Anything else: they share a desk, so one monitor arm each is plenty.
Aoife Brennan · a.brennan@northgatecare.co.uk
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Google Forms
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Google Sheets
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Intake rules
How your intake sheet is laid out - the exact columns in order, what belongs in each one, the labels you use for request types, and the date and phone formats you want. The agent writes every row to match this.
Alert criteria
Which submissions are worth interrupting someone for - the request types, urgency words, sites, or people that mean somebody should look now rather than at the end of the day.
Choose which agent runs it
NoClick's built-in models work out of the box — or bring Claude Code, Codex, and other coding agents on your own subscription.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
About this agent
Intake forms pile up in a response tab nobody reads in order, and the one urgent request sits quietly between two laptop orders. This agent writes every submission into your sheet in the column order you defined, tidies the dates and phone numbers people type badly, and posts to Slack only when a response matches criteria you set. Nothing is dropped, including the ones that arrive half finished at midnight.
What people use it for
- One tidy sheet, always - Support requests, IT asks, and event signups land as rows in your order rather than a raw form export. The filters, pivots, and reports built on top of that sheet keep working.
- Urgent requests get seen - A failing freezer and a monitor request arrive through the same form. Only the first one reaches Slack, which is why people keep the channel open at all.
- Messy answers come out clean - Dates typed six different ways and phone numbers missing a country code end up consistent, so the sheet is still searchable months later when somebody asks what happened in August.
- Nothing quietly disappears - A submission the agent cannot parse still gets a row, with a note saying what was unreadable. That is recoverable in a minute, whereas a skipped response is simply gone.
Before you fork
What do I need to connect?
The Google Form you collect submissions on, a Google Sheets credential that can read and append to your intake sheet, and the Slack channel for alerts. Then you describe your columns in order and what counts as urgent, in your own words. The sheet can already have data in it, since the agent reads the header row and appends underneath.
What happens if someone changes the sheet columns?
It reads the header row on every run instead of remembering a layout, so an added or renamed column is picked up on the very next submission. If a column your rules mention no longer exists, it says so in the notes column rather than guessing where the value belongs. Update the rules and the following row matches again.
What does it cost to run?
One short run per submission, so a quiet form costs almost nothing and a busy one scales with real volume. Submissions that do not meet the alert criteria finish sooner because they end at the sheet write. Nothing runs between responses, so an idle week costs nothing at all.
Run it with your coding agent
Works with
More agents like this
Put Form Intake Agent to work
Free to start. Guided setup, a test run against staged conversations, and it's live.