Procurement that runs
without a procurement team.
Sourcing supplies takes weeks of email tag. Quote requests go out, half come back, comparison is manual, and the order finally lands a month after it was needed. A Loomal procurement agent runs the entire loop — RFQ, comparison, order, confirmation — from a real inbox at machine speed.
API Primitives used
mail_sendSend RFQs to suppliers
Quote requests go out from the procurement identity, threaded by supplier, signed and verifiable.
mail_list_messagesCompare incoming bids
Replies thread back into the agent inbox. extractedText feeds clean prices into the comparison logic.
vault_getPull approved supplier list
Approved suppliers, payment terms, and budget caps live encrypted in the vault.
Procurement is email tag with a budget.
A typical purchase request passes through five email threads, three approvers, and at least one forgotten reply before turning into an order. The work is mechanical — request quotes, compare prices, pick the winner, place the order — but the tool stack is so fragmented that humans end up running it manually every single time.
An agent collapses the workflow into one identity. It sends the RFQs, reads the replies, scores the bids, and places the order — only escalating when the bids are out of band or the supplier is new.
How to build it.
mail_sendSend the RFQs
Agent reads the approved supplier list from the vault and sends a parallel RFQ to each one with consistent specs.
mail_list_messagesCompare the bids
Replies come back into the agent inbox. extractedText pulls out price, lead time, and terms for clean comparison.
vault_getPlace the order
Agent picks the winning bid against budget rules from the vault, replies to the chosen supplier, and notifies finance.
Example prompt
“We need 200 laptops. Send RFQs to our 5 approved hardware vendors, wait 48 hours for responses, pick the lowest bid that meets our specs, and place the order.”
What ops teams build.
Recurring supplies
Agent reorders office and lab supplies on a schedule, comparing prices each cycle.
One-off purchases
Internal purchase requests trigger an RFQ loop and order placement without procurement intervention.
Multi-vendor sourcing
Agent maintains parallel RFQ threads with multiple vendors and consolidates the comparison automatically.
Budget enforcement
Bids over policy thresholds get routed to a human approver with the comparison data attached.
Supplier qualification
New supplier inquiries get qualified through a defined questionnaire flow before being added to the approved list.
Why procurement needs an agent identity.
Procurement workflows touch sensitive data — supplier pricing, payment terms, internal budgets — and they live in email. Most automation tools ignore the email layer entirely and try to recreate it inside their own UI, which nobody adopts. The result is a function that stays manual for years.
Loomal works inside the email layer where procurement actually happens. The agent has the inbox, the vault, and the audit trail — and runs the loop without forcing anyone to learn a new tool.
Supplier data encrypted
Approved supplier lists, pricing, and payment terms live in the vault under AES-256-GCM.
Per-order audit
Every RFQ, reply, and order is logged with timestamp and the human who authorized the agent.
Budget-scoped identities
Different cost centers can run on isolated identities with separate budgets and approvers.