Omnea

This page records how composerID publishes into Omnea: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. Omnea (London, founded 2022) is a procurement intake and orchestration platform, positioned by the vendor as the agentic operating system for procurement and supplier management: requests arrive in natural language via Slack, Teams or web, a no-code Workflow Builder routes them through approvals, supplier onboarding, risk checks and sourcing, and approved requests become purchase orders in the ERP through two-way integrations. composerID hands canonical intent to Omnea’s intake and lets the orchestrated flow carry it to PO: Omnea is a complementary orchestration partner, not a destination-of-record.

Category: Procurement Orchestration. Coverage status: Specification mapped. Vendor documentation: gated (customer or SKU documentation). No developer portal is evident.

Integration path

How composerID connects to this destination, at a glance.

Step	Detail
Authentication	Credentials provisioned per customer.
composerID publishes	Intake request: Intake request (Workflow Builder routing)
Intent ID lands on	`intake_request` `customFields.intentId`, written into the destination record
Back-sync	Polling: the destination publishes no events composerID can subscribe to, so state is read back on a schedule.

Vendor documentation

Omnea: platform overview

Omnea: Workflow Builder

Omnea: approval workflows

Omnea: automated PO creation

Omnea: build vs buy (integration surface)

API posture

Aspect	Detail
Authentication	Credentials provisioned per customer. The vendor describes integrations as out-of-the-box or via API; no public self-service developer portal was found, so the auth model (OAuth 2.0 vs API key) is confirmed at onboarding.
Style	Pre-built bidirectional connectors across ERP, CLM, HRIS, ticketing, eSign and TPRM data providers (NetSuite and PandaDoc named in customer material), plus API integrations for what the connectors do not cover. Omnea also ships an MCP server that exposes suppliers, purchase orders, spend and renewals to AI assistants. Endpoint-level reference is customer-scoped until onboarding.
Base URL	Per-customer tenant, provisioned at onboarding. No public base URL.
Webhooks	The vendor states supplier records updated in the ERP are reflected in workflows immediately rather than synchronised overnight, so event-driven sync exists in the connector layer; outbound webhook specifications are not published and are confirmed per tenant.
Events posture	Polling
Rate limits	Not publicly documented; defined per customer integration.
Objects	Intake request, Approval, Supplier (onboarding questionnaire, risk profile), Sourcing event, Contract and renewal, Purchase Order (created in the ERP)

Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.

Intake request

Create the request Omnea orchestrates

Mapping	Detail
Canonical to destination	request_type, description, requester, cost_center, budget, supplier (if known), start_date
Target	Intake request (Workflow Builder routing)
Requirement	Tenant required
Notes	Natural-language intake fields are tenant-configured; composerID supplies the structured record so Omnea skips re-asking

Supplier

Supplier the request is for

Mapping	Detail
Canonical to destination	supplier_name, legal_entity, country, existing_supplier_id
Target	Supplier object (onboarding + risk)
Requirement	Tenant required
Notes	Triggers Omnea’s onboarding questionnaire and TPRM checks when the supplier is new

Intent ID correlation

Carry the Intent ID

Mapping	Detail
Canonical to destination	intent_id, intent_version
Target	Custom field on the intake request
Requirement	Required
Notes	Field key agreed with the joint customer; read back onto the PO the ERP integration creates

Purchase Order

Result of the orchestrated flow

Mapping	Detail
Canonical to destination	po_number, supplier, amount, gl_code, dates
Target	PO created in the ERP via Omnea’s two-way integration (read)
Requirement	Read only
Notes	composerID records the PO reference on the intent timeline; the ERP, not Omnea, is the system of record

Omnea is an orchestration layer over the customer’s ERP, CLM, eSign and risk tooling, and its intake forms, approval chains and Workflow Builder logic are tenant-defined. Integration credentials, base URLs and any webhook specifications are provisioned by Omnea during onboarding; the public material describes the integration surface, not endpoints. Note the domain is omnea.co.

Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.

⌘I

Get started

Concepts

Guides

Destinations

Upstream connectors

API reference

Endpoints

Manuscript API (Triage)

Manuscript endpoints

Resources

Integration path

Vendor documentation

Omnea: platform overview

Omnea: Workflow Builder

Omnea: approval workflows

Omnea: automated PO creation

Omnea: build vs buy (integration surface)

API posture

Publish target and field mapping

Next steps

How composerID connects

Publishing

All destinations

​Integration path

​Vendor documentation

Omnea: platform overview

Omnea: Workflow Builder

Omnea: approval workflows

Omnea: automated PO creation

Omnea: build vs buy (integration surface)

​API posture

​Publish target and field mapping

​Next steps

How composerID connects

Publishing

All destinations

Integration path

Vendor documentation

API posture

Publish target and field mapping

Next steps