Skip to main content

​
Overview

Make.com (formerly Integromat) is a powerful cloud-based automation platform that allows you to create sophisticated scenarios connecting various apps and services. Opsmatic provides comprehensive monitoring and analytics for your Make.com scenarios, helping you optimize performance and track execution success.
Make.com connection setup

​
Prerequisites

Before connecting Make.com to Opsmatic, ensure you have:

Make.com Account

Active Make.com account (Free, Core, Pro, or Teams plan)

API Access

Ability to generate API tokens in your Make.com profile

​
Supported Make.com Plans

Opsmatic works with all Make.com plans:

Free

Basic monitoring with limited API calls

Core

Standard monitoring and analytics

Pro

Advanced monitoring with full API access

Teams

Organization-level monitoring and team analytics

​
Creating a Make.com API Token

​
Personal API Token

1

Access Profile Settings

Log into Make.com and click your profile icon in the top-right corner
2

Navigate to Profile

Select “Profile” from the dropdown menu
3

Find API Section

Scroll down to the “API” section in your profile
4

Generate Token

Click “Generate Token” button
5

Copy Token

Copy the generated API token immediately (it won’t be shown again)
6

Store Securely

Save the token in a secure location for use in Opsmatic

​
Team API Token (Teams Plan)

For Make.com Teams plan users:
1

Access Team Settings

Go to your team dashboard and click “Team Settings”
2

Navigate to API

Select “API” from the team settings menu
3

Create Team Token

Click “Generate Team API Token”
4

Configure Permissions

Set appropriate permissions:
  • Read scenarios: Required
  • Read executions: Required
  • Read team data: Recommended
5

Save Token

Copy and securely store the team API token

​
Understanding Make.com Regions

Make.com operates in different regions, and you need to specify the correct one:
Region: eu2.make.com (default) API Base URL: https://eu2.make.com/api/v2 Covers: Europe, Middle East, Africa
How to Find Your Region: Check the URL when you’re logged into Make.com. It will show your region (e.g., eu2.make.com, us1.make.com).

​
Adding Make.com Connection in Opsmatic

​
Step-by-Step Setup

1

Navigate to Connections

In Opsmatic, go to Connections from the sidebar menu
2

Add New Connection

Click “Add Connection” button
3

Select Make.com

Choose Make from the platform options
4

Enter Connection Details

Fill in the required information:
  • Service Name: Descriptive name (e.g., “Production Make.com”)
  • Organization: Choose personal or organization context
  • API Token: Your Make.com API token
  • Region: Your Make.com region (eu2, us1, or ap1)
  • Team ID: (Optional) For Teams plan users
5

Test Connection

Click “Test Connection” to verify the setup
6

Save Connection

If the test succeeds, click “Save Connection”

​
Connection Configuration Details

Required Fields:
  • API Token: Your personal API token
  • Region: Your Make.com region
Optional Fields:
  • Team ID: Leave blank for personal accounts
What You’ll Monitor:
  • Personal scenarios
  • Individual execution history
  • Account-level analytics

​
Verifying the Connection

​
Connection Test Results

When you test your Make.com connection, you should see:

Successful Connection

  • ✅ API authentication successful
  • ✅ Scenario count retrieved
  • ✅ Team/user information accessed
  • ✅ Response time measured

Connection Information

  • Number of accessible scenarios
  • Account/team type detected
  • Response time in milliseconds
  • Region confirmation

​
Troubleshooting Connection Issues

Error: “Authentication failed” or 401 UnauthorizedSolutions:
  • Verify API token is copied correctly (no extra spaces)
  • Check if API token has expired
  • Re-generate API token in Make.com profile
  • Ensure token has necessary permissions
Error: “Cannot reach server” or connection timeoutSolutions:
  • Verify your Make.com region (check URL when logged in)
  • Try different region settings (eu2, us1, ap1)
  • Ensure you’re using the correct regional endpoint
Error: “Team not found” or 404 errorSolutions:
  • Verify Team ID is correct (numeric only)
  • Ensure you’re a member of the specified team
  • Check if you have permissions to access team data
  • Try without Team ID first (personal scenarios)
