# Supported Integrations

> Choose how to connect PSA, RMM, identity, documentation, security, and billing systems in each client workspace.

Glow connects the systems an MSP uses through pre-built app connections, HTTP requests, and inbound webhooks. Choose the method each client system supports, then keep its credentials inside that client's workspace.

Build a reusable workflow in your own workspace, then copy it to one client at a time after reviewing its preflight.

,
    },
    {
      value: "Per workspace",
      label: "Client Credentials",
      note: "Secrets and tokens stay in the workspace where they were added",
      icon: ,
    },
    {
      value: "REST & webhooks",
      label: "Custom Connections",
      note: "Connect services that expose a compatible API or webhook",
      icon: ,
    },
  ]}
/>

---

## Connection Methods

Glow communicates with client systems through three connection methods:

1. **Pre-built apps ([Apps and Integrations](/manage/apps-and-integrations/overview)):** Use a visual action or trigger where the required service and operation are available in the directory.
2. **REST APIs ([HTTP Request](/build/action-steps/http-request)):** Call a service that exposes a compatible REST endpoint, using its documented authentication method.
3. **Inbound webhooks ([Webhook Trigger](/build/triggers/webhook)):** Receive real-time telemetry and alerts, with signature verification where the sender supports it.

| Category                 | Examples in the Glow ecosystem                       | Ways to connect                                                                                                                                 | Typical authentication          | Example workflows                                                                                         |
| ------------------------ | ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | --------------------------------------------------------------------------------------------------------- |
| **PSA & Service Desk**   | ConnectWise PSA, Autotask, ServiceNow, Zendesk, Jira | [Pre-built app](/manage/apps-and-integrations/overview) or [HTTP Request](/build/action-steps/http-request)                                     | OAuth 2.0, API key or secret    | Dispatch tickets, sync configuration items, update agreements and log technician time                     |
| **Identity & IAM**       | Microsoft 365, Entra ID, Google Workspace, Okta      | [Pre-built app](/manage/apps-and-integrations/overview) or [HTTP Request](/build/action-steps/http-request)                                     | OAuth 2.0 or admin consent      | Provision and offboard users, assign licences, update groups and revoke sessions                          |
| **RMM & Endpoint Mgmt**  | NinjaOne, Datto RMM, ConnectWise Automate            | [Pre-built app](/manage/apps-and-integrations/overview), [HTTP Request](/build/action-steps/http-request) or [Webhook](/build/triggers/webhook) | OAuth 2.0, API key or secret    | Receive device alerts, fetch hardware details and start remediation                                       |
| **Documentation & CMDB** | IT Glue, Hudu, ScalePad, Liongard                    | [Pre-built app](/manage/apps-and-integrations/overview) or [HTTP Request](/build/action-steps/http-request)                                     | API key or bearer token         | Create records, track warranty dates and sync contacts                                                    |
| **Cybersecurity & EDR**  | CrowdStrike Falcon, SentinelOne, Huntress, Duo       | [Pre-built app](/manage/apps-and-integrations/overview), [HTTP Request](/build/action-steps/http-request) or [Webhook](/build/triggers/webhook) | OAuth 2.0, API key or signature | Receive detections, route forensic indicators and isolate endpoints where the selected action supports it |
| **CSP & Cloud Billing**  | QuickBooks, Xero, Stripe, DocuSign, Pax8             | [Pre-built app](/manage/apps-and-integrations/overview) or [HTTP Request](/build/action-steps/http-request)                                     | OAuth 2.0 or API key            | Compare subscriptions with agreements, route billing exceptions and prepare reconciliation                |
| **Alerts & Team Comms**  | Microsoft Teams, Slack, PagerDuty, Twilio            | [Pre-built app](/manage/apps-and-integrations/overview) or [HTTP Request](/build/action-steps/http-request)                                     | OAuth 2.0 or API key            | Send notifications, route on-call escalations and dispatch messages                                       |

---

## How Connections Work

The available method depends on the service and operation. Check the Integrations Directory first, then use HTTP Request or a webhook when that is the better fit.

### 1. Pre-Built App Connections

Where the app and operation are available in the directory, configure them from the App drawer:

1. Open your workflow canvas and click **Apps** in the dock.
2. Select your application from the catalogue and click **Connect**.
3. Authorize the account. Glow securely stores credentials inside the active workspace and handles token lifecycles and background refreshes automatically.
4. Pick your pre-built action or trigger from the drawer and configure inputs using dynamic variable tags.

### 2. Custom PSA & RMM REST APIs ([HTTP Request](/build/action-steps/http-request))

For specialized MSP platforms and on-premise tools with a documented REST API:

1. Add an [HTTP Request](/build/action-steps/http-request) step to your canvas or paste a cURL snippet to generate it instantly.
2. Configure your endpoint URL using workspace variables: `https://{{ $var.PSA_INSTANCE }}/api/v1/tickets`.
3. Provide authentication in headers: `Authorization: Bearer {{ $secret.PSA_API_KEY }}`.
4. Response payloads are automatically parsed into structured variables accessible in subsequent steps.

### 3. Real-Time Telemetry & Threat Feeds ([Inbound Webhooks](/build/triggers/webhook))

For instant alert ingestion (NinjaOne monitoring alerts, SentinelOne threat detections, Huntress incident feeds):

1. Add a [Webhook](/build/triggers/webhook) trigger step to your workflow canvas.
2. Switch the workflow to **Live** mode to generate your unique, per-workflow webhook URL.
3. Configure your RMM or EDR to dispatch alert notifications to this webhook URL.
4. Provide a secret key to enforce cryptographic HMAC signature verification on every inbound payload.

---

## Workspace Credential Isolation

Each client's credentials belong in that client's workspace:

- **Separate client workspaces:** Secrets, API keys, and app connections added in Client A's workspace are not available to workflows in Client B's workspace.
- **Client-owned authentication:** A client can connect its own service accounts without giving you the underlying credential value.
- **Reviewed workflow copies:** Build a reusable workflow in your own workspace, then copy it to one client through [Pushing Workflows to Clients](/msp/cross-workspace-pushing). The preflight identifies connections and values the client still needs to provide.

---

## Explore Integrations & Blueprints

  - [App Directory](/msp/integration-directory): Search commonly used MSP platforms by category, connection method, and authentication type.
  - [Automation Blueprints](/msp/automation-blueprints): Example workflow patterns for onboarding, billing reconciliation, security alerts, and routine operations.

## What's Next?

👉 **[App Directory →](/msp/integration-directory)** — find the connection method available for a specific MSP platform.

Sideways from here: [How Multi-Tenancy Works](/msp/how-multi-tenancy-works) explains what stays inside each client workspace.