Connect to the systems
you already run.
NodeFox reaches your systems through their APIs, files and webhooks, and calls the model providers you choose. Each system of record is connected for the workflow that needs it.
Read the evidence. Approve the action. Carry the result forward.
01 · File intake
INV-2048.pdf
Reader receives 240 units at $18.
02 · Read access
PO-7301 + GR-918
Configured API or export returns 228 received units.
03 · AI + code
$4,104 supported · $216 held
Extract the fields, then match IDs and quantities exactly.
04 · Human approval → scoped write
Prepare the AP record
The reviewer releases this action. Payment authorization is separate.
- invoice_id
- INV-2048
- supported_amount
- 4104.00
- held_amount
- 216.00
- receipt_ref
- GR-918
- payment_authorized
- false
Writer → agreed AP endpoint or file. The run record retains the configured inputs and result.
Synthetic payload. Confirm endpoint access, credentials, record freshness and duplicate handling before enabling writes.
Connect a process, not just two applications.
Prepare an invoice for AP
Microsoft 365 intake → SAP purchasing / receipt data → AP review
Extract the invoice, retrieve purchase and receipt records, apply matching rules and carry the approved result to the accounting boundary.
Give a service team a complete handoff
Salesforce or HubSpot → approved document store → Jira or ServiceNow
Match the customer, check the required information and prepare an owned task with the source records attached.
Prepare a cross-system investigation
Snowflake or Databricks export → order records → reviewer report
Read an agreed dataset through supported access, reconcile identifiers and calculations, and prepare evidence for an accountable decision.
Validate API availability, licensing, scoped credentials, network access and duplicate handling for each system. A compatible MCP service can provide tools in the supported browser/gateway path; it does not make every vendor operation automatically available.
Through the access your systems already offer.
ERP, CRM, WMS and TMS platforms connect through configured APIs or exports. These patterns are scoped to the workflow; they are not prebuilt vendor connectors.
APIs
Files
Watched folders and webhooks
Code
| Approach | Good for | Browser | Headless |
|---|---|---|---|
| API stepsSystems with an HTTP API | Systems with an HTTP API | ✓ | ✓ |
| FilesExports, spreadsheets and documents | Exports, spreadsheets and documents | ✓ | ✓ |
| Watched folderFiles another system drops | Files another system drops | — | ✓ |
| WebhookEvents your systems push | Events your systems push | — | ✓ |
| Code (JavaScript)Custom parsing and logic | Custom parsing and logic | ✓ | ✓ |
| MCP and OAuth servicesTools and connected accounts | Tools and connected accounts | ✓ | Not yet |
What needs to be ready for a connection?
- API and credential access
- Agree the permitted reads and writes. Browser requests need a reachable endpoint and compatible CORS policy; credentials used in the browser are exposed to that client environment. Choose supported headless execution when the process needs machine-side access.
- Tools and connected accounts
- MCP and OAuth use the supported browser/gateway path. Confirm the tool operations and account scopes; these connections do not carry over automatically to headless runs.
- Database and file handoffs
- Use an authorized API, query service or agreed export for database records. Define stable record IDs, accepted formats and duplicate handling before enabling downstream writes.
Accounts and tools, in the browser.
Authorize an account once and use it in browser runs, or connect MCP servers as tools for a step. Neither is available headless yet.
- Microsoft
- Slack
- Notion
- Atlassian
- Dropbox
- GitHub
- Linear
Your provider, your keys.
Model requests go directly to the provider you configure. Headless runs can also call a custom endpoint.
- Gemini
- OpenAI
- Anthropic
- xAI
- Mistral
Name the systems. We’ll map the access.
Bring the systems your workflow touches and how each one is reached today.