What are Connections?

Connections are the bridge between Opsmatic and your automation platforms. They allow Opsmatic to monitor, analyze, and provide insights about your workflows across different platforms.
Connections overview dashboard

Supported Platforms

Opsmatic currently supports monitoring for two major automation platforms:

Connection Types

Personal Connections

Personal connections are:
  • Owned by your individual user account
  • Visible only to you (unless shared with organizations)
  • Perfect for personal projects and testing

Organization Connections

Organization connections are:
  • Owned by an organization/team
  • Visible to all organization members (with appropriate permissions)
  • Ideal for team collaboration and shared projects

Connection Management

Adding a New Connection

1

Navigate to Connections

Click “Connections” in the sidebar or go to /connections
2

Click Add Connection

Click the “Add Connection” button in the top-right corner
3

Choose Platform

Select either n8n or Make.com from the available options
4

Configure Settings

Enter the required credentials and configuration details
5

Test Connection

Use the “Test Connection” button to verify your setup
6

Save

Save your connection to start monitoring

Connection Information

Each connection displays:
  • Service Name: Custom name you assigned
  • Platform Type: n8n or Make.com indicator
  • Status: Active, Inactive, or Error state
  • Creation Date: When the connection was added
  • Connection Status: Real-time availability
  • Last Sync: When data was last retrieved
  • Response Time: Platform response performance
  • Error Count: Recent connection issues
  • Owner: Who created the connection
  • Organization: Which team owns it (if applicable)
  • Permissions: Your access level to this connection

Connection Status

Connections can have different status indicators:

Active

Connection is healthy and monitoring data

Error

Connection has issues and needs attention

Inactive

Connection is paused or not responding

Status Details

Characteristics:
  • Successfully authenticating with the platform
  • Regularly syncing workflow data
  • Responding to health checks
  • Processing analytics data
What You’ll See:
  • Green status indicator
  • Recent “Last Sync” timestamp
  • Current workflow counts
  • Performance metrics

Connection Security

Credential Storage

Opsmatic securely stores your connection credentials:
  • Encryption: All API keys and tokens are encrypted at rest
  • Access Control: Only authorized users can view/edit connections
  • Audit Logging: Connection access and changes are logged
  • Secure Transmission: All communication uses HTTPS/TLS

Best Practices

Use Dedicated API Keys

Create specific API keys for Opsmatic rather than using personal tokens

Regular Key Rotation

Periodically rotate API keys and update connections

Minimal Permissions

Grant only necessary permissions for monitoring functionality

Monitor Access

Regularly review who has access to your connections

Managing Multiple Connections

Connection Organization

For users with multiple connections:
Use clear, descriptive names:
  • Production n8n - Main Server
  • Development Make.com - Testing
  • Client Project - Automation Hub
Organize connections by:
  • Personal: Your individual projects
  • Team: Organization-specific connections
  • Environment: Production, staging, development
  • Client: Different client projects
Keep track of connection health:
  • Regularly test connections
  • Monitor error notifications
  • Update credentials proactively
  • Review sync frequency

Bulk Operations

Manage multiple connections efficiently:
  • Test All: Test all connections at once
  • Status Filter: View connections by status
  • Organization Filter: Show connections for specific teams
  • Platform Filter: Display only n8n or Make.com connections

Connection Analytics

What Data is Collected

For each connection, Opsmatic monitors:
  • Workflow names and IDs
  • Execution history and status
  • Success and error rates
  • Execution duration and performance
  • Node count and complexity metrics

Data Retention

Data Retention Policy:
  • Execution Logs: 30 days detailed, 1 year summary
  • Availability Metrics: 7 days raw, 1 year aggregated
  • Analytics Aggregations: 2 years for all periods
  • Connection Metadata: Retained as long as connection exists

Troubleshooting Connections

Common Issues

Symptoms:
  • Connection shows “Error” status
  • “Invalid credentials” error message
  • No data syncing
Solutions:
  • Verify API key/token is correct
  • Check if credentials have expired
  • Ensure proper permissions are granted
  • Re-generate API keys if necessary
Symptoms:
  • Timeouts during connection tests
  • Intermittent connection failures
  • “Cannot reach server” errors
Solutions:
  • Verify platform URL is correct
  • Check firewall and network settings
  • Test platform accessibility from your location
  • Consider network proxy requirements
Symptoms:
  • Limited workflow data
  • “Access denied” errors
  • Missing workflows or executions
Solutions:
  • Review API key permissions
  • Ensure user has appropriate platform access
  • Check team/organization permissions
  • Verify webhook configurations

Testing Connections

Regularly test your connections to ensure they’re working properly:
1

Access Connection

Go to the Connections page and find your connection
2

Click Test

Click the “Test” button on the connection card
3

Review Results

Check the test results for:
  • Connection success/failure
  • Response time
  • Accessible workflows count
  • Any error messages
4

Address Issues

If test fails, follow the error-specific troubleshooting steps

What’s Next?

Once you understand connection basics: