Lola Bureau icon

Lola Bureau

Lola Bureau Node
Join our community

Overview

The Lola Bureau node performs screening and validation checks on individuals against various lists, such as government blacklists (OFAC, Patriot Act, SDN), identity validation sources, and custom blacklists. It is useful in compliance, anti-money laundering (AML), and know-your-customer (KYC) workflows where you need to verify a person's identity or check if they appear on any watchlists before proceeding with further processing.

Practical examples:

  • Screening new customers during onboarding for financial services.
  • Verifying identities and checking sanctions lists before approving transactions.
  • Automating compliance checks for e-commerce or fintech platforms.

Properties

Name Meaning
Screening Lists Select which lists to screen against. Options: All Lists (*), Black Lists Screening (OFAC, Patriot Act, SDN, etc.), Validate Identity, Custom Blacklist. Multiple can be selected.
Fail Early If enabled, the node stops at the first failed check and does not continue to subsequent lists.
First Name First name of the person to search.
Last Name Family name of the person to search.
Date of Birth Date of birth in YYYY-MM-DD format.
Nationality Country 3-letter country code (e.g., USA, MEX) representing the person's nationality.
Address Street address of the person to search.
City City of the person to search.
State 2-letter state code of the person to search.
Zip Code Zip code of the person to search.

Output

  • The output is attached to the input item's json field under the key lola_bureau.
  • The structure of lola_bureau may include:
    • blacklists: Result object from blacklist screening (if selected).
    • identity_validation: Result object from identity validation (if selected).
    • custom_lists: An empty object if custom blacklist is selected.
  • Each result object typically contains a status field (e.g., "Success" or failure status) and a trackId.

Example output:

{
  "lola_bureau": {
    "blacklists": {
      "status": "Success",
      "trackId": "abc123"
      // ...other fields
    },
    "identity_validation": {
      "status": "Failed",
      "trackId": "def456"
      // ...other fields
    },
    "custom_lists": {}
  }
}

  • If "Fail Early" is enabled and a check fails, only the results up to the point of failure are included.

  • The node has two outputs:

    • Success output: Items that passed all selected screenings or did not fail early.
    • Rejected output: Items that failed a screening when "Fail Early" is enabled.

Dependencies

  • May require credentials named lolaKeyApi (optional, depending on configuration).
  • Relies on internal functions for blacklist screening and identity validation.
  • No explicit external API keys or environment variables are required unless configured in n8n.

Troubleshooting

Common issues:

  • Missing required fields: If "First Name" or "Last Name" is missing, the node will not function correctly.
  • Incorrect date format: "Date of Birth" must be in YYYY-MM-DD format.
  • Invalid country/state codes: Ensure correct 3-letter country and 2-letter state codes.
  • API errors: If the underlying screening service returns an error, the node may output a failure status.

Error messages:

  • "Blacklist Screening failed: <trackId>, since failEarly is true, it will not continue to the next list"
    Resolution: Check the input data and ensure the person is not on a blacklist; disable "Fail Early" to continue with other checks.
  • "Validate Identity failed: <trackId>, since failEarly is true, it will not continue to the next checkpoint"
    Resolution: Verify the provided identity information; disable "Fail Early" to proceed with other screenings.

Links and References

Discussion