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 rounded snapshot of customer-facing namespaces on 2026-11-03. They move as libraries ship. A registered type is a capability, not a count of production runs. Tenant apps and operator namespaces are not listed on this page.
Cloud providers & infrastructure
| Namespace | Workflows | What it covers |
|---|---|---|
aws.* | ~480 | EC2, S3, IAM, EKS/ECS, RDS, Lambda, Cognito, CloudFront, cost and billing, and more |
azure.* | ~110 | AKS, ACR, compute, networking, DNS, Front Door, Key Vault, blob storage |
gcp.* | ~100 | Compute, GKE, Cloud Run, Cloud SQL, BigQuery, billing, IAM, storage |
mgc.* | ~90 | Magalu Cloud API — compute, Kubernetes, DBaaS, LBaaS, networking, object storage, registry. This is not a runner backend |
kubernetes.* | ~110 | Cluster-agnostic Kubernetes — deployments, jobs, manifests, RBAC, pods, services. A separate k8s.* set is not this row |
cloudflare.* | ~400 | DNS, Pages, Workers, R2, queues, tunnels, cache, and the rest of the Cloudflare API |
hostinger.* | ~390 | Domains, DNS, VPS, and billing on a Hostinger account |
argocd.* | ~100 | Argo CD applications and sync |
neon.* | ~55 | Serverless Postgres — projects, branches, databases, roles, data APIs |
runner.* | ~490 | Runner groups on AWS, Azure, Google Cloud, and Kubernetes |
spad.* | ~90 | Cloud Deploy — static sites on your cloud account, not App Host |
cluster.*, deploy.*, network.*, registry.* | ~75 | Managed cluster VMs, deploy surfaces, network topology, image registries |
Smaller DNS and site ports: vercel.*, netlify.*, bunnycdn.*.
Finance & ERP
| Namespace | Workflows | What it covers |
|---|---|---|
xero.* | ~235 | Invoices, credit notes, payments, contacts, purchase orders, quotes, reports, journals |
omie.* | ~85 | Omie ERP (Brazil) |
mercadopago.* | ~80 | Mercado Pago payments on a connected account. Not a settlement rail for Agent Exchange |
bling.* | ~50 | Bling ERP (Brazil) — orders, finance, and catalog |
abacatepay.* | ~55 | AbacatePay (Brazil) — Pix, checkouts, subscriptions, payouts, coupons, webhooks |
stripe.* | ~40 | Payments — checkout, subscriptions, invoices, customers, refunds, disputes, webhooks |
sap.* | ~15 | SAP — connection plus journal-entry and business-document sync |
Checkout is the agentic checkout product. It is not a payments-provider row on this page.
Documents, messaging & social
| Namespace | Workflows | What it covers |
|---|---|---|
docusign.* | ~430 | Envelopes, signing, templates, brands |
wasender.* | ~65 | Unofficial WhatsApp session gateway. Not the official WhatsApp Cloud API |
whatsapp.* | ~23 | Official WhatsApp Cloud API |
meta.* | ~25 | Facebook and Instagram — content, media, comments, ads |
telegram.* | ~14 | Bots, messages, updates, callbacks |
slack.* | ~16 | Messages, channels, approvals, webhooks. Separate from Lumen alert webhooks |
email.* | 9 | Your own mailboxes (IMAP/SMTP or Microsoft 365 / Outlook.com) — list, search, read with attachments, mark read, poll for new mail, send after human approval (guide) |
linkedin.* | ~6 | Posts and ads |
google_ads | 1 | One Google Ads workflow. Not the whole google.* namespace |
youtube.*, publisher.*, media.* | ~40 | Video, publishing calendars, posts, reviews, media artifacts, and brand profiles |
Developer & SaaS tooling
| Namespace | Workflows | What it covers |
|---|---|---|
github.* | ~150 | Repos, pulls, checks, actions, releases, installations, code search |
openai.* | ~45 | OpenAI API calls through a connection you grant |
linear.* | ~24 | Linear issues and projects |
firecrawl.* | ~22 | Web crawling, scraping, extraction, research |
sentry.* | ~9 | Issues, projects, organizations |
notion.* | 1 | Notion pages |
lovable.* | 3 | Lovable projects |
typesafe.* | 1 | TypeSafe Jev — typed choice, score, or noul via typesafe.systemone.evaluate (guide) |
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: a Lumen error opening a ticket, a Stripe payment triggering a DocuSign envelope — each is input mapping between typed workflows, not glue code.