Add a New Integration

Integrations are the data sources that power LanternOps. They collect evidence, enable automation, and prove compliance. Each integration takes 5-10 minutes to connect and begins delivering value immediately.

Time to Complete: 5-10 minutes per integration

What Integrations Do

Every integration you connect:

Collects Evidence

• Asset data (NinjaOne, Syncro)
• Security events (Huntress, CrowdStrike)
• Tickets and time (ConnectWise, HaloPSA)
• Email security (Avanan, Microsoft 365)

Enables Compliance

• Automatic control-to-evidence mapping
• Real-time compliance dashboards
• Audit-ready documentation

Powers Revenue Discovery

• Identifies service gaps
• Detects hardware refresh needs
• Finds upsell opportunities

Updates Business Impact Dashboards

• Threats blocked
• Value delivered
• ROI calculations

The more integrations you connect, the smarter LanternOps becomes.

Supported Integrations

LanternOps supports 17+ active integrations across categories:

RMM & Asset Management

• NinjaOne - Asset inventory, patch status, endpoint monitoring
• Syncro - RMM and PSA combined
• Action1 - Patch management and remote control

PSA & Ticketing

• ConnectWise Manage - Ticketing, time tracking, projects
• HaloPSA - Service desk and PSA
• Autotask - PSA and project management

Security Tools

• Huntress - EDR, threat hunting, ransomware protection
• CrowdStrike - Enterprise EDR and threat intelligence
• Avanan - Email security and threat protection
• NextDNS - DNS filtering and web security
• Cisco Umbrella - DNS and web gateway

Microsoft Ecosystem

• Microsoft 365 - Users, licenses, security events
• Microsoft Graph - Deep integration (email, Teams, SharePoint)
• Azure AD - Identity and access management

Backup & DR

• Veeam - Backup validation and recovery testing
• Datto - BCDR and backup monitoring

Network & Infrastructure

• Auvik - Network monitoring and mapping
• PRTG - Infrastructure monitoring

Business & Billing

• Pax8 - License management and billing
• Timely - Time tracking and billing

View full integration list →

Prerequisites

Before connecting an integration:

• Admin access to the tool you’re integrating
• API credentials or OAuth permissions
• Understanding of what data you want to collect
• Firewall/network access if required

Step-by-Step Instructions

Step 1: Navigate to Integrations

1. Log in to LanternOps
2. Click Integrations in the main navigation
3. Click Add Integration
4. Browse or search for the tool you want to connect

Popular First Integrations:

• NinjaOne (if you use it as RMM) - Best evidence source for assets
• Microsoft 365 (most MSPs have it) - User/license data
• ConnectWise (if your PSA) - Ticket and time data

Step 2: Select Integration Type

Click on the integration you want to add. You’ll see:

Integration Overview:

• What data it collects
• What compliance controls it satisfies
• Which services require it
• Estimated setup time

Example: NinjaOne

Data Collected:
• Asset inventory (all endpoints and servers)
• Operating system versions and patch status
• Software installations and licenses
• Hardware specs and warranty info
• Last check-in timestamps

Satisfies Controls:
• CIS 1.1, 1.2, 1.5 (Asset Management)
• CIS 7.1-7.7 (Vulnerability Management)
• NIST ID.AM-1, ID.AM-2 (Asset Inventory)
• CMMC AC.1.001 (System Inventory)

Required For Services:
• Complete Asset Management
• Patch Management
• Hardware Lifecycle Management

Setup Time: 5 minutes

Step 3: Configure Connection

Each integration has different connection methods:

Option A: OAuth (Easiest - Recommended)

Used by: Microsoft 365, Google Workspace, some modern tools

1. Click Connect with OAuth
2. You’re redirected to the tool’s login page
3. Sign in with admin account
4. Review permissions requested
5. Click Authorize
6. Redirected back to LanternOps

Done! Integration is connected.

Option B: API Key

Used by: NinjaOne, Huntress, Auvik, many others

1. Get API credentials from the source tool:

   NinjaOne Example:

   • Log in to NinjaOne
   • Navigate to Administration → API
   • Click Add API Key
   • Select Scope: Read (minimum required)
   • Copy Client ID and Client Secret

2. Enter in LanternOps:

   • Paste Client ID
   • Paste Client Secret
   • Enter Region (if applicable - e.g., US, EU, APAC)

3. Click Test Connection

