New response
Handle access requests
Checks each request against policy and routes it for approval.
Request intake agentEvery ask lands in one place.
People send requests through one form. The agent adds each to a tracker, sorts it by type, suggests an owner, and tells that person in Slack.
Your first signup includes $50 in free credits.
New response
One door for every request
- Reads
- The form response
- Grows
- A tracked row with an owner
- Lands in
- Sheets and Slack
Ask for it once, in plain words.
No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.
You
When someone sends the request form, add it to my Requests sheet, pick a category and an owner from my list, and tell the owner in Slack.
TulipFarm
I made an agent called Request intake and a workflow that starts on each Google Forms response. Adding the row and posting to Slack asks you first. Activate it?
ActivateEdit first
One request, start to finish.
Every run is saved as an agent task you can open, check and rerun.
- Google Forms
A request is submitted
Run startedStarted - Reads
The response and your owners list
1 request - Writes
A category, a priority and a suggested owner
Facilities, normal - Checks
Does it need a manager to approve first
No - Asks first
Add the row and tell the owner in Slack
Approved - Saves
Row in Sheets, message in Slack
Owner toldCompleted
What lands in your tracker.
One row per request. The status column is the thing everyone checks.
Requests| Request | Category | Owner | Status |
|---|---|---|---|
| Replace the broken desk lamp | Facilities | Owner A | New |
| Add a seat to the design tool | Software | Owner B | New |
| Book the offsite room | Events | Owner C | In progress |
| Update the visitor sign-in | Facilities | Owner A | Done |
What gets planted.
Three parts you own and can change at any time.
- Agent
Request intake
Sorts each request and picks an owner.
- Table
Requests
Every request, with status.
- Workflow
New response
Starts on each form response.
Uses
- Google Sheets
- Slack
Add if you use it
- Gmail
Trello
Jira
It reads quietly. It asks before it acts.
Reads without asking
- The form response
- Your categories and owners list
- Open rows in the tracker
Asks you first
- Adding a row to the tracker
- Posting to Slack
- Sending any email
It uses your own connections, so it never sees more than you can.
Grow it your way.
Tell the requester
Draft a short note saying who has it and when to expect news.
Chase the stuck ones
Check weekly for rows still new after five days.
Split by team
Send each category to its own channel.
Questions, answered.
Who picks the owner?
The agent suggests one from your list. You can change it before you approve.
Can people see their request status?
They can if you share the sheet. The agent does not change what people can see.
Can it close a request?
Only if you ask it to update the status, and that change asks you first.
New response
Onboard a new vendor
Collects the forms, checks the list, and keeps a tracker up to date.
Fridays · 14:00
Run the weekly ops review
Gathers the week's numbers and open items into one review page.
Requests in. Owners told.
Public beta, open to everyone. Your first signup includes $50 in free credits.