Leitet Ausgabenanfragen aus Formularen, ERP und Slack nach Betragsgrenzen an Genehmiger weiter

## Route spend requests to approvers by threshold with deputies, reminders and escalation Who it is for. Any company where purchase and expense approvals live in chat threads and nobody can say who approved what. What it does - A request arrives from a form, the ERP or Slack. The policy picks the tier by type and amount: under the threshold approved automatically, then manager, director, CEO. - Checks who is out of office and routes to the named deputy. A requester can never approve their own request; it escalates instead. - Sends the request to the approver and tells the requester where it went and why. - A decision callback is validated: only the current approver can decide, and only once. Anyone else gets a 409. - An hourly sweep escalates anything past the SLA and logs it. Setup 1. Edit the policy table (tiers, thresholds, deputies, SLA) in Config. 2. Set base or replace the HTTP Request nodes with your HR (out of office), Slack or email and ERP nodes. 3. Point your request form at approval-in and your approve or reject buttons at approval-decision. Activate; the hourly schedule runs the sweep. All external systems are reached through HTTP Request nodes against base in the Config node, so the whole flow imports and runs against any REST backend; swap any of them for the native n8n node of your system. Built and tested on sample data by Finamatik: https://finamatik.com/work/approval-workflow Requirements. n8n 1.100 or later; for the AI steps, a model endpoint at base/llm/complete or the OpenAI or Anthropic node in its place; your own systems reachable over HTTPS. How to customise. Every rule lives in one Code or Config node and is named for what it decides; change the thresholds there, not in the branches.