​
Why Test Connections?

Regular connection testing ensures your automation monitoring remains reliable and accurate. Testing helps you:

Verify Connectivity

Confirm your platforms are accessible and responding correctly

Validate Credentials

Ensure API keys and tokens are still valid and have proper permissions

Monitor Performance

Track response times and identify potential performance issues

Prevent Downtime

Proactively identify issues before they impact your monitoring

​
Types of Connection Tests

​
Manual Testing

Perform on-demand tests when needed:
1

Navigate to Connections

Go to the Connections page in Opsmatic
2

Find Your Connection

Locate the connection you want to test
3

Click Test Button

Click the “Test” button on the connection card
4

Review Results

Analyze the test results and address any issues

​
Automatic Health Checks

Opsmatic automatically tests connections:
  • Every 5 minutes for active connections
  • Every 15 minutes for inactive connections
  • Increased frequency during peak hours
  • Custom intervals for enterprise users
  • Response time monitoring
  • Success/failure rate tracking
  • Availability percentage calculation
  • Trend analysis over time

​
Understanding Test Results

​
Successful Connection Test

A successful test shows:
Successful connection test results
Indicators of Success:
  • ✅ Green status indicator
  • ✅ “Connection successful” message
  • ✅ Response time under 2 seconds
  • ✅ Workflow/scenario count retrieved
  • ✅ Platform information detected

​
Failed Connection Test

Failed tests provide diagnostic information: Common Failure Messages:
  • “Authentication failed” - Invalid credentials
  • “Connection timeout” - Network or server issues
  • “Access denied” - Permission problems
  • “Server not found” - URL or configuration errors

​
Platform-Specific Testing

​
n8n Connection Testing

API Endpoints:
  • /api/v1/workflows - Workflow list retrieval
  • /api/v1/executions - Recent execution data
  • /api/v1/credentials - Credential validation
Validation Checks:
  • API key authentication
  • Base URL accessibility
  • n8n version compatibility
  • Workflow read permissions

​
Make.com Connection Testing

API Endpoints:
  • /api/v2/scenarios - Scenario list retrieval
  • /api/v2/users/me - User information
  • /api/v2/teams/{id} - Team information (if applicable)
Validation Checks:
  • API token authentication
  • Region endpoint accessibility
  • Team ID validation (if provided)
  • Scenario read permissions

​
Interpreting Test Metrics

​
Response Time Analysis

Excellent: < 500ms
  • Optimal performance
  • No action needed
Good: 500ms - 2s
  • Normal performance
  • Monitor for trends
Warning: 2s - 5s
  • Slower than ideal
  • Check network or server load
Poor: > 5s
  • Performance issues
  • Investigate immediately
Network Factors:
  • Internet connection speed
  • Geographic distance to servers
  • Network congestion
  • Firewall/proxy processing
Platform Factors:
  • Server load and performance
  • Database query complexity
  • API rate limiting
  • Maintenance or updates

​
Availability Metrics

Excellent (99%+)

Highly reliable connection with minimal downtime

Good (95-99%)

Generally stable with occasional issues

Poor (<95%)

Frequent connection problems requiring attention

​
Automated Monitoring Features

​
Health Check Dashboard

Monitor connection health in real-time:
Connection health monitoring dashboard
Dashboard Elements:
  • Real-time status indicators
  • Response time graphs
  • Availability percentage
  • Recent test history
  • Error frequency charts

​
Alert Notifications (Coming Soon)

Get notified when connections fail:
Trigger Conditions:
  • Connection test failures
  • Response time threshold exceeded
  • Availability drops below threshold
  • Credential expiration warnings
Features:
  • Real-time connection status updates
  • Automated incident reports
  • Team collaboration on issues
  • Status recovery notifications

​
Best Practices for Connection Testing

​
Regular Testing Schedule

Daily Checks

Test critical connections daily, especially for production environments

Pre-Deployment

Always test connections before deploying new workflows or updates

Post-Maintenance

Test connections after platform maintenance or configuration changes

Credential Rotation

Test immediately after updating API keys or tokens

​
Proactive Monitoring

1

Set Baselines

Establish normal response time and availability baselines for each connection
2

Monitor Trends

Watch for gradual degradation in performance or reliability
3

Plan Maintenance

Schedule connection updates during low-activity periods
4

Document Issues

Keep records of connection problems and their resolutions

​
Troubleshooting Connection Issues

​
Systematic Troubleshooting Approach

  • Check if the platform is online and accessible
  • Verify credentials haven’t expired
  • Confirm URL and configuration settings
  • Test with a different browser or device
  • Verify API key/token permissions
  • Check if user account is still active
  • Confirm organization/team access
  • Review recent permission changes
  • Test platform accessibility from different locations
  • Check firewall and proxy settings
  • Verify DNS resolution
  • Test with direct IP if possible
For n8n:
  • Verify n8n instance is running
  • Check n8n logs for errors
  • Confirm API is enabled in settings
  • Test API endpoints manually
For Make.com:
  • Check Make.com status page
  • Verify correct region selection
  • Test API token in Make.com interface
  • Check account standing and limits

​
Common Solutions

Regenerate API Keys:
  1. Log into your platform (n8n/Make.com)
  2. Navigate to API settings
  3. Revoke old API key/token
  4. Generate new credentials
  5. Update connection in Opsmatic
  6. Test the updated connection

​
Testing Multiple Connections

​
Bulk Testing

For users with multiple connections:
1

Select Connections

Choose multiple connections to test simultaneously
2

Run Batch Test

Execute tests for all selected connections
3

Review Results

Analyze results across all connections
4

Address Failures

Focus on failed connections first

​
Performance Comparison

Compare connection performance:

Response Time Comparison

Identify which connections are slower than others

Reliability Analysis

Compare availability percentages across connections

​
Integration with Monitoring

​
Connection Health in Analytics

Connection test results feed into:
  • Availability Metrics: Uptime calculations
  • Performance Tracking: Response time trends
  • Reliability Reports: Success/failure statistics
  • Capacity Planning: Load and usage analysis

​
Correlation with Workflow Performance

Connection health directly impacts:
  • Data Freshness: How recent your monitoring data is
  • Alert Accuracy: Reliability of performance alerts
  • Trend Analysis: Quality of historical data
  • Reporting Completeness: Coverage of workflow analytics

​
Need Help?

If you’re experiencing persistent connection issues:

Documentation

Check our detailed connection troubleshooting guide

Support

Contact our support team for personalized assistance

​
What’s Next?

After mastering connection testing:

Dashboard Overview

Learn how to interpret your monitoring dashboard

Analytics Deep Dive

Explore detailed workflow analytics and performance metrics