Audit workflow credential usage to Google Sheets using Google Drive and SQLite3

Workflow Introduction

This workflow is specifically for Self-Hosted N8N Docker users.

The purpose of this workflow is to: 1. Take an inventory of all workflows with credentials (Workflow -> Credential 1, Credential 2, etc.), connecting credential names to workflow names 2. Create a credentials impact map (Credential -> Workflow 1, Workflow 2, etc.), connecting workflow names to credential IDs and names

This workflow drastically minimizes the amount of time spent trying to figure out which workflows will break if a credential is updated or deleted by bridging the gap between the public API (workflow metadata) and the internal sqlite database (hidden version labels and credential mappings).

In essence this tool audits your n8n environment without touching your sensitive encrypted data, keeping you API Keys 100% secure.

It features dynamic time saving trackers, set for what I estimate to be the amount of time it would take to manually complete every individual thing this workflow does in less than 5 minutes.

Limitations This workflow is optimized for the Standard N8N Execution Mode. Due to the high-frequency data lookups required for this tool, it is not compatible with Task Runners (N8NRUNNERSENABLED=true). For maximum stability and to prevent "Database Locked" errors, please ensure your instance is running in the default configuration.

If you use Method 1 (Direct Insertion) in the API Key Instructions below your N8N API key will not appear as connected to this workflow in the resulting Credential Impact Map. Same goes for all other credentials directly inserted into a HTTP Request node across your N8N environment.