Integration — pick a provider
Data Provider lists the providers connected in Data Sources. Output Variable names where the result lands (vars.<name>.*).
Node settings
Each provider declares its own inputs: a dataset picker (for example Risk Score or Person Data on the Frayme provider; Individual (KYC) or Business (KYB) on Sumsub) and fields such as document number or verification level. Any field can be switched to an expression binding (input.document_number) with the ƒx button.
Node outputs
The fields the provider returns for the chosen dataset, referenced downstream asvars.<output variable>.<field>. The list follows the inputs: pick a different dataset and it changes.
Keep monitoring
When on, the provider keeps watching the subject after the case is decided and, on a finding, opens a new case on the Workflow to run on a finding you choose. The section appears only for providers that emit monitoring signals (Chainalysis today), so it is absent on the Frayme mock provider used in these screenshots.Screenshot pending until a monitoring-capable provider is connected to the capture tenant.
Webhook notify
Posts a notification to a Webhook config when the node runs, with the provider’s payload type, optional lifecycle events and a kebab-case Tag.HTTP Request
Method, URL, Headers, Body (with${...} interpolation), Output variable, Timeout (s) and Retry count. Turn on Async callback mode when the remote system answers later: pick the Webhook config it will post back through and map callback fields to outputs.
Send RFI
Sends an information request from the flow using a Template from Settings → Communication. The request id lands in Output variable (defaultrfi). Delivery goes through the communication webhook exactly as when an analyst sends one.