Success: “Connected to NinjaOne - 147 devices discovered”

Option C: Username & Password (Legacy)

Used by: Older tools without API support

1. Enter username (service account recommended)
2. Enter password
3. Enter tenant ID or subdomain if required
4. Click Test Connection

Security Note: Credentials are encrypted at rest in our database

Option D: Webhook (Advanced)

Used by: Real-time integrations (Microsoft Graph webhooks)

1. Click Generate Webhook URL

2. Copy the webhook URL

3. Configure in source tool:

   • Paste webhook URL
   • Select events to send (new emails, new users, etc.)
   • Save in source tool

4. Click Test Webhook in LanternOps

5. Trigger test event in source tool

6. Verify LanternOps receives it

Result: Real-time data sync (under 5 minutes latency)

Step 4: Configure Sync Settings

After connection is established:

Sync Frequency

How often should LanternOps pull data?

• Real-time (webhook-based) - For Microsoft Graph, modern APIs
• Every 15 minutes - Recommended for most integrations
• Hourly - Sufficient for slow-changing data (licenses, users)
• Daily - For backup validation, reports
• Manual - Only sync when you click “Sync Now”

Recommendation: Start with 15 minutes, adjust based on needs

Data Scope

What data should we collect?

Example: NinjaOne

• Devices (endpoints and servers)
• Operating systems
• Installed software
• Patch status
• Performance metrics (CPU, RAM usage)
• Alerts and incidents

Why Limit Scope: Faster syncs, lower API usage, focus on compliance-relevant data

Recommendation: Enable only what you need initially, expand later

Tenant Filtering (Multi-Tenant Tools)

If the integration covers multiple customers:

Example: Pax8

• Your Pax8 account has 50 customers
• Map each to corresponding LanternOps customer
• LanternOps automatically segregates data

To configure:

1. Click Map Tenants
2. Match source tenant to LanternOps customer
3. Save mappings

Result: Customer A only sees their Pax8 data, Customer B sees theirs, etc.

Step 5: Initial Sync

1. Click Sync Now to trigger first data pull
2. Progress bar shows:
   • Connection status
   • Records discovered
   • Records imported
   • Errors (if any)

Typical Times:

• Small environment (50 endpoints): 30-60 seconds
• Medium environment (200 endpoints): 2-3 minutes
• Large environment (1000+ endpoints): 5-10 minutes

First Sync Complete:

✅ NinjaOne Sync Complete

Imported:
• 147 devices
• 2,847 software installations
• 147 patch status reports
• 12 alerts

Next sync: 15 minutes

All data indexed in RAG system.

Step 6: Verify Data

Check that data is flowing correctly:

1. Click View Imported Data

2. Review sample records:

   • Device names make sense?
   • Patch status accurate?
   • Software list reasonable?

3. Navigate to customer → Assets tab

4. Verify assets appear in customer view

Troubleshooting: If data looks wrong, check:

• Integration permissions (does API key have read access?)
• Tenant mapping (are we pulling the right customer?)
• Data scope (did we enable the right data types?)

Step 7: Map to Services

Tell LanternOps which services use this integration:

Example: NinjaOne provides data for:

• Complete Asset Management
• Patch Management
• Hardware Lifecycle Management

Why This Matters: When generating audit packages or dashboards, LanternOps knows to use NinjaOne data as evidence for these services.

Auto-Detection: LanternOps suggests mappings based on integration type. Review and confirm.

Step 8: Enable Compliance Evidence Collection

Final step: Enable automatic evidence collection

1. Click Compliance Evidence tab
2. Review suggested evidence rules:

Example: NinjaOne

Evidence Rule: Asset Inventory Report
Frequency: Monthly
Controls: CIS 1.1, 1.2, 1.5 | NIST ID.AM-1
Action: Auto-generate asset inventory report from NinjaOne data
Status: ✅ Enabled

Evidence Rule: Patch Compliance Report
Frequency: Weekly
Controls: CIS 7.1, 7.2, 7.3 | NIST PR.IP-12
Action: Generate patch status report, flag critical missing patches
Status: ✅ Enabled

3. Enable desired evidence rules
4. Click Save

Result: Evidence automatically collected and attached to compliance controls. No manual work.

Integration-Specific Guides

NinjaOne Integration

What You Need:

• NinjaOne admin account
• API access enabled (contact NinjaOne if not visible)

Steps:

