Compliance
ComplyAdvantage in a decision flow.
A Connection node calls ComplyAdvantage 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
- Compliance
- Type
- Integration
- Authentication
- api_key
- Test environment
- Production host only
What a flow can call
3 operations, each one a step you can place on the canvas.
- POST
/searchesScreen a person
Creates a sanctions, PEP and adverse-media search for one applicant.
- GET
/searches/$data.complyadvantage_search_id/detailsRead a screening result
Fetches the complete result for a previous search, including matched entities and their sources.
- GET
/searchesList past screenings
Lists searches already made by the account. Filter and paginate with query parameters on the node instead of fetching the entire history.
Provider documentation: https://docs.complyadvantage.com/
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 ComplyAdvantage returned at the time is in the trace, not re-fetched from a service whose answer has since changed.
- 01Add ComplyAdvantage 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.
Inscribe
VouchedReady when you are
Wire ComplyAdvantage into a real decision.
Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.