Overview
This node connects to an n8n instance and retrieves information about credentials used across workflows. It helps users audit and analyze credential usage without requiring authentication to the n8n API.
Common scenarios include:
- Auditing which credentials are actively used in workflows.
- Identifying unique credentials to manage or rotate secrets.
- Grouping credentials by workflow for better organization and security reviews.
Practical example:
- A user wants to list all unique credentials IDs used in their n8n instance to ensure no unused credentials remain, improving security hygiene.
Properties
| Name | Meaning |
|---|---|
| n8n Base URL | The base URL of your n8n instance (e.g., http://localhost:5678). |
| Skip SSL Verification | Whether to skip SSL certificate verification, useful for local development with self-signed certificates. |
Note: The operation is fixed as "Get Unique Credentials" based on your selection, so it is not listed here as a property.
Output
The output JSON contains an array of objects, each representing a unique credential ID found across all workflows, along with its total usage count.
Example output item structure:
{
"credentialId": "string", // The unique identifier of the credential
"totalUsage": 5 // Number of times this credential is used across all workflows
}
If no credentials are found, the output will contain a message indicating no credentials were found, along with the total number of workflows scanned and the operation performed.
Dependencies
- Requires access to the n8n REST API endpoint
/rest/workflowson the specified base URL. - No authentication is required to fetch this data.
- Optionally skips SSL verification if enabled, useful for local or self-signed cert environments.
Troubleshooting
- Invalid response format from n8n API: This error occurs if the API response is not an array of workflows. Ensure the base URL points to a valid n8n instance and the
/rest/workflowsendpoint is accessible. - Failed to fetch credentials data: General failure to connect or retrieve data. Check network connectivity, correct base URL, and that the n8n instance is running.
- If using HTTPS with self-signed certificates, enable "Skip SSL Verification" to avoid SSL errors.
- If no credentials are found but you expect some, verify that workflows actually use credentials and that the n8n instance exposes them via the API.