Connections guide for Make.com

In this step-by-step guide, you will learn how to create, manage, and secure connections in make.com so your scenarios can access external apps, services, and data safely.

Connections are the bridge between modules in a scenario and the services they work with. Understanding how they behave, where they are stored, and how to configure them is essential for building reliable automations.

What is a connection in Make.com?

A connection in make.com is the saved authentication that lets a module communicate with another app or service. When you add a module that requires access to an external system, you must either create a new connection or reuse an existing one.

Connections can be based on many authentication methods, depending on the service:

• API tokens
• OAuth authorization
• Username and password
• Custom credentials such as keys or secrets

Once created, a connection is available for reuse in any other module that uses the same app or service, as long as you have the required permissions in the organization and team.

How to create a new connection in Make.com

You normally create a new connection while building or editing a scenario. The exact process depends on the app you are connecting to, but the high-level steps are similar.

Step-by-step: create a connection in Make.com

1. Open the scenario editor and add a module for the app or service you want to use.

2. Click the module to open its configuration panel.

3. Locate the Connection field and click Add or New connection.

4. A new window or panel appears. Follow the prompts to authenticate. This may involve:

   • Signing in to the app in a popup window
   • Entering an API key or token
   • Approving requested permissions

5. Give the connection a clear name so you can recognize it later, then save.

After saving, the module uses the new connection. The same connection will also appear in the connection list for that service when configuring other modules.

Managing existing Make.com connections

You can manage all your existing connections directly from the connection overview of make.com. This allows you to rename, delete, or update them without opening a specific scenario.

Access the connections overview in Make.com

1. Sign in to your make.com account.

2. Open the Connections section using the workspace navigation (as documented on the official help page at https://help.make.com/connections).

3. You will see a list of all connections available to you, usually grouped by app or service.

From here you can quickly review which accounts are linked, when they were created, and whether any require attention.

Rename or update a connection in Make.com

To keep your workspace clear, give connections meaningful names and update them when something changes on the service side.

1. Find the desired connection in the list.

2. Use the available actions (for example, an edit or pencil icon) to open its details.

3. Update the connection name so it reflects the service, environment, or owner.

4. If prompted, reauthorize or refresh credentials, then save.

Renaming or refreshing an existing connection will not normally break your scenarios, as they will continue pointing to the same underlying connection object.

Delete a connection in Make.com

When a connection is no longer needed, you can remove it. Be cautious, because deleting a connection used in scenarios may cause errors.

1. Open the Connections section.

2. Locate the connection you want to delete.

3. Use the delete or trash option and confirm the removal.

After deletion, any scenario using that connection will fail until you select a new valid connection in each affected module.

Reusing connections across Make.com scenarios

One of the advantages of make.com is the ability to reuse the same connection in multiple modules and scenarios. This avoids repeated authentication steps and keeps configuration consistent.

When you open a module with a Connection field, you can:

• Select an existing connection from the drop-down list
• Create a new connection if none of the available options fit

Reusing connections is particularly helpful when you:

• Maintain standard accounts for integrations (for example, a shared CRM account)
• Need consistent access rights across several scenarios
• Want a single place to refresh credentials when passwords or tokens change

Security and ownership of Make.com connections

Connections in make.com are tied to users, organizations, and teams. The exact visibility and sharing behavior depends on how your workspace is structured.

Some key security principles include:

• Personal scope: Many connections belong to the user who created them and are only available in contexts where that user has access.
• Organizational rules: Depending on your plan and configuration, administrators may control which users can create or manage certain connections.
• Token storage: Authentication data is stored securely so that modules can run even when you are not actively logged in.

If your organization has strict security requirements, regularly audit connections, revoke those that are not needed, and update any that rely on rotated credentials or expired tokens.

Best practices for secure connections in Make.com

• Use dedicated integration accounts where possible instead of personal accounts.
• Grant only the minimal required permissions when authorizing connections.
• Periodically review the Connections list and remove unused items.
• Immediately revoke and recreate connections if an API key, password, or token is compromised.

Troubleshooting Make.com connection issues

When a module fails, connection problems are a common cause. Typical symptoms include authorization errors, permission denials, or expired credentials.

Checklist to fix a failing connection

1. Open the scenario and identify the module that failed.

2. Check the error details shown in the execution log or module bubble.

3. If the error mentions authorization or permissions, open the module configuration.

4. Verify the selected connection and test it, if the app provides a test button.

5. If the test fails, return to the Connections section and reauthorize or recreate the connection.

6. Run the scenario again to confirm the issue is resolved.

When errors persist, review the documentation for the specific app module you are using, as some services require extra configuration such as whitelisting IP addresses or enabling APIs.

Advanced tips for working with Make.com connections

Beyond basic creation and management, you can adopt a few advanced practices to keep your workspace organized and scalable.

• Naming conventions: Include the service, environment (for example, production or sandbox), and owner in the connection name.
• Environment separation: Create separate connections for test and live systems to avoid accidental changes in production.
• Documentation: Maintain an internal document listing which scenarios depend on each key connection, so you know what will be affected when you change it.

For broader automation strategy and optimization beyond connections, you can also explore expert resources such as Consultevo, which focuses on automation and integration consulting.

Next steps

You now know how connections work in make.com, how to create them in scenarios, manage them from the connection overview, reuse them safely, and troubleshoot common issues. Apply these practices as you build new automations and review your existing scenarios to ensure that every module relies on secure, well-maintained connections.

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.

Get Help