Skip to the catalogue

Integrations

Your providers, called from inside the decision.

A Connection node calls the services you already have contracts with, mid-decision, using your own credentials. The response lands in the flow as data any rule can read — no glue service in between.

55providers
16categories
260operations

Compliance

Screening and document checks for the parts of a decision a regulator will ask about.

Messaging

Notify a person or a channel as part of the decision, not after it.

Banking

Read balances, transactions and income where affordability has to be evidenced rather than assumed.

AI

Model providers for the judgment a table cannot express.

Business verification

Confirm a company exists, who controls it, and whether its filings support the application.

Identity verification

Prove the applicant is who they claim before anything downstream trusts the input.

Business data

Accounting and financial data for decisions about a company rather than a person.

CRM

Write the outcome back to where the commercial team already works.

Credit Bureaus

Pull a credit file mid-decision and score it against your own policy, not the bureau's.

Research

Open-web lookups for the context that is not in any structured feed.

Address verification

Resolve and validate an address before it becomes a field in a credit file.

Developer tools

Turn repository activity and delivery automation into inputs and actions a decision flow can inspect.

Fraud prevention

Device and behavioural signals for the decisions that are contested rather than assessed.

Integrations

Productivity

Create and update the operational work that a decision puts in motion.

Reference data

Lookup tables and policy parameters someone maintains outside the flow.

How a connection works

Your contract, your credentials, your call.

ArboRule does not resell provider data and does not sit between you and your vendor. You add a connection with the credentials your contract issued, and a flow decides which calls to make, in what order, and what the answers mean together.

Because the call happens inside the decision, the response is part of the record: what was asked, what came back, and which branch it sent the applicant down are all in the same trace.

  • 01Add the connection once, with your own credentials, scoped to the workspace.
  • 02Drop a Connection node into a flow and pick the operation it should call.
  • 03Map the response into the fields your rules read, and branch on them.
  • 04The call, its response and the path it produced are kept with the decision.

Ready when you are

Bring the providers you already pay for.

Build the flow in Sandbox, wire your connections, and watch a real decision pull what it needs before it answers.

See what teams build