Skip to main content
CadreenResearch Preview
DocumentationAPI ReferenceGuides & Cookbooks
Back to Guides & Cookbooks

Custom connections

When Cadreen can't find a pre-built integration, it builds one for you.

What are custom connections?

Cadreen checks its integration marketplace (250+ pre-built connectors) and your registered API specs before connecting to a service. If none of those have a match, it can build a custom integration from scratch.

Cadreen runs four automated steps (research, design, build, verify). You review the result and approve deployment.

How does it work?

Research
Checks API docs and connectivity
Design
Wraps results in a connector contract
Build
Generates connector definition
Verify
Validates contract, reachability, governance
Deploy
You review and deploy after approval

When does Cadreen build a custom connection?

Only when no existing integration matches. Cadreen checks these sources first:

  • Pre-built integrations from the marketplace
  • API specs you've registered
  • MCP servers you've connected

If none of those have a match, Cadreen automatically starts building a custom integration.

How do I approve a custom connection?

After testing completes, Cadreen shows you a verification report. You can review what it built and what each tool does before approving.

Click "Use this connection" to deploy it. The custom integration then appears in your connected services like any other integration.

What can go wrong?

Authentication required

The API needs credentials Cadreen doesn't have. You can provide an API key or OAuth token when prompted.

Unclear documentation

If the API docs are sparse, Cadreen may not be able to build a reliable connector. You can provide additional documentation or a spec URL to help.

Rate limiting

Some APIs limit how many requests you can make during research. Cadreen will retry with backoff, or you can try again later.