Connector Builder

Build and deploy custom connectorsin minutes, not days

Point Connector Builder at a source API, test the stream, and publish a connector your workspace can run. It's that easy.

Get started freeRead the docs

The problem

Catalogs have limits. Custom glue takes weeks.

Pre-built connectors cover the popular sources. The rest of your stack still needs a connector you can test and publish yourself.

  • Catalogs stop at the long tail

    Your warehouse still needs the regional ERP, the internal tool, and the vendor that is not in any marketplace.

  • Custom Python takes weeks

    Auth, pagination, incremental sync, and tests become a project. Then you own the glue.

Read a Real Connector Builder Success Story

How it works

From API docs to a connector your workspace can run.

Four steps in Connector Builder, from the start path through publish.

  1. 01

    Choose a start path

    Import a YAML manifest, fork a catalog connector, or start from scratch.

  2. 02

    Configure the stream

    Set the endpoint, auth, pagination, and schema in the UI or in YAML.

  3. 03

    Test the live API

    Run the stream in the Test panel and confirm records before you publish.

  4. 04

    Publish to your org

    Use the connector in your workspace, or contribute it back to Airbyte.

Get started freeRead the docs

Start here

Import YAML, fork a connector, or start from scratch.

The same three start paths you see in Cloud. Pick the one that matches the API you need to sync.

  • Import a YAML manifest

    Select an existing low-code YAML manifest from your computer to import into Connector Builder.

  • Fork an existing connector

    Select an existing connector to use as a starting point, then edit streams to match your API.

  • Start from scratch

    Build a connector from start to finish in the form, with YAML available when you want it.

Get started free

AI Assistant

Paste a docs URL. Review the draft.

Enable AI Assistant, add a public API documentation URL or OpenAPI spec, and let Connector Builder suggest stream configuration. You still test and publish.

Get started freeRead the docs

Built in

Auth, schema, YAML, and publish.

Switch between the form and the declarative manifest. Detect schema, store secrets as encrypted user inputs, then publish to your organization or contribute to Airbyte.

  • UI and YAML

    Switch the same stream between the form and the declarative manifest.

  • Detected schema

    Detect fields from the records you pull in Test.

  • User inputs for secrets

    Enter custom secrets or tokens. They are saved encrypted, not hardcoded in YAML.

  • Publish or contribute

    Use the connector in your workspace, or contribute it back to Airbyte.

Get started freeRead the docs

FAQ

Didn't find your answer?
Please don't hesitate to reach out.

Talk to us

Yes, Connector Builder is designed for HTTP-based APIs, including both REST and GraphQL. It supports JSON, JSONL, CSV, and XML response formats, as well as gzip-compressed responses. For non-HTTP sources like databases, message queues, or object storage, use a pre-built connector or the Python CDK.

Yes. You can build and publish connectors in Airbyte Cloud, Flex, and self-managed deployments.

Connector Builder currently only supports source connectors, not destinations. Please talk to your Airbyte representative if you are interested in destinations.

Publish to your organization for private use, or choose Contribute to Airbyte from the Publish menu when you want to share it.

Connector Builder is the UI for declarative connectors, including YAML. The CDK is for language-specific connectors when you need more control than the declarative manifest.

No. Start from scratch in the form, import YAML, or fork a catalog connector. Switch to the YAML editor when you want to edit the manifest directly.

Build the connector your catalog is missing.

Free to start. Publish to your workspace when the stream tests clean.

Get started freeTalk to sales