Custom Connectors
fyrn can generate a connector for any REST API using AI. Provide an API documentation URL, a natural language description, or an OpenAPI spec file, and the AI builds a complete connector definition with actions, authentication, and request/response schemas.
Building a custom connector
Section titled “Building a custom connector”From API documentation
Section titled “From API documentation”fyrn connector build https://api.acme.com/docsThe AI crawls the documentation, identifies endpoints, auth methods, and data schemas, then generates a connector definition.
From a description
Section titled “From a description”fyrn connector build "Acme CRM REST API with OAuth2" --name acme-crmFrom an OpenAPI spec
Section titled “From an OpenAPI spec”fyrn connector build --spec ./openapi.yaml --name acme-crmAll three methods produce the same output: a connector added to your account’s private catalog with actions, auth configuration, and schemas ready to use in flows.
AI action cost
Section titled “AI action cost”Building a custom connector consumes AI actions from your plan quota:
| Plan | Cost per connector build |
|---|---|
| Free | 5 AI actions |
| Team | 5 AI actions |
| Business | 3 AI actions |
| Enterprise | 1 AI action |
Each iteration (re-generation, refinement) also costs AI actions.
Production limits
Section titled “Production limits”| Plan | Custom connectors in production |
|---|---|
| Free | 1 |
| Team | 5 |
| Business | Unlimited |
| Enterprise | Unlimited |
OAuth setup
Section titled “OAuth setup”For connectors that use OAuth2, run the connect command to start the authorization flow:
fyrn connector connect my-acme-instanceThis prompts for OAuth client credentials, opens a browser for authorization, and polls for completion. Once connected, check the status:
fyrn connector status my-acme-instanceOutput includes connection state, token expiry, and authorized scopes.
Connector sharing
Section titled “Connector sharing”On Business and Enterprise plans, custom connectors can be shared org-wide. Any team member can create instances from a shared connector without rebuilding it.
On Enterprise, a private connector registry provides a curated internal catalog of your organization’s custom connectors, with version control and access policies.
Using custom connectors in flows
Section titled “Using custom connectors in flows”Once built, custom connectors work exactly like built-in connectors. Reference them by instance name in your flow YAML:
flow: acme-syncversion: 1source: connector: shopify-production trigger: webhook event: orders/createtarget: connector: acme-crm-instance endpoint: /api/orders method: POSTmapping: order_id: source.id customer_email: source.customer.email | lowercase total: source.total_price | decimal(2)on_error: retry: 3x exponential(30s) then: dead-letterManaging connectors
Section titled “Managing connectors”# Browse the connector catalog (built-in + custom)fyrn connector catalog
# List configured instancesfyrn connector instances
# Test a connectionfyrn connector test <instance-id>What’s next
Section titled “What’s next”- Connectors — Browse all built-in connectors
- Creating Flows — Use connectors in flows
- Plans & Limits — Connector limits per plan