Skip to the operations

Business verification

Middesk in a decision flow.

A Connection node calls Middesk mid-decision with the credentials your own contract issued. Whatever comes back is data the rest of the flow can read, branch on, and keep in the decision's trace.

Category
Business verification
Type
Integration
Authentication
api_key
Test environment
Production host only

What a flow can call

2 operations, each one a step you can place on the canvas.

  1. POST/v1/businesses

    Verify a business name and address

    Starts an asynchronous US business-verification order.

  2. GET/v1/businesses/$data.middesk_business_id

    Read a business verification

    Polls a business created by Verify a business name and address.

Provider documentation: https://docs.middesk.com/api-reference/business-verification/businesses/create-business

Where it sits in the decision

A provider call is a node, not a side effect.

The call runs where the policy needs it — after the cheap checks that might make it unnecessary, before the rules that depend on it. Calls that do not depend on each other run together rather than in sequence.

Because it is part of the run, the response is part of the record. When someone asks why an applicant was declined months later, what Middesk returned at the time is in the trace, not re-fetched from a service whose answer has since changed.

  • 01Add Middesk as a connection, with your credentials.
  • 02Place a Connection node and choose the operation.
  • 03Read the response in the rules, tables and branches that follow.
  • 04Test the whole path in Sandbox before it carries live traffic.

Also in Business verification

Ready when you are

Wire Middesk into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs