App Directory
Use this directory to plan connections for common client systems. For the complete app list, browse the Integrations Directory . An app connection does not imply that every vendor operation or event is available. Check the required action or trigger in the App drawer before committing to an implementation.
- Use it to
- Search and filter PSA, RMM, IAM, EDR, documentation, and billing platforms by category and authentication method
- Find it
- Canvas → Dock → Apps (or Connections → Connections in the client workspace)
- Limits
- App connections are authorized per client workspace · Private-network and localhost URLs are refused in HTTP Request
- Instead
- HTTP Request (for public REST APIs without a pre-built action) or Webhook Trigger (for inbound event payloads)
Apps and Connection Methods
Search by app name, category, or authentication method, then combine the category and connection filters to narrow the results. App Connections includes both OAuth and credential-based apps. Systems to Assess identifies other client systems that need operation-specific assessment.
Choose Connect App for the client-workspace setup guide, or Assess Connection for the assessment guidance below. Connection methods are those presented by Glow, not interchangeable authentication options for every API endpoint.
App Connections
16 AppsConnect these apps in the client workspace using the method shown on each card. Check the required action or trigger in the App drawer; an app connection does not cover every vendor operation.
Site, company ID, public key, private key, and client ID.
API user username and secret, API tracking identifier, and zone REST URL.
OAuth 2.0 with instance configuration.
OAuth 2.0 with subdomain configuration.
Google OAuth sign-in.
API token with organization domain configuration.
OAuth 2.0 with region selection.
Falcon API client: cloud region, client ID, and client secret.
OAuth 2.0 with separate production and sandbox sign-in choices.
OAuth 2.0 sign-in.
Secret or restricted API key.
OAuth 2.0 with separate production and developer-environment sign-in choices.
Microsoft OAuth sign-in.
OAuth 2.0 sign-in.
OAuth 2.0 sign-in.
Account SID and Auth Token, with optional API Key SID and secret for requests.
Other Client Systems to Assess
23 SystemsThese are project candidates, not a promise of native app coverage. Confirm the vendor API, authentication, event delivery, and required operation before choosing HTTP Request or a webhook.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Confirm the required operation, authentication, and event delivery in the vendor API before implementation.
Ask the client to authorize the account with the permissions required for the selected operation. A delegation grant does not permit connection creation or reauthorization under impersonation. Record the connection owner and plan for reconnection or replacement.
Other Client Systems to Assess
Cards under Systems to Assess are common candidates for client projects, not a promise of native app coverage. Check the vendor’s current API, authentication, event delivery, and required operation. Where no suitable app action is available, assess HTTP Request or a compatible Webhook.
A method supported by one vendor does not establish support for another vendor in the same category. Validate a representative request and result with approved test data before production use.
Connecting Custom, On-Premise, and Niche Tools
For internal scripts, proprietary client databases, or tools without a pre-built connector:
- Use the HTTP Request Step with cURL command import for publicly reachable APIs. Private-network and localhost addresses are refused; arrange an approved public API endpoint before connecting an on-premise system.
- Store each client’s credentials in that client’s workspace Secrets. Review access and the destinations that receive secret values.
- Receive alerts using the Webhook Trigger. Configure its secret and signature header to match a sender using the supported raw-body HMAC-SHA256 format; verification is not enabled by default.
- Run
- Filter the catalog above by category or connection type and click an app card
- You should see
- The card displays the supported authentication method and links to the setup or assessment guide.
What’s Next?
👉 Automation Blueprints →: turn these connection methods into example client automations.
Sideways from here: Supported Integrations explains when to use an app connection, HTTP Request, or webhook.