Business verification
A Connection node calls Creditsafe 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.
What a flow can call
/companiesSearches Creditsafe's global company database. Add countries=US or countries=BR and at least a registration number, tax number, or a precise name-plus-address query on the Connection node to avoid ambiguous matches.
/companies/$data.creditsafe_connect_idReturns a company report for a Connect ID found by Search companies.
/companies/schema/$data.creditsafe_country_codeRetrieves the available report schema for a two-letter country code, such as US or BR.
Provider documentation: https://doc.creditsafe.com/connect-apis-catalog/product-catalog/connect-api-full/connectapi/authentication
Where it sits in the decision
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 Creditsafe returned at the time is in the trace, not re-fetched from a service whose answer has since changed.
Ready when you are
Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.