Operations & Admin Request Desk · Operations
One routed, logged queue for every internal admin request
Laptops, access, purchases, HR paperwork: each request is classified, approved where your rules require it, logged in Notion, posted to Slack and confirmed to the requester.
Free account to start. Buying and running live need a paid plan.
- Starts when your form or app sends it something
- 1 AI step
- A person approves before it acts
- About 20 min to set up
Sound familiar?
The job, before and after this agent.
What it feels like today
- “Requests come in by email, chat and hallway, and half of them get lost.”
- “Someone buys software before anyone approved the spend.”
- “We find out what's missing from a request days later, when the deadline is close.”
What you get with the agent
- Every request classified by department and urgency, using the rules you write.
- A task title, checklist and list of missing information drafted for each request.
- Requests your rules flag (purchases, access) wait for an approver; rejected ones go no further.
- Each request logged in your Notion request queue and posted to your operations channel in Slack.
- The requester gets a confirmation email right away, with replies going to your operations inbox.
Before
A team lead messages you about a new starter on Monday who needs a laptop, four app seats and a $1,200 subscription. You piece it together from three messages and realise on Friday that nobody approved the subscription.
After
The request comes through your form, gets tagged IT and Finance, the subscription waits for an approver, and the requester is told today that you still need the start time. It's logged in Notion and visible in Slack.
How it works
The whole workflow, step by step.
Receives each internal request (equipment, access, purchases, HR paperwork, facilities) from your request form through a webhook. AI classifies the department and urgency, decides whether it needs approval under the rules you write, and drafts a task title, checklist, missing information and a confirmation for the requester. Requests that need approval wait for an approver in Reviews. The request is then logged in your Notion request-queue database, posted to your operations channel in Slack and confirmed to the requester by email, with replies going to your operations inbox.
- TriggerNew internal request
- AI stepClassify the request
- LogicNeeds approval?
- Needs approval:Approve the request
- No approval needed:Log it in the request queue
- No approval needed:Notify the team in Slack
- No approval needed:Confirm to the requester
- Human approvalApprove the request
- Approved:Log it in the request queue
- Approved:Notify the team in Slack
- Approved:Confirm to the requester
- App callLog it in the request queue
- App callNotify the team in Slack
- OutputConfirm to the requester
- OutputLogged
This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.
- Step 1New internal requestYour internal request form (or a chat or helpdesk tool) posts each new request to the workflow's webhook URL.
- Step 2Classify the requestAI picks the department, urgency and whether it needs approval under your rules, and writes a task title, checklist, missing information and a confirmation for the requester.
- Step 3Needs approval?Requests your rules say need approval wait for an approver in Reviews; the rest go straight to the queue.
- Step 4Approve the requestAn approver sees the request, the rule that applies and the checklist in Reviews, and approves or rejects it.
- Step 5Log it in the request queueCreates the request in your Notion request-queue database, titled with the department, with the summary, urgency, checklist and missing information.
- Step 6Notify the team in SlackPosts the request with its department, urgency and suggested owner to your operations channel.
- Step 7Confirm to the requesterEmails the requester what was understood, which team has it and what information is still needed, with replies going to your operations inbox.
- Step 8LoggedThe run history keeps the request, its classification and the outcome.
Example run
What goes in, and what comes out.
Example with fictional data
Comes in
Form request from a fictional Customer Success lead: new hire starting the 20th needs a laptop, Google Workspace, CRM access and a $1,200-a-year call-recording subscription.
The agent produces
Classified IT + Purchasing, urgency high, needs approval (spend over your limit). Checklist of 5 items, missing info: start time and cost center. After approval: logged in Notion, posted to #ops, confirmation emailed.
What you need
Everything it takes to run it.
About 20 minutes from purchase to live. A checklist above the canvas takes you through each step.
Plan
Included in Enterprise; on other paid plans it's $79 once. Agents run live on paid plans, from Basic ($39/mo).
Your AI key
Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.
Checklist
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Notion and Slack, connected in Settings → Integrations.
- A request form (or chat or helpdesk tool) that can send new requests to a webhook URL.
Setup, about 20 minutes
- Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
- Connect Notion. Connect the Notion workspace that holds your request queue (Settings → Integrations → Notion) and share the database with it.
- Connect Slack. Connect the Slack workspace your team uses (Settings → Integrations → Slack).
- Describe your teams and approval rules. Open “Classify the request” and replace the placeholder. Routing and approvals follow exactly what you write here.
- Pick your request queue. Open “Log it in the request queue” and pick your account and database.
- Pick the Slack account and channel. Open “Notify the team in Slack” and pick your account and channel. Invite the app to private channels first (/invite @Fluxo Flow).
- Add your operations email address. Open “Confirm to the requester” and enter the address requesters should reply to.
- Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
- Switch the trigger on. Open the trigger, switch the webhook on and send your request form's submissions to its URL.
Is it a fit?
Who it's for, and what it won't do.
Built for
- Operations and office managers
- People-ops teams at growing companies
- IT generalists handling access and equipment
- COOs who want approvals before spend
What it doesn't do
- It doesn't read a shared inbox; requests arrive through the webhook.
- It doesn't create tasks in other project tools or create documents in Google Docs.
- It doesn't order equipment, grant access or make payments; it routes the request to the people who do.
- It doesn't track the request after it's logged (status lives in your Notion database).
We list the limits up front so you can decide before you buy.
Price
$79 one-time
Per workspace. It never renews.
- Included at no extra cost on Enterprise.
- Buying and running it live need a paid plan, from Basic ($39/mo).
- Dry Run costs nothing: simulated AI and app calls, nothing sent.
- AI usage is billed by your own provider, at cost. No AI credits to buy from us.
One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy
FAQ
Questions about Operations & Admin Request Desk.
What if it classifies a request wrong?
It follows the departments and approval rules you write, and anything that needs sign-off waits in Reviews for a person. You can test it with Dry Run on a sample request before going live.
Does it actually order equipment or grant access?
No. It routes, logs and confirms; the people who do the work still do it. Status after logging lives in your Notion database.
What do I need to set it up?
About 20 minutes. Notion and Slack connected, plus a request form (or chat or helpdesk tool) that can send requests to a webhook. To run it live you need a paid plan and your own AI provider key (OpenAI, Anthropic, Google and others), added in Settings. Dry Run on sample data is free, so you can see real output before you commit.
Is it worth the price?
It's a one-time purchase that never renews. Weigh that against one unapproved purchase or one new hire starting without a laptop.
Who approves requests?
Anyone in your workspace who handles Reviews. Only requests your rules mark as needing approval wait there.
Can it create tasks in my project tool instead of Notion?
This version logs to a Notion database. You can swap the Notion step for another app step in the canvas.
Is this a subscription?
No. Operations & Admin Request Desk is a one-time purchase of $79 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.
Can I test it before it touches real data?
Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.
Put Operations & Admin Request Desk to work.
Free account, no credit card. Your Agents page opens with Operations & Admin Request Desk ready to buy and set up, then Dry Run it before it goes live.