Actions31
- 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 integrates with the Bedrijfsdata API to retrieve various types of miscellaneous data, including checking if a password has been leaked before. The "Get Password Leaks" operation allows users to query the API with either a plain password or its SHA1 hash to find out how many times that password has appeared in known leaks.
Practical scenarios include:
- Security audits where you want to verify if user passwords have been compromised.
- Integrations in workflows that enforce password strength and safety by checking against leaked password databases.
- Automated alerts for users when their passwords are found in leaks.
Properties
| Name | Meaning |
|---|---|
| Password | (Optional) Enter a plain text password to scan for leaks. |
| Password (SHA1) | (Recommended) Enter the SHA1 hashed version of the password to scan for leaks. |
The node accepts either the plain password or its SHA1 hash as input query parameters. Using the SHA1 hash is recommended for security reasons.
Output
The output JSON contains the response from the Bedrijfsdata API's /password endpoint. This typically includes information about the number of times the given password or hash was found in leaks.
The exact structure depends on the API response but generally includes fields such as:
- Count or frequency of leaks
- Possibly metadata about the leak sources or dates
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/password. - No additional environment variables are needed beyond the API authentication setup.
Troubleshooting
- Empty or no results: If neither password nor password_sha1 is provided, the API may return no data or an error. Ensure at least one property is set.
- API errors: Network issues or invalid API keys will cause request failures. Verify your API credentials and network connectivity.
- Security caution: Avoid sending plain text passwords unless necessary; prefer using SHA1 hashes to protect sensitive data.
- Unexpected API responses: If the API changes or returns unexpected data, the node might throw errors. Check the API documentation and update the node accordingly.
Links and References
- Bedrijfsdata API Documentation (general reference for endpoints)
- Have I Been Pwned - Password Leak Database (conceptual background on password leak checks)
This summary is based solely on static analysis of the provided source code and property definitions.