I need to rotate credentials for an integration, and creating a new API key is the first step.

This feature supports credential rotation for an existing integration by guiding you through creating a new API key as the first step. It helps you transition to fresh credentials with minimal disruption to the integration’s connectivity.

This feature focuses on the first step of rotating integration credentials: creating a new API key. It is intended for situations where you need to replace existing credentials due to security policy, scheduled rotation, or suspected exposure. By generating a new key first, you can prepare the updated credential before switching the integration over, which helps reduce downtime risk. The new API key can then be applied to the integration configuration in a controlled manner. This approach also supports parallel validation, allowing you to test that the new key works before retiring the old one. Rotating credentials in this way improves security hygiene and reduces the blast radius of compromised credentials. It is useful for teams that must meet compliance requirements or internal security standards that mandate periodic credential changes. It also helps administrators respond quickly when access needs to be resecured without rebuilding the entire integration. Overall, the feature provides a clear starting point for a safe, repeatable credential rotation workflow.