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 — entry screen
Builder landing view: auth-mode picker, schema setup, and the start-from-scratch option.
Build it in the product
A builder, not a services engagement.
Pick a connection shape — OAuth 2.0, API key, JWT, or a custom auth flow written as a 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. Draft and edit in the product. Publish to go live. Roll back when you need to. AI assistance handles the boilerplate where the target system has public documentation.
Connector builder — mid-configuration
Panels for entity schemas and field mappings, Owlie Expression Language inline, and a small Function snippet in the gutter.
Where config ends
Functions pick up where config can't reach.
Config covers most of what a connector needs to do — authenticate, fetch entities, create and update and delete accounts, assign and revoke entitlements. What config can't express — system-specific quirks, custom auth flows, derived fields, non-standard lifecycle semantics — you write as a Function. 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. The priority list is informed by real requests. In the meantime, the builder is usually the faster path to a working integration.