What If I Rotate or Revoke an API Key?
API tokens may need to be rotated or revoked periodically for security reasons. Here’s what to do if you update your Zendesk, Jira, or Slack API keys so ZenSync keeps working smoothly.
Why Rotate or Revoke API Keys?
- Security best practice: changing tokens regularly reduces risk
- If you suspect a key has been compromised
- When a team member with access leaves or changes roles
How to Update Your API Keys with ZenSync
- Generate a New API Token
- Follow our guides to create a new token for Zendesk, Jira, or Slack as needed.
- Follow our guides to create a new token for Zendesk, Jira, or Slack as needed.
- Send Your New Token to ZenSync
- Use our secure onboarding form or email support@zensync.co with the updated credentials.
- Use our secure onboarding form or email support@zensync.co with the updated credentials.
- We’ll Update Your Automation
- Once we receive your new key, we’ll promptly update your scenario on Make.com and test to confirm everything works.
- Once we receive your new key, we’ll promptly update your scenario on Make.com and test to confirm everything works.
- Confirm Activation
- We’ll notify you when your updated credentials are live.
- We’ll notify you when your updated credentials are live.
Important Tips
- Don’t revoke the old token until you confirm the new one is working — this avoids downtime.
- If you revoke a token before updating us, your automation will stop until the new token is provided.
- Always keep a secure copy of your tokens; you won’t be able to retrieve them after creation.
Need Help?
If you’re unsure about rotating keys or want assistance, just reach out via our Support Page or email us directly at support@zensync.co — we’re here to help.