Skip to main content

Connect your entire tech stack

Integrations are how Serval acts on the rest of your stack. A connected application can power ticket sync with your ITSM, mirror knowledge bases into Serval, sync users/groups/devices for access management and assets, and give workflows (and Catalyst) the ability to take real actions - provision access, manage devices, file tickets, query records. To browse what’s available, open your Serval workspace and go to Integrations → Connect new. Search the catalog, or select Connect on the Custom card to add a custom application.
Serval's Connect an integration page showing a searchable catalog with Access and Workflows capability badges

The integration catalog - Integrations → Connect new

How connecting works

Each integration uses the connection flow its provider supports. You’ll see one of three patterns:
  • Sign in with the provider (OAuth) - a browser sign-in and consent screen, with no credentials to copy. Examples: Confluence, Jira, Notion, Microsoft 365.
  • Guided app installs - Serval walks you through installing an app on the provider side, like a Slack app from a generated manifest, the Serval GitHub App, or the Microsoft Teams bot package.
  • Credential forms - you create a credential in the provider’s admin console and paste it into Serval: API tokens (Iru, Freshservice, Zendesk), OAuth client credentials (Okta, Salesforce, ServiceNow), or service accounts (Google Workspace, which also offers a basic Sign in with Google flow).
Every integration’s guide documents the exact provider-side click-path to create the credential, the fields Serval’s connect form asks for, and the gotchas we see most often during setup. Secrets are stored encrypted and shown masked when you edit a connection later.

Manage connected applications

The Integrations page lists the applications connected to your workspace, the capabilities each connection powers - Access, API, Knowledge, Ticket Sync, Workflows - and its connection status. Serval can also discover apps in use from your connected sources, so you can bring unmanaged software under management from the same page.
The Connected tab for a workspace showing application cards, workflow counts, and ready-to-install workflow links

The Integrations page - connected applications and available workflow installs

Verify with health checks

Most API-connected catalog integrations have an API Integration tab showing the scopes or permissions the connection was granted and a set of health checks that exercise the live integration - authentication, list/read access per surface, and write access where workflows need it. Run them right after connecting, and any time something stops working: a failing check names what it couldn’t reach, which usually points straight at a missing scope or permission on the provider side. A few integrations don’t include built-in health checks yet - their pages say so and suggest a quick manual verification instead.
Okta API Integration tab showing enabled health checks with Not Run status

An application's API Integration tab - enabled health checks before their first run

When something is wrong, an alert icon appears on the integration’s card on the Integrations page, in the app list, and in the sidebar, so you can spot a broken connection without opening each app. Hovering it shows how many syncs and how many health checks are currently failing as separate counts, each linking to where you investigate: the sync settings page for sync failures and the API Integration tab for health-check failures. The alert clears once the underlying syncs and checks recover. You can turn an individual health check off from its toggle. That choice is saved for that connected application, and a disabled check no longer runs or counts toward the integration’s overall health. This lets you silence a check that doesn’t apply to your setup without it showing the integration as unhealthy.

Duplicate applications across workspaces

You can copy a connected application’s configuration to other workspaces in one click. Open the application’s Settings tab, find the Duplicate Application section, click Duplicate, and choose the destination workspace.

Shared connections and self-hosted workers

If a workspace receiving a shared connection is deleted, it disappears from the connection’s sharing list. The remaining workspaces stay listed.
If a shared connection uses Run on self-hosted workers (for example, Active Directory on-prem or a private-network app), the workspace receiving it needs its own self-hosted worker. Sharing the connection does not share the worker. See Hybrid Worker Setup.

Integration sync history

Each application’s Settings tab includes a Sync History view for monitoring background syncs:
  • Track recent sync runs - when each sync ran and its outcome
  • View breakdowns - how many items were added, updated, or removed
  • Identify issues - spot failed syncs and review error details to troubleshoot connectivity or permission problems

Find your integration

Each guide in this section covers one integration end to end: what it enables, where to get credentials on the provider side, the connect form in Serval, how to verify the connection, and the gotchas that actually come up. The most commonly connected: Identity & directory: Okta · Google Workspace · Microsoft 365 / Entra ID · LDAP / Active Directory Messaging & collaboration: Slack · Microsoft Teams · Confluence · GitBook · Notion ITSM & ticketing: ServiceNow · Jira · Zendesk · Freshservice Devices & assets: Iru · Jamf · Apple Business Manager HR & business systems: Workday · Salesforce · NetSuite · GitHub Don’t see your app? You can connect a custom application through Serval’s API integration framework.