Overview
This node lists credentials used across n8n workflows. It helps users identify which credentials are in use, grouped either by workflow or as a unique set. This is useful for auditing, managing, or cleaning up credentials in an n8n instance.
Common scenarios include:
- Auditing all credentials currently used in workflows.
- Listing credentials grouped by each workflow to understand credential usage per workflow.
- Getting a unique list of all credentials used across all workflows to identify duplicates or unused credentials.
For example, a user might want to see all credentials used in a specific workflow or get a comprehensive list of all credentials used in their automation environment.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform: - List All Workflow Credentials - List Credentials by Workflow - Get Unique Credentials |
| Include Workflow Details | Whether to include the workflow name and ID in the output (boolean). |
| Include Node Details | Whether to include the node name and type that uses the credential (boolean). |
Output
The output is an array of JSON objects representing credentials information depending on the selected operation:
List All Workflow Credentials: Outputs each credential usage with fields such as
credentialId,credentialType, optionallyworkflowId,workflowName, and if enabled,nodeNameandnodeType.List Credentials by Workflow: Outputs grouped data by workflow, where each item contains:
{ "workflowId": "...", "workflowName": "...", "credentials": [ { "credentialId": "...", "credentialType": "...", "nodeName": "...", // optional "nodeType": "..." // optional } ] }Get Unique Credentials: Outputs unique credentials across all workflows, each with:
{ "credentialId": "..." }
No binary data is output by this node.
Dependencies
- Requires an API key credential to authenticate requests to the n8n REST API.
- The node makes authenticated GET requests to the
/rest/workflowsendpoint to retrieve workflow and credential data. - Proper permissions to access workflow data via the API are necessary.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Insufficient permissions to access workflow data.
- Empty results if no workflows or credentials exist in the system.
Error messages:
- Errors returned from the API will be caught and included in the output if "Continue On Fail" is enabled.
- Typical error message:
"Unknown error"or the actual error message string from the API response.
Resolutions:
- Verify the API key credential is correctly configured and has required permissions.
- Ensure workflows exist and contain nodes with credentials assigned.
- Enable "Continue On Fail" to handle errors gracefully during batch processing.