Custom systems
The system your company actually runs.
Every company has one: the internal tool, the legacy portal, the long-tail SaaS nobody's heard of. Owlie ships an in-app connector builder so these aren't an RFP — they're a Monday afternoon, with AI assistance where useful.
In-app connector builder — setup flow
The builder's setup tabs — basics, authentication, entity schemas, and Functions — reached after you name the connector. Import from an OpenAPI spec, or start from scratch.
Build it in the product
A builder, not a services engagement.
Pick how it authenticates — OAuth 2.0, API key, bearer token, basic auth, or a custom header. Declare the entity schemas you want to sync. Write the read and write operations as Functions — one handler per operation, a few lines of TypeScript. Draft and edit in the product. Publish a version to go live. AI assistance drafts the boilerplate where the target system has public documentation.
Connector builder — schemas and Functions
Entity-schema panels and a full-panel Function editor, one handler at a time.
Before you build
A lot of custom systems already speak a standard.
Before you hand-write a connector, check whether your system speaks a protocol Owlie already handles. If it does, you configure a rail instead of building one — no Functions to write.
- SCIM 2.0
- User, group, and membership sync and provisioning over SCIM, with presets for common variants. Point it at your endpoint and configure.
- LDAP
- Account, group, and membership sync and provisioning against an LDAP directory, executed through the gateway.
- SQL database
- Sync and provision accounts and entitlements from a SQL database, using queries you configure — no connector to write.
- Flat file (CSV)
- Drop a CSV snapshot to an Owlie-hosted location; each upload is a full authoritative feed. Sync only — no writes back.
Configured, not coded. The builder is for the systems that don't fit one of these.
Where config ends
Functions pick up where config can't reach.
Config declares the shape of the connection — how it authenticates, the entity schemas you sync, the shared configuration installers fill in, and the egress domains it may reach. The operations are Functions. Fetching an entity, creating or updating or deleting an account, assigning or revoking an entitlement — each is a handler you write, a few lines of TypeScript against the target's API. Same Function runtime as everywhere else in Owlie: sandboxed, version-managed, secrets-scoped, outbound-allowlisted.
Or ask us to ship it
Some systems deserve a native connector.
If your system needs a native connector — maintained by us, shared across customers — submit it through the request form. Real requests help us decide what to build next. In the meantime, the builder is usually the faster path to a working integration.