Reference

Integrations Catalog

The live integration surface — every cloud, ERP, commerce, messaging, and SaaS domain registered in the production workflow catalog, with links to per-workflow reference

Every integration on Orkestia is a family of workflows under a dotted namespace — there are no bespoke connectors with their own semantics. That means every row below behaves identically: discover the types, read a schema, satisfy prerequisites (usually a connection), start a run. This page is the map; the per-workflow truth (exact names, typed schemas, prerequisites, outputs) lives in the reference catalog.

Counts are a snapshot of the production registry (2026-08-26, ~2,700 registered types) and grow as libraries ship. A namespace's presence here means it is live in production — not roadmap.

Cloud providers & infrastructure

Namespace	Workflows	What it covers
`aws.*`	~480	The deepest port — EC2, S3, IAM, EKS/ECS, RDS, Lambda, Cognito, CloudFront, cost & billing (Cost Explorer, CUR, Budgets), and more
`gcp.*`	~100	Compute, GKE, Cloud Run, Cloud SQL, BigQuery, billing, IAM, storage
`mgc.*`	~90	Magalu Cloud — compute, Kubernetes, DBaaS, LBaaS, networking, object storage, registry
`azure.*`	~60	AKS, ACR, compute, networking, DNS, Front Door, Key Vault, blob storage
`kubernetes.*`	~80	Cluster-agnostic Kubernetes — deployments, jobs, manifests, RBAC, pods, services
`cloudflare.*`	~60	DNS, Pages, Workers, R2, queues, tunnels, cache
`neon.*`	~45	Serverless Postgres — projects, branches, databases, roles, data APIs
`runner.*`	~200	Runner provisioning and lifecycle across AWS, Azure, GCP, DigitalOcean, Magalu, Kubernetes
`cluster.`, `deploy.`, `network.`, `registry.`	~75	Managed cluster VMs, deploy surfaces (k8s, Cloud Run, static, domains), network topology, image registries

Smaller DNS/CDN ports: vercel.*, netlify.*, bunnycdn.*.

Finance & ERP

Namespace	Workflows	What it covers
`xero.*`	~235	Full Xero accounting surface — invoices, credit notes, payments, contacts, purchase orders, quotes, reports, journals
`bling.*`	~50	Bling ERP (Brazil) — the system-of-record integration for orders, finance, and catalog
`stripe.*`	~35	Payments — checkout, subscriptions, invoices, customers, refunds, disputes, webhooks
`sap.*`	~15	SAP — connection plus journal-entry and business-document sync
`abacatepay.*`	~36	AbacatePay (Brazil) — Pix, checkouts, subscriptions, payouts, coupons, webhooks

Commerce & food delivery

Namespace	Workflows	What it covers
`ifood.*`	~58	iFood merchant — orders, events, reviews, reconciliation, catalog
`data.commerce.*`	~12	The commerce data layer — normalized entities and sync cursors shared across commerce integrations

Namespace	Workflows	What it covers
`docusign.*`	14 live (full eSignature surface in catalog)	Envelopes, signing, templates, brands
`slack.*`	~13	Messages, channels, approvals, webhooks
`telegram.*`	~14	Bots, messages, updates, callbacks
`wasender.*`	~7	WhatsApp messaging sessions
`meta.*`	~25	Facebook & Instagram — content, media, comments, ads
`linkedin.*`	~6	Posts and ads
`google.ads.*`	~4	Google Ads
`youtube.`, `publisher.`, `media.*`	~23	Shorts, publishing calendars/posts/reviews, media artifacts & brand profiles

Developer & SaaS tooling

Namespace	Workflows	What it covers
`github.*`	~85	Repos, pulls, checks, actions, releases, installations, code search
`firecrawl.*`	~22	Web crawling, scraping, extraction, research
`typesafe.*`	1	TypeSafe Jev — typed choice / score / noul via `typesafe.systemone.evaluate` (guide)
`sentry.*`	~7	Issues, projects, organizations
`notion.` · `repligit.` · `lovable.*`	~10	Notion pages, git mirroring appliances, Lovable projects

How every integration is used

1. Discover      list_workflow_types(prefix="xero.")
2. Read schema   get_workflow_schema("xero.invoices.create-invoice")
3. Prerequisites get_workflow_prerequisites(...)   # usually: create a connection
4. Run           start_workflow(...)               # org-scoped automatically

Connections (the credential/grant a namespace needs) follow the same pattern as AWS connections and DNS providers: the org connects once, workflows resolve the connection at run time, and RBAC governs who — human or agent — may use it.

Integrations compose. The point of a uniform catalog is cross-domain compositions: an iFood order event feeding Bling, a Lumen error opening a ticket, a Stripe payment triggering a DocuSign envelope — each is input mapping between typed workflows, not glue code.

API & Tooling

The programmatic surfaces for driving Orkestia workflows — the REST API, the typed Node/TS SDK, and the two-token auth model

Platform Services