Actions30
- Company Actions
- Company (Related) Actions
- Data (Advanced) Actions
- Enrich Actions
- Live Web RAG Actions
- LLM Template Actions
- Other Data Actions
- Validation & Cleansing Actions
Overview
This node interacts with the Bedrijfsdata API to retrieve various types of miscellaneous data, including checking if a password has been leaked before. Specifically, the "Get Password Leaks" operation allows users to query the API with either a plaintext password or its SHA1 hash to find out how many times that password has appeared in known leaks.
This functionality is useful for security audits, user account management, and risk assessment scenarios where you want to verify if a password is compromised. For example, before allowing a user to set a new password, you could check it against this service to prevent usage of commonly leaked passwords.
Properties
| Name | Meaning |
|---|---|
| Password | (Optional) Enter a plaintext password to scan for leaks. |
| Password (SHA1) | (Recommended) Enter the SHA1 hashed version of the password to scan for leaks. |
Note: The node supports providing either the plaintext password or its SHA1 hash as input. Using the SHA1 hash is recommended for privacy reasons.
Output
The node outputs JSON data containing the results from the Bedrijfsdata API's password leak endpoint. This typically includes information such as:
- The number of times the password was found in leaks.
- Possibly metadata about the leaks or breach sources.
The exact structure depends on the API response but generally provides counts and details about password exposure.
No binary data output is involved in this operation.
Dependencies
- Requires an active API key credential for the Bedrijfsdata API.
- The node makes HTTP GET requests to
https://api.bedrijfsdata.nl/v1.2/passwordwith query parameters for the password or its SHA1 hash. - No additional environment variables are needed beyond the API authentication setup.
Troubleshooting
- Empty or missing password inputs: If neither password nor password SHA1 is provided, the API request may return an error or no results. Ensure at least one is supplied.
- API authentication errors: Verify that the API key credential is correctly configured and valid.
- Unexpected API responses: Network issues or changes in the Bedrijfsdata API might cause errors. Check the error message returned by the node for clues.
- Password hashing: If using the SHA1 option, ensure the hash is correctly computed; otherwise, the lookup will fail or return incorrect results.
Links and References
- Bedrijfsdata API Documentation (general reference for the API)
- Have I Been Pwned - Password Leak Checking Concept (similar public service concept)
This summary is based solely on static analysis of the provided source code and property definitions.