How to Manage API Keys in Make.com
This guide explains step by step how to create, view, secure, and revoke API keys in make.com so you can safely connect external apps and services to your scenarios.
What are API keys in Make.com?
In make.com, an API key is a unique token that authorizes external tools to access your organization via the Make API. It works like a password for integrations, so each key must be handled with great care.
API keys allow you to:
- Authenticate calls to the Make API.
- Automate tasks from external systems.
- Control and revoke access when needed.
The API key is always tied to the user who created it and to a specific organization in make.com.
Accessing the API keys page in Make.com
Before you can generate or manage API keys, you need to open the dedicated page in the make.com interface.
Steps to open the API keys section in Make.com
- Sign in to your make.com account.
- In the upper-right corner, click your avatar.
- From the dropdown menu, choose the organization in which you want to work.
- Click Profile.
- In the left-hand menu, select API keys.
This page lists all API keys created under your selected organization and user in make.com.
How to create a new API key in Make.com
To let an external app communicate with your scenarios, you need to create a new key in make.com. Each app or integration should have its own key for better control and security.
Step-by-step: Create an API key in Make.com
- Navigate to the API keys section as described above.
- Click the + Add API key button.
- Enter a clear name for the key. Use a descriptive label, such as the system or project that will use it.
- Click Save.
- After saving, a dialog appears showing the newly generated key value.
Important: This is usually the only time you will see the full value of the key in make.com. Copy it and store it securely right away.
Viewing and copying API keys in Make.com
The API keys list in make.com displays basic information about each key you have created.
For each API key you can see:
- Name – the label you set when creating the key.
- Creation date – when the key was generated.
- Last used – when the key was last used to access the Make API.
The actual secret value of the key is shown only once, immediately after creation. If you lose it, you cannot reveal it again in make.com; instead, you must generate a new key and update any integrations using the old one.
Best practices when copying keys from Make.com
- Paste the key directly into the configuration of the external tool that needs access.
- Store a backup copy in a secure password manager.
- Never send the key over unsecured channels such as email or public chat.
How to use Make.com API keys securely
Correct use of keys in make.com is essential for protecting your data and automations from unauthorized access.
Security tips for Make.com API keys
- Keep keys secret: Treat every key like a password. Do not share it publicly or embed it in client-side code.
- Use separate keys: Create different keys for different systems or projects to simplify troubleshooting and revocation.
- Rotate keys regularly: Periodically revoke and recreate keys to reduce long-term exposure.
- Monitor “Last used”: In make.com, check the last used column to detect inactive or suspicious keys.
If you suspect any key has been exposed, revoke it immediately and replace it with a new one.
Revoking an API key in Make.com
Revoking a key in make.com instantly blocks that token from accessing the Make API. This is the main way to cut off access for a compromised or unused integration.
Steps to revoke an API key in Make.com
- Open the API keys page for your organization.
- Locate the API key you want to revoke.
- Click the trash bin icon next to that key.
- Confirm the action when prompted.
After revocation, any external system that relied on that key will fail to authenticate and must be updated with a new key from make.com.
Troubleshooting common issues with Make.com keys
If your integration suddenly stops working, the problem may be related to the status or value of your key in make.com.
Typical problems and solutions
- Authentication errors: Verify the key is correctly copied, has no extra spaces, and has not been revoked.
- Key not found: If you cannot see a key in make.com, it might have been created under another organization or user profile. Switch organizations from your avatar menu and check again.
- Lost key value: If you did not store the key when it was shown, you must create a new one and replace it everywhere it is used.
Where to learn more about Make.com API keys
For deeper technical details about the Make API, rate limits, and authentication, consult the official documentation:
If you need expert help designing secure integrations, automation architecture, or LLM-based workflows around make.com, you can also reach out to specialized consultants:
By following the steps in this guide and applying these security best practices, you can confidently manage API keys in make.com, keep your automations secure, and maintain full control over which systems have access to your organization.
Need Help With Make.com?
If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.