We need to rotate an API key, but 30 flows use it and can't go down

Hard-coded keys in individual flow steps make rotation painful. The trick is a central secret store with aliases, and an overlap period where old and new both work.

Try this first

1. 1Centralise secrets in a vault: 1Password Secret Automation, Bitwarden Secrets Manager, Azure Key Vault, AWS Secrets Manager, or n8n credentials / Zapier auth-store.
2. 2Make sure the source API allows two active keys at once. Stripe, HubSpot and Mollie support it, some don't, check the docs.
3. 3Add the new key in the vault under the same alias or as a new version. Update flows to the new version and monitor 24h for errors.
4. 4Only when all flows run on the new key, deactivate the old in the source API. Document date and operator.
5. 5Schedule rotation as a standard quarterly or yearly calendar item, not just reactive after a leak.

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.