Forecast cash positions using banking, invoice, and payment-schedule APIs

Description

Quick overview
This workflow exposes a POST webhook that gathers banking balances, outstanding invoices, and upcoming payment schedules via HTTP APIs, then combines the results into a day-by-day cash-position forecast (optionally including FX enrichment) and returns the forecast JSON with a data-source status audit trail.

How it works
Receives a cash-forecast request via a POST webhook.
Validates the request inputs (such as horizon days and base currency) and prepares the endpoint URLs and parameters used for downstream API calls.
Calls a banking API over HTTP to retrieve current balances and recent transaction context for the requested accounts.
Calls an accounts-receivable API over HTTP to retrieve outstanding invoices and expected collection timing within the forecast horizon.
Calls a payment-schedules API over HTTP to retrieve upcoming outflows (such as AP, payroll, taxes, and recurring payments) and optionally calls an FX/enrichment API.
Aggregates the collected data into a daily cash-position projection, computes summary metrics, and returns the forecast as the webhook response with an HTTP status that indicates full or partial data availability.

Setup
Configure the webhook endpoint in the calling system by copying the production webhook URL for the cash-forecast path and sending forecast requests to it via POST.
Replace the placeholder httpbin.org URLs with your real banking, invoicing/accounts-receivable, payment-schedule, and (optional) FX API endpoints.
If your APIs require authentication, add the necessary credentials/headers (for example OAuth2 or API keys) in the HTTP requests.
Adjust defaults such as base currency, timeout, and forecast horizon (and align request body fields like accounts, asOfDate, and horizonDays) to match your data sources’ schemas.