Procurify

In flight

The Procurify connector ships with the Conversational FP&A recipe build. This page is a stub of the planned spec — file an issue if you need it sooner.

Connect to Procurify to import purchase orders, PO status, and committed spend. Approved POs in Procurify represent commitments that haven't yet hit the ERP — Agentcy surfaces them as a distinct committed spend layer in forecasting views.

Setup

1. In Procurify, navigate to Settings → Integrations → API.
2. Generate an API key with read access to purchase_orders, requisitions, vendors, and budgets.

Configuration

curl -X POST $API/api/v1/sources \
  -H "authorization: Bearer $TOKEN" -H 'content-type: application/json' \
  -d '{
    "name": "procurify-prod",
    "connector": "procurify",
    "realm": "fin-master",
    "config": {
      "api_key": "…",
      "include_pending_pos": false,
      "include_approved_pos": true
    }
  }'

Field	Type	Required	Description
api_key	secret	Yes	Procurify API key.
include_approved_pos	bool	No	Default true. The recipe needs this for the committed-spend layer.
include_pending_pos	bool	No	Default false. Enable only for forecasting visibility into the funnel.

Tools (planned)

• procurify.list_purchase_orders(status, date_range)
• procurify.get_po(id)
• procurify.get_committed_spend(period, department)
• procurify.list_vendors()

Three-layer view

The FP&A recipe combines:

• Actuals (NetSuite)
• Committed (Procurify approved POs not yet booked)
• Budget (Excel or NetSuite budget)

The agent surfaces these as separate columns in any spend view — never folds Committed into Actuals silently.

Used by

• Recipe: Conversational FP&A