Create a job requisition via the ATS API (e.g., Greenhouse Harvest POST /v1/jobs) with fields for title, department, headcount, and hiring manager
Set the job status to 'draft' and trigger an approval workflow by calling the ATS approval endpoint or by updating a custom 'approval_status' field
Notify approvers (typically finance and department heads) via your notification system with a link to the requisition; capture approval responses via a callback URL or by polling a status field
Once all approvals are recorded, update the job status to 'open' via the ATS API to make it available for posting and sourcing
Log each approval action with approver identity, timestamp, and decision in an audit trail stored as job notes or in an external audit log
Known gotchas
Not all ATS platforms expose a native requisition approval API; if native support is absent, approval state must be managed in an external system and synced back to the ATS via custom fields
Approval chains with conditional logic (e.g., salary above a threshold routes to CFO) must be modeled explicitly; a simple sequential list of approvers will not handle branching conditions
If an approver rejects and the requisition is revised, re-approval from all prior approvers may be required by internal policy; ensure your workflow can reset the approval chain on edit
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp