How do I connect Fingerprint to a decision flow?
Add Fingerprint as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Fingerprint in a decision without ever seeing the secret.
Can I test Fingerprint without touching production?
Fingerprint exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.
What can a flow call on Fingerprint?
2 operations: “Read device-intelligence event”, “Flag a device event as suspicious”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Read device-intelligence event”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.
Where in a decision should Fingerprint be called?
Device and behavioural signals are contested rather than assessed — the applicant is actively trying to affect the answer. They are cheap enough to call on every event and most useful combined with history, so they usually sit alongside an entity read rather than on their own.