How to Set Up the Make.com On-Premise Agent

The Make.com On-Premise Agent lets you run secure data processing inside your own infrastructure while still using the Make.com platform in the cloud. This guide explains how to install, configure, and manage the agent step by step so you can safely connect private systems to your automations.

What the Make.com On-Premise Agent Does

The On-Premise Agent is a lightweight service you install in your local network or private cloud. It creates a secure communication channel between Make.com and resources that are not directly accessible from the internet.

With this agent, Make.com scenarios can:

• Access internal APIs, databases, or services that sit behind a firewall.
• Process sensitive data without exposing internal systems publicly.
• Communicate over outbound connections instead of opening inbound ports.
• Comply with security and governance requirements in your organization.

The agent works as a bridge only; it does not replace the main Make.com platform, which still runs in the cloud.

Prerequisites for Make.com On-Premise Installation

Before you deploy the On-Premise Agent, prepare the following in your environment and Make.com account.

System and Network Requirements for Make.com Agent

• A supported operating system (for example, a recent Linux distribution or compatible server OS).
• System user permissions to install and run services or Docker containers, depending on the chosen deployment method.
• Outbound internet connectivity from the server to the Make.com platform over HTTPS (typically port 443).
• Ability to allow the agent host to reach the Make.com endpoints required for secure communication.

Account and Access in Make.com

• An active Make.com account with rights to manage organization and project settings.
• Permissions to create an On-Premise Agent configuration within the Make.com interface.
• Access to the On-Premise Agent configuration page at the official Make.com On-Premise Agent documentation for reference.

Download and Install the Make.com On-Premise Agent

The agent can usually be installed either as a native service or as a container. Always follow the exact commands and package names from the current Make.com documentation, as versions and build instructions can change.

1. Retrieve the Latest Agent Package from Make.com

1. Sign in to your Make.com account in a browser.
2. Open the organization or admin area where you manage agents.
3. Locate the On-Premise Agent section and copy the download link or Docker image reference provided.
4. Move to the target server (local machine, VM, or container host) that will run the agent.

2. Install the Make.com Agent Service

You typically have two main options:

• Binary or package installation
  Download the agent binary or system package and install it using your operating system’s package manager or the commands provided in the Make.com instructions.
• Container-based installation
  Pull the official agent image from the container registry recommended by Make.com and run it with the environment variables specified in the docs.

During installation, you will generally need to:

• Set environment variables for the agent token and configuration.
• Choose or confirm the directories for logs and runtime files.
• Optionally configure a systemd service or equivalent so the Make.com agent starts on boot.

Configure the Make.com On-Premise Agent

After installation, the next step is to configure how the agent connects to Make.com and how it reaches your internal resources.

3. Generate Agent Credentials in Make.com

1. In the Make.com web application, open the On-Premise Agent configuration page.
2. Create a new agent entry and copy the unique agent identifier and token that Make.com generates.
3. Store these credentials securely, as they allow the agent to authenticate to the Make.com platform.

4. Apply Configuration to the Local Agent

Use the credentials and settings from Make.com to configure the agent on your server. Typical steps include:

• Editing a configuration file or environment variables to set the agent ID and token.
• Defining allowed internal hosts, ports, or services that the agent is permitted to access.
• Setting any required proxy, TLS, or certificate options so the agent can reach Make.com securely.

Once configuration is complete, restart the agent service or container to load the new settings.

Verify Connectivity Between Make.com and the Agent

Before using the agent in scenarios, confirm that it can communicate with Make.com and your local resources.

5. Check Agent Status in Make.com

1. Return to the On-Premise Agent overview page in the Make.com interface.
2. Locate your new agent and confirm its status indicates it is online or connected.
3. If the status shows offline or error, review the logs on the agent host and verify network settings.

6. Test Internal Resource Access

To make sure the Make.com agent can reach internal systems:

• Create a test scenario in Make.com that uses a module configured to run via the On-Premise Agent.
• Point the module to an internal API, database, or service that is not publicly accessible.
• Run the scenario and confirm that data flows correctly without connection errors.

Use the Make.com Agent in Scenarios

After connectivity is verified, you can start integrating the On-Premise Agent into your everyday Make.com workflows.

7. Assign Modules to the On-Premise Agent

1. Open an existing Make.com scenario or create a new one.
2. Select the module that needs to access an internal resource.
3. In the module settings, choose the appropriate connection or execution option that routes traffic through the On-Premise Agent instead of the public internet.
4. Save the scenario and run it manually or schedule it as needed.

8. Secure and Limit Access via Make.com

To maintain strong security when using the agent:

• Restrict which internal endpoints the Make.com agent is allowed to access.
• Limit agent usage to specific projects or teams within Make.com.
• Rotate agent tokens periodically according to your security policy.
• Monitor logs on both the agent host and within Make.com to detect unusual activity.

Maintain and Update the Make.com On-Premise Agent

Keeping the On-Premise Agent up to date ensures compatibility, security, and stability.

9. Monitor Performance and Logs

• Review agent logs regularly on the host machine for errors or warnings.
• Use system monitoring tools to watch CPU, memory, and network usage of the Make.com agent process or container.
• Check the Make.com admin interface for status indicators or alerts about the agent.

10. Upgrade the Make.com Agent Safely

When a new version is released:

1. Consult the release notes in the official Make.com documentation.
2. Plan a maintenance window if your scenarios depend heavily on the agent.
3. Update the package or container image following the Make.com instructions.
4. Restart the agent and confirm in Make.com that it reconnects successfully.

Additional Resources Beyond Make.com Docs

For advanced automation planning, security architecture, or integration design that complements your Make.com setup, you can work with specialist consultants. One such resource is Consultevo, which focuses on automation and optimization advisory services.

For the most accurate and detailed technical procedures, always refer to the official Make.com guide here: Make.com On-Premise Agent Help Center article. Use that documentation together with this how-to guide to design a secure and reliable deployment that fits your infrastructure and governance requirements.

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