Error: “Access denied” or 403 ForbiddenSolutions:
  • Check API token permissions in Make.com
  • Ensure account is active and in good standing
  • Verify team membership if using Team ID
  • Contact Make.com support if permissions seem correct

​
What Data is Monitored

Once connected, Opsmatic will monitor:

​
Scenario Information

  • Scenario names and unique identifiers
  • Creation and modification timestamps
  • Active/inactive status
  • Scenario complexity (module count)
  • Folder organization
  • Scheduling information
  • Execution start and end times
  • Success/failure/incomplete status
  • Execution duration
  • Operations consumed
  • Error details and messages
  • Data processed (records, size)
  • Average execution time per scenario
  • Success rate trends
  • Operations usage patterns
  • Peak execution periods
  • Error frequency and types

​
Account/Team Analytics

  • Operations consumption tracking
  • Execution quota utilization
  • Monthly usage trends
  • Plan limit monitoring
  • Team member activity
  • Scenario ownership
  • Collaborative usage patterns
  • Team-wide performance metrics

​
Advanced Configuration

​
API Rate Limiting

Make.com has API rate limits that vary by plan:
Limits:
  • 100 API calls per hour
  • Limited scenario access
Opsmatic Optimization:
  • Reduced sync frequency
  • Prioritized data collection
  • Essential metrics only

​
Custom Sync Settings

Options:
  • Every 5 minutes (Pro/Teams plans)
  • Every 15 minutes (standard)
  • Every 30 minutes (Free plan)
  • Hourly (low activity)
Scenario Filtering:
  • Include/exclude specific scenarios
  • Filter by folder or organization
  • Active scenarios only
Execution Filtering:
  • Date range limitations
  • Status-based filtering (success/error)
  • Operations threshold filtering

​
Understanding Make.com Executions

​
Execution States

Success

Scenario completed successfully without errors

Error

Scenario failed due to errors or issues

Incomplete

Scenario stopped before completion (timeout, manual stop)

​
Operations Tracking

Make.com charges based on “operations” - each module execution:
  • Each module = 1 operation
  • Filters don’t count as operations
  • Routers multiply operations by routes
  • Iterators multiply by items processed
Opsmatic helps identify:
  • High-operation scenarios
  • Inefficient routing patterns
  • Unnecessary module executions
  • Optimization opportunities

​
Security and Compliance

​
API Token Security

Token Management

  • Create dedicated tokens for Opsmatic
  • Use descriptive names for identification
  • Regularly rotate API tokens
  • Monitor token usage and access

Permission Control

  • Grant minimum necessary permissions
  • Use team tokens for team monitoring
  • Regularly review token permissions
  • Revoke unused or old tokens

​
Data Privacy

Privacy Commitment: Opsmatic only accesses scenario metadata and execution logs. We never access scenario configuration details, credentials, or processed data content.

​
Monitoring Multiple Make.com Accounts

For agencies or enterprises with multiple Make.com accounts:

​
Organization Strategy

Create separate connections for:
  • Client A: Client A - Make.com Production
  • Client B: Client B - Make.com Automation
  • Internal: Internal Make.com - Company Tools
  • Production: Make.com Production - Live
  • Development: Make.com Dev - Testing
  • Staging: Make.com Staging - QA
  • Marketing Team: Marketing - Make.com
  • Sales Team: Sales - Make.com Automation
  • Operations: Ops - Make.com Workflows

​
Common Use Cases

​
Scenario Monitoring

Monitor scenarios handling:
  • Order processing workflows
  • Inventory management
  • Customer communication
  • Payment processing
Track performance of:
  • Lead nurturing sequences
  • Social media posting
  • Email campaign automation
  • CRM synchronization
Monitor workflows for:
  • Document processing
  • Approval workflows
  • Data synchronization
  • Reporting automation

​
What’s Next?

After successfully connecting your Make.com account:

Test Your Connection

Learn how to properly test and validate your Make.com connection

View Analytics

Start monitoring your Make.com scenario performance and analytics

Set up n8n

Add n8n connections for comprehensive automation monitoring

Dashboard Overview

Explore your monitoring dashboard with Make.com data