Read Authorization
Read Authorization checks whether a customer has signed a specific authorization and routes accordingly. No message goes to the customer — it evaluates silently and branches TRUE or FALSE.
What It Checks
The node looks up the borrower's authorizations (see Authorizations API) and applies conditions in sequence. All must pass for TRUE:
- Does an authorization with the specified key exist?
- If check signed is enabled, does it have a signature?
- If an age limit is set, is it recent enough?
Any check fails, FALSE.
When to Use It
Before requesting consent. A returning customer shouldn't re-sign terms they agreed to last week. Check first, skip the consent flow if already signed.
Compliance gates. Ensure required authorizations exist before proceeding to sensitive operations.
Re-authorization flows. With age limits, check whether old signatures need renewal.
Configuration
| Option | Description |
|---|---|
| Authorization Type | The key identifying which authorization to look for (credit_bureau_consent, terms_and_conditions, etc.) |
| Check Signed | Require an actual signature, not just existence |
| Authorization Age | Max age since the record was created (minutes, hours, or days) |
| Signature Age | Max age since it was last signed (minutes, hours, or days) |
| Selected Variable | Stores the authorization object for later use |
Output Handles
| Handle | When |
|---|---|
| TRUE | Authorization exists and passes all checks |
| FALSE | Missing, unsigned, or too old |
Prerequisites
The conversation must be authenticated — Login or Create Borrower must have run first. The authorization type must exist in the tenant's data model; referencing a nonexistent key routes FALSE, not error.