Integrations
Helix connects to the tools your business already uses. Every integration routes through the App Marketplace — deploy once, serve all your brands.
The integrations above are built by cAND/or.
Every card on this page carries a "Built by cAND/or" mark — these are first-party connectors maintained by the team that builds Helix. They are tested, versioned, and supported as part of the platform.
But the App Marketplace is not a closed ecosystem. The same architecture that powers NinjaOne and Stripe is published as an open standard that any vendor can implement.
Connector Manifest Specification
Helix publishes a versioned Connector Manifest — a documented contract specifying how a third-party connector declares its fields, data flows, capability directions, and authentication method. A vendor who implements the spec appears in the App Marketplace alongside cAND/or-built integrations.
Bidirectional by Design
Third-party connectors support the same bidirectional flows as first-party ones — your platform can talk TO Helix via webhooks and inbound routing, and Helix can talk TO your platform via REST API calls. The data direction is declared in the manifest and displayed to the operator exactly as you see it on this page.
Marketplace Governance
Control how team members can self-provision integrations.
Require approval for all self-provisioning
When on, all team members must request manager approval before connecting any integration.
Require approval for community & third-party integrations onlyRecommended
Team members can freely connect built-in Helix integrations (AI providers, M365, Google), but need approval for community-submitted or custom integrations.
Open self-provisioning
Team members can connect any integration from the App Marketplace without approval. Audit log records every connection.
Build a connector. Join the marketplace.
The Connector Manifest Specification ships with the Helix API Platform. Third-party connectors are published through the cAND/or developer portal.