Ontelis connects to all of your business systems: Veeva CRM, SAP, Snowflake, Salesforce, distributor portals, data files and more. Every write is certified, and credentials stay in your vault.
OAuth client; secret at vault path sap/prd/purchasing
Discovery calls
OData $metadata for the purchasing services
Read actions
get_purchase_order(po_number)Certified
Change feed
Change pointers on purchasing documents
Write actions
Write actions in the SAP purchasing manifest
Action
Effect
Write class
Undo
Status
create_requisition
Starts the release workflow
Compensable
Deletion flag
Certified
change_requisition
Changes quantity or delivery date on an open requisition
Reversible
Restore the prior values
CandidateWaiting for the SAP procurement owner
create_purchase_order
Creates a purchase order
Not yet set
Not yet tested
CandidateBlocked: the sandbox run also sent the order to the vendor. Declare the side effect before certifying.
Rate budget
Agreed with the SAP basis team, shared by all agents
Change windows
No writes during month-end close
Owner
SAP procurement owner
Certification status
Reads certified; one of three writes certified
Licence and purpose terms
Commercial vendor spend only
Show 4 more fields
Rate budget
Agreed with the SAP basis team, shared by all agents
Change windows
No writes during month-end close
Owner
SAP procurement owner
Licence and purpose terms
Commercial vendor spend only
Trusted by 2 out of the 5 largest life sciences companies
The most structured route, every time.
Connect uses the most structured route a system offers and steps down only when that route lacks the operation. Files with no system behind them land in a zone you own.
A new system is configuration, not a release.
Each connector is a manifest generated from the system’s own description, such as an OpenAPI spec or SAP OData metadata. Reads go live after a sandbox test and the owner’s sign-off. Writes are certified one at a time.
Agents work in any web app through the browser.
Where a system has no API, agents use the browser directly, the way a person would: sign in with a vaulted credential, find the page, read it and fill it in. Each step is logged, and screenshots pass Mask.
Agents never hold a password.
Credentials stay in your vault. A broker issues a short-lived token for each call, and the ledger records the exact agent, run and person behind every write.
When a source breaks, work stops safely.
Schema drift quarantines the affected actions and pauses the agents that depend on them. An expired credential marks the source down, and checks that need it fail closed.
“The diagram used to be the thing we argued about. Now it shows us where every value came from, and it flags what our own templates got wrong.”
Senior Solution Architect, Campaign OperationsOne of the top 10 global pharma companies
What Connect does not do
Sync systems with each other without an agent step.
Bulk-copy row-level data from a system that can be queried in place.
Borrow a person’s login.
Hold credentials outside your vault.
Where Connect fits
Connect writes each approved action back to its system of record.
Ontelis Connect is how Ontelis agents read and write in the systems you already run, such as Veeva Vault CRM, SAP, Salesforce and Snowflake. It takes the most structured route each system offers: the published API first, a query run inside the warehouse, SFTP for partner files, and a browser only for a portal with no API. Connect is how Ontelis reaches your systems; the Agent Gateway is how agents, including Copilot and Agentforce, reach Ontelis.
Connect has no fixed list of supported systems. It comes with prebuilt connectors for Veeva Vault CRM and PromoMats, Salesforce Life Sciences Cloud, IQVIA feeds, Snowflake, Databricks, SAP, Coupa, Model N, OneTrust and DocuSign, and those are a head start, not the limit. For any other system, Ontelis generates the connector from the system's own description, such as an OpenAPI spec or SAP OData metadata, so a new system is configuration, not a product release.
No. Connect never syncs one system with another without an agent step, so the system-to-system flows your integration platform runs aren't work it takes over. It also doesn't bulk-copy rows out of a system it can query in place: Snowflake and Databricks data is read where it sits. Connect is there so an Ontelis agent can do a step of work, such as validating a PBM rebate invoice or raising an SAP requisition, and write the approved action back to the system of record.
Yes, once your CRM owner certifies each write action. Vault CRM is one of Connect's prebuilt connectors, and writes are certified one at a time, because an API spec doesn't show an action's side effects. Each certified write carries a tested undo or is labelled irreversible. When an Ontelis agent writes, the checks for that step run first, a person approves if the step requires it, and Connect reads the record back to confirm the change landed.
No, never. Ontelis agents don't borrow anyone's login and don't hold passwords. Your credentials stay in your own vault, and a credential broker issues a short-lived token for each call an agent makes to Veeva, SAP or any other system. Read credentials and write credentials are kept separate.
The audit trail shows the agent's own named account wherever that trail is your regulated record, as in Vault, sample management or a validated system, or wherever you require one. Elsewhere, Ontelis agents built for the same job share one integration user, and that's the account the system shows; where the system allows it, the agent ID is stamped into its audit fields. Ontelis's own record of the write always names the exact agent, the run and the person behind it.
Ontelis starts from the system's own description, such as an OpenAPI spec or SAP OData metadata, and needs a sandbox or non-production copy to test against. The rest is your people. The system's owner signs off the reads and certifies each write, one action at a time. A data steward puts a class on every field the connector brings in. Your privacy officer approves any source that may hold patient data. Nothing in a new connector runs until it's certified.
Credentials stay in the customer’s vault, and read and write credentials are separate.
Vendor documents
Ontelis provides: a SOC 2 Type II report, an ISO 27001 certificate, a HIPAA business associate agreement wherever Ontelis processes PHI, a data processing agreement with transfer clauses, and a sub-processor list.
Models
Ontelis builds no foundation model. No model is trained on customer data, except an opt-in adapter that never leaves the customer’s data plane.
Your controls
Ontelis’s posture as a vendor is kept separate from Govern, which holds your own controls.