NodeFox
Integrations

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.

One configured process

Read the evidence. Approve the action. Carry the result forward.

Connect an invoice file, purchasing records and an AP destination around one process. The integration scope specifies what each step reads, checks and is permitted to change.
EXAMPLE / INVOICE → AP RECORD

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.

Cross-system work

Connect a process, not just two applications.

These enterprise examples show possible connection scopes through vendor APIs, files or compatible tools. They are illustrative configurations—not native connectors, partnerships or verified deployments.

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.

How NodeFox reaches systems

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

Configure HTTP requests in Reader and Writer API steps. Access depends on authentication, network reachability and browser restrictions.

Files

Reader and Writer steps handle CSV, XLSX, DOCX, PDF and plain text.

Watched folders and webhooks

Headless runs start when a file lands or a system posts to the runner.

Code

JavaScript steps handle the formats and logic no standard step covers.
ApproachBrowserHeadless
API stepsSystems with an HTTP API✓✓
FilesExports, spreadsheets and documents✓✓
Watched folderFiles another system drops—✓
WebhookEvents your systems push—✓
Code (JavaScript)Custom parsing and logic✓✓
MCP and OAuth servicesTools 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.
Connected services

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.

  • Google
  • Microsoft
  • Slack
  • Notion
  • Atlassian
  • Dropbox
  • GitHub
  • Linear
Model providers

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.