Integrations
Connectors where you can. A builder where you can't.
Four native connectors for the stack most mid-market teams already run: Google Workspace, Microsoft Entra ID, Auth0, BambooHR. For everything else — the internal tool your company actually built, the SaaS your vendor hasn't heard of — an in-app connector builder you use directly in Owlie.
Configuration-first. Functions where config ends. AI-assisted where useful.
In-app connector builder — entry screen
Live at launch
Four connectors. Actually shipped.
Native, maintained, production connectors for the systems mid-market teams already depend on. Coverage varies by system — full provisioning plus sync for Google Workspace, Microsoft Entra ID, and Auth0; sync-only for BambooHR, scoped to HRIS lifecycle signals and identity attributes.
Google Workspace
Users, groups, admin roles, org units, domains. Sync and provision.
Microsoft Entra ID
Users, groups, group membership. Sync and provision.
Auth0
Users, organizations, roles. Sync and provision.
BambooHR
Employee records. Sync for lifecycle signals and identity attributes.
We ship narrow and deep. Coverage expands through the builder and partner work — not through theater.
For everything else
Connectors you build in the product.
The builder is a web UI you use directly inside the admin dashboard. Configure the connection shape — OAuth 2.0, API key, JWT, or a custom auth flow via Function. Declare the entity schemas you want to sync. Map fields with the Owlie Expression Language. Fill in the behaviors that don't fit a config field with a Function — a few lines of TypeScript, sandboxed, version-managed. AI assistance accelerates the parts that have public documentation. A connector that would be a six-figure services engagement elsewhere is a configuration task in Owlie.
- Config-first.
- Most of a typical connector is mapping and lifecycle rules.
- Functions where config ends.
- The behaviors that vary get written in TypeScript.
- AI-assisted where useful.
- Schema inference, auth detection, and boilerplate scaffolding for systems with public docs.
- Versioned releases.
- Draft and edit. Publish to go live. Roll back when you need to.
Connector builder — mid-configuration (panels + OEL + Function snippet)
Beyond the catalog.
Standards
SCIM, SAML 2.0, OIDC for SSO and directory sync.
APIs and webhooks
A GraphQL API for every platform object. Webhooks for lifecycle events.
Sync & import
Scheduled pulls, incremental where the source supports it, full-state reconciliation where it doesn't.
Custom systems
The builder handles this. Request an integration for systems we haven't shaped yet.
What we're not.
We don't ship 200 connectors on day one. We don't want to. A wide catalog of shallow integrations is a maintenance tax you'd pay and an audit headache we'd both regret. Our bet is a small, deep set of native connectors — Google Workspace, Microsoft Entra ID, Auth0, BambooHR — plus a builder that handles the rest of your stack without an integration project.
Small catalog. Deep coverage. Builder for everything else.
Don't see what you need?
Tell us which system. If the builder can shape it, we'll help. If it needs a native connector, it goes on the priority list.
Security & Trust.
-
Trust Center
Formal review materials at trust.owlie.com .
-
SOC 2 program in progress
Controls design and evidence collection underway ahead of Type I.
-
security@owlie.com
Direct line for security reviewers and responsible disclosure.
The stack you have. Not the one your vendor wishes you had.
Early access is open. Bring a real integration ask and we'll show you the builder working against it.