1. NinjaOne → Administration → API
2. Add API Key → Scope: Read
3. Copy Client ID and Client Secret
4. LanternOps → Integrations → NinjaOne
5. Paste credentials → Test Connection

Data Collected:

• All devices (endpoints, servers, network devices)
• OS versions, patch status
• Software inventory
• Hardware specs, warranty dates
• Last check-in times

Sync Time: 2-5 minutes for typical environment

Evidence Generated: Asset inventory, patch compliance, hardware lifecycle

Microsoft 365 Integration

What You Need:

• Global Admin or Application Admin role
• Microsoft 365 E3/E5 or Business Premium license

Steps:

1. LanternOps → Integrations → Microsoft 365
2. Click Connect with OAuth
3. Sign in to Microsoft
4. Review permissions:
   • Read users and groups
   • Read organization info
   • Read security events (optional)
   • Read mailbox metadata (optional - needed for email security metrics)
5. Click Accept

Data Collected:

• User accounts and licenses
• MFA status per user
• Mailbox counts
• Security alerts (if enabled)

Sync Time: 30-90 seconds

Evidence Generated: User access controls, MFA enforcement, email security

Huntress Integration

What You Need:

• Huntress account with API access
• API key (from Huntress dashboard)

Steps:

1. Huntress → Account Settings → API Credentials
2. Generate API Key
3. Copy API Key and Account Name
4. LanternOps → Integrations → Huntress
5. Paste credentials → Test Connection

Data Collected:

• Agents deployed (endpoint count)
• Threats detected and remediated
• Malware incidents
• Ransomware attempts blocked

Sync Time: 30 seconds

Evidence Generated: Endpoint protection status, threat metrics, malware prevention

ConnectWise Manage Integration

What You Need:

• ConnectWise admin account
• API member account (create one for integrations)

Steps:

1. ConnectWise → System → Members → API Members
2. Add API Member
   • Name: LanternOps Integration
   • API Keys: Generate
   • Permissions: Read (minimum)
3. Copy Company ID, Public Key, Private Key
4. LanternOps → Integrations → ConnectWise Manage
5. Paste credentials → Select Data Center (NA, AU, EU) → Test Connection

Data Collected:

• Tickets (open, closed, resolution times)
• Time entries
• Agreements (services customers have)
• Billing information (if enabled)

Sync Time: 1-3 minutes

Evidence Generated: Service delivery metrics, response times, uptime SLA compliance

Troubleshooting

”Connection Failed” Error

Cause: Invalid credentials, network issue, or permission problem

Solution:

1. Re-check credentials: Typo in API key? Extra space copied?
2. Verify permissions: Does API key have read access to required data?
3. Check network: Can LanternOps reach the API endpoint? (firewall rules)
4. Confirm API status: Is the source tool having an outage? (check status page)

Still failing? Click View Diagnostic Logs to see detailed error message

Sync Completes But No Data Appears

Cause: Data scope misconfigured or tenant mapping wrong

Solution:

1. Check Data Scope settings - are required data types enabled?
2. Review Tenant Mapping - are we pulling the right customer?
3. Check Filters - did we accidentally filter out all data?
4. Verify Permissions - API key may not have access to this data type

Example: NinjaOne connected but no devices show → Check: Is “Devices” enabled in Data Scope? Yes → Check: Does API key have permission to read devices? (Log in to NinjaOne → API settings)

Data Appears in Wrong Customer

Cause: Tenant mapping incorrect (multi-tenant integration)

Solution:

1. Integrations → Select integration → Tenant Mapping
2. Review mappings (Source Tenant → LanternOps Customer)
3. Correct any mistakes
4. Click Re-sync to refresh data with correct mapping

Sync Very Slow or Times Out

Cause: Too much data, API rate limiting, or network latency

Solution:

1. Reduce data scope: Disable performance metrics, historical data
2. Increase sync interval: Change from 15 min to 30 min or hourly
3. Use delta sync: Only pull changed data (enable in settings)
4. Check rate limits: Some APIs limit requests per hour (contact vendor)

Example: NinjaOne with 1000+ devices timing out → Solution: Enable Delta Sync (only pull devices changed since last sync) → Result: Sync time drops from 10 minutes to 30 seconds

Integration Disconnects After Working

Cause: Credentials expired, password changed, or API key revoked

Solution:

1. Re-authenticate: Click Reconnect and enter new credentials
2. Check expiration: Some OAuth tokens expire (30-90 days) - refresh them
3. Verify API key: Log in to source tool, confirm API key still exists
4. Enable auto-refresh: For OAuth, enable automatic token refresh

Prevention: Use service account credentials that don’t expire

Best Practices

Which Integrations to Connect First

Priority 1 (Connect Day 1):

1. RMM (NinjaOne, Syncro) - Asset data is foundation
2. PSA (ConnectWise, HaloPSA) - Service delivery metrics
3. Microsoft 365 (if you manage it) - User and license data

Priority 2 (Connect Week 1): 4. Security tools (Huntress, Avanan) - Threat metrics 5. Backup (Veeam, Datto) - Disaster recovery evidence 6. DNS Security (NextDNS, Umbrella) - Web filtering data

Priority 3 (Connect Month 1): 7. Network monitoring (Auvik) - Uptime data 8. Licensing (Pax8) - Billing reconciliation 9. Specialty tools (Action1, Timely, etc.) - As needed

Service Account Best Practices

Don’t:

• Use your personal admin account
• Use shared credentials
• Use accounts that expire

Do:

• Create dedicated service account: [email protected]
• Use strong, unique password
• Store in password manager
• Document in integration notes

Why: Personal accounts get disabled when people leave. Service accounts persist.

Security Considerations

API Keys:

• Use read-only permissions whenever possible
• Never share API keys
• Rotate keys annually
• Revoke immediately if compromised

OAuth:

• Review requested permissions before accepting
• Revoke access to test accounts after testing
• Monitor OAuth app usage in admin consoles

Data Privacy:

• Only sync data you need (minimize scope)
• Understand where data is stored (LanternOps uses US-based cloud)
• Ensure compliance with customer contracts (BAA for HIPAA, DPA for GDPR)

Monitoring Integration Health

Weekly Check:

1. Integrations dashboard → Review Sync Status
2. Look for:
   • ❌ Failed syncs (red) - Fix immediately
   • ⚠️ Warnings (yellow) - Investigate soon
   • ✅ Healthy (green) - All good

Set Up Alerts:

1. Integrations → Alerts
2. Enable:
   • Notify if sync fails
   • Notify if sync delayed >1 hour
   • Notify if data volume drops significantly (may indicate issue)

Monthly Review:

• Check integration performance (sync times)
• Review error logs (recurring issues?)
• Validate data quality (spot check against source)

Advanced: Custom Integrations

Don’t see your tool in our list?

Request an Integration

1. Integrations → Request Integration
2. Fill out form:
   • Tool name and vendor
   • What data you need
   • How many customers would benefit
   • API documentation URL (if available)

Typical turnaround: 2-4 weeks for popular tools

Build Custom Integration (API)

For developers:

LanternOps provides Integration SDK for building custom integrations:

from lanternops_sdk import Integration, Field

class CustomToolIntegration(Integration):
    name = "Custom Tool"

    api_key = Field(type="password", label="API Key")
    endpoint = Field(type="url", label="API Endpoint")

    def fetch_data(self):
        # Your logic to fetch data from API
        return data

    def transform_data(self, data):
        # Transform to LanternOps format
        return transformed_data

Documentation: Custom Integration Developer Guide

Next Steps

After connecting your first integrations:

• Verify data appearing in customer views
• Enable evidence collection rules
• Map integrations to services in catalog
• Generate first audit package (see evidence auto-collected!)
• Set up business impact dashboards
• Connect 2-3 more integrations

Related Guides

• Set Up Service Catalog - Map services to integrations
• Generate Audit Package - See integration evidence in action
• Configure Customer Dashboards - Display integration metrics
• Review Revenue Opportunities - Integration data powers opportunity detection

Need Help?

Common Questions:

• Q: How many integrations should I connect?

• A: Start with 3-5 core tools, expand to 10-15 over time. More = better data.

• Q: Do integrations cost extra?

• A: No, unlimited integrations included in your LanternOps subscription.

• Q: Can I disconnect an integration?

• A: Yes, but historical data is retained. Future syncs stop.

Support Resources:

• View Integration Video Tutorials
• Integration Troubleshooting Guide
• Contact Support

Ready to see LanternOps in your environment?

Join the Founding Partner Pilot (60 days) and get a client-ready compliance + security reporting layer connected to your PSA/RMM/security stack.

No credit card required

~30-minute setup (typical)

Limited founding partner spots

Request a Demo →