Build visual, no-code automation rules for your RFX process. Set triggers, add conditions, run actions, and delegate to AI agents — so every RFQ ends the way your procurement policy defines, automatically.
Outcomes from moving RFQ decisions out of an SOP PDF and into a running flow.
Small RFQs below your threshold close themselves — award, notify, and push to ERP without anyone looking at them. Buyers keep their hours for strategic spend.
Thresholds, approvals, and awarding rules live in the flow — not in an SOP PDF that nobody re-reads.
Above the threshold, a named AI agent drafts a summary and awarding recommendation — the human makes the call.
Webhooks push results straight into SAP, BI dashboards, custom middleware, or a ticketing system on award.
Every run logs the path taken — Fired · Passed · Done · Won't run — with node-level status and timestamp.
Connect Triggers, Conditions, Actions, and AI Agents into branching YES/NO logic — then apply the flow to any RFQ.
Start a flow when an RFX event closes, or when an RFQ is created programmatically via the intake REST API.
Branch on any RFx field against a threshold, or on intake source. YES / NO paths lead into different actions.
Auto-award according to the rule, or POST the result to any webhook — ERP, BI, ticketing, custom middleware.
Delegate analysis to a named agent with a custom prompt — weighting included. Email the owner or hand back for review.
Every execution shows node-level status — Fired · Passed · Done · Won't run — with a timestamp. Full audit trail per run.
Attach a flow to any RFQ, apply it retroactively, or trigger a manual run — from the flow header.
Follow one real tail-spend request end-to-end — from Intake submission, through auto-award of small RFQs, back into ERP as a PO.
An RFQ created via REST API has just closed. The flow attached to it starts executing automatically.
Different rules for system-created RFQs and manually created ones. This RFQ came via REST API — condition passes.
RFx total value under 600,000 EUR? Yes — this is tail spend, safe to auto-award. Above the threshold, the flow would branch to an AI agent instead.
Two actions run in sequence. PINPOOLS awards the lowest bid according to the rule, then fires a webhook with the award payload to the downstream system.
From intake to award to downstream update in seconds. If the RFQ had exceeded the threshold, the No branch would delegate analysis to an AI agent and email the RFQ owner — nothing gets lost.
It's a layer that sits on top of the PINPOOLS RFX engine. Every flow acts on real RFQs and Series Requests inside the platform — nothing lives outside it.
No — it’s a visual no-code builder. Buyers assemble triggers, conditions, actions, and AI agents by connecting nodes, without writing code.
Yes. The "Send result to external" action performs a POST to any webhook endpoint — SAP, custom middleware, BI tools, ticketing systems, etc.
Yes. Every flow has an Apply to this RFQ button and a Run now button. You can also apply a flow retroactively.
When conditions indicate an RFQ is too strategic to auto-award, the flow delegates to an AI agent that drafts a summary and awarding recommendation, then emails it to the RFQ owner. The human makes the final call.
Yes. The agent prompt supports free text, including weighting instructions like "pricing should count for 70%" alongside qualitative criteria.
Each flow shows the "Last run path on this RFQ" with per-node status (Fired · Passed · Done · Won’t run) and a timestamp. Complete audit trail per execution.
Guided Sourcing helps you create complex RFQs with AI assistance. Process Flow decides what happens after an RFQ closes — awarding, notifications, ERP updates, AI analysis. The two are complementary.
30 minutes. Bring one RFQ. Leave with a flow ready to run.
No-code · Fully auditable · Runs on your RFX policy