New response
One door for every request
Form in, row added, owner pinged, status tracked.
Access request agentThe right yes, from the right person.
When someone asks for access to a tool, it checks the request against your policy, logs it, and asks the right approver in Slack. It never grants access itself.
Your first signup includes $50 in free credits.
New response
Handle access requests
- Reads
- The request form, your policy
- Grows
- A logged request and a recommendation
- 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 access request form, check it against my access policy sheet, log it, and ask the right approver in Slack with a short recommendation.
TulipFarm
I made an agent called Access checker and a workflow that starts on each Google Forms response. It never grants access. Logging the request, posting to Slack and drafting the reply all ask 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
An access request is submitted
Run startedStarted - Reads
The request and the access policy sheet
1 request - Checks
Is the role allowed this tool by policy
Needs a manager - Writes
A recommendation and the approver's name
1 note - Asks first
Log the row and ask the approver in Slack
Approved - Posts
Row in Sheets, message in Slack
Approver askedCompleted
What lands in Slack.
The approver gets the request, the policy check and a plain recommendation.
Direct messageAccess checker APP · 11:05
Access request · design tool
Request
- Person A, on the design team, wants an editor seat.
- Reason given: owns the new landing page.
Policy check
- Design team may have viewer seats by default.
- Editor seats need manager approval.
Recommendation
- Approve. The reason fits the role.
- Someone must grant the seat in the tool.
What gets planted.
Three parts you own and can change at any time.
- Agent
Access checker
Checks each request against the policy.
- Table
Access log
Every request and who decided.
- Workflow
New response
Starts on each form response.
Uses
- Google Sheets
- Slack
- Gmail
Add if you use it
Jira
Google Calendar
Notion
It reads quietly. It asks before it acts.
Reads without asking
- The request form
- Your access policy sheet
- The access log
Asks you first
- Logging the request
- Asking the approver in Slack
- Emailing the requester
It uses your own connections, so it never sees more than you can.
Grow it your way.
Set an end date
Add a reminder to review temporary access.
Monthly review
List who has what and flag seats nobody used.
Tell the requester
Draft a short note once the approver decides.
Questions, answered.
Does it give anyone access?
No. It checks, logs and asks. A person grants access in the tool itself.
Where does the policy live?
In a sheet or doc you keep. Update it and the next run uses the new version.
Can it open a Jira ticket for IT?
Yes. Jira is built in. Creating the ticket 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.
Access, decided by people. Tracked by the agent.
Public beta, open to everyone. Your first signup includes $50 in free credits.