Introducing Agent Connectors from Airbyte

Introducing Agent Connectors from Airbyte enabling AI agents to securely access, sync, and act on real-time data across your tools and systems.

AI AGENTS

December 16, 2025

3 min

Michel Tricot

Summarize with AI:

Introducing Agent Connectors from Airbyte

Today, we're launching Agent Connectors: open-source Python SDKs purpose-built to give AI agents consistent, real-time access to operational data for context-rich decision making.

This is the start of building the data infrastructure layer that connects AI agents to enterprise systems.

What We're Launching

Open-source Agent Connectors for 10 critical operational systems: Gong, Zendesk Support, GitHub, HubSpot, Salesforce, Jira, Asana, Stripe, Greenhouse, and Linear.

These are standalone Python packages you can use directly in your app or plug into any agent framework, giving your agentic applications strongly typed, well-documented access to third-party APIs. Each connector enables critical agent operations including fetch, search, and discovery in real-time.

Try them now:

Repo: Airbyte Agent Connectors
Docs: Available here

The Problem

AI agents are limited by the tools they can call. Most context lives inside SaaS APIs that hold CRM records, support tickets, billing events, recruiting pipelines, code repositories, and operational data. Yet giving agents reliable access to these APIs remains difficult.

Every integration becomes a custom wrapper, every schema behaves differently, and every edge case becomes another source of operational risk. None of these patterns support agents that need real-time decisions and just-in-time context retrieval.

The infrastructure layer between agents and operational systems doesn't exist. Everyone's building custom integrations, duplicating work, and creating reliability nightmares.

How Agent Connectors Work

Agent Connectors are standalone Python packages that wrap operational APIs with strongly-typed interfaces. Each connector handles authentication, validates schemas, and exposes operations through consistent method signatures that both developers and LLMs can interpret reliably.

from airbyte_agent_gong import GongConnector
from airbyte_agent_gong.models import GongAuthConfig

# Create connector
connector = GongConnector(
    auth_config=GongAuthConfig(
        access_key="...",
        access_key_secret="..."
    )
)

users = await connector.users.list(limit=10)

Attaching this to an agent is straightforward:

@agent.tool_plain
async def list_users(limit: int = 10):
    return await connector.users.list(limit=limit)

Under the hood, they derive typed request and response models from the underlying API specifications, enforce schema validation at runtime, and provide transparent error handling. This gives agents the low-latency primitives they need for real-time fetch, search, and action operations without the brittleness of ad hoc API wrappers or the staleness of batch ETL.

Each connector is delivered as an independent Python package with a predictable structure:

connectors/
├── gong/
│   ├── airbyte_agent_gong/
│   ├── pyproject.toml
│   ├── CHANGELOG.md
│   └── README.md
│   └── REFERENCE.md
├── github/
│   └── ...
└── ...

The REFERENCE.md file in each connector documents all available operations from listing sources to fetching specific records and executing actions. This gives both developers and Agents a complete map of what each connector can do. For example, the Gong connector reference details operations like ‘users.list(), users.get(), calls.list(), and more, with full type information for each.

Every connector can be used directly in a Python application, attached to frameworks like PydanticAI or LangChain, integrated into any custom agent loop, or exposed through MCP-based interfaces for tool-calling LLMs.

Why we’re building this

We've built a company on moving data reliably. We have 20,000+ GitHub stars, thousands of customers, and millions of pipelines synced daily. We've built and maintained hundreds of open-source connectors with a community of 27,000+ developers.

But as AI agents have emerged, I've noticed a challenge that dramatically limits their success: most enterprise APIs weren't designed for LLMs or agent execution models. As agents must interact with real operational systems, developers write custom wrappers, manage authentication constraints, normalize schemas, and handle inconsistent error behavior across every system their agent touches. This works at small scale but breaks when agents need to call multiple systems reliably.

Agent Connectors bring our connector expertise to agent workloads, providing a consistent way to fetch and search operational data without writing custom integration code for each system.

Why this matters

I think agentic AI represents the biggest shift in software since the move to cloud. But the infrastructure layer needed to make it work in production doesn't exist yet.

We're not building another agent orchestrator or LLM framework. We're building the connection between facts and intelligence: the data layer that every framework plugs into.

The companies that win with AI won't be the ones with the best models. They'll be the ones who figured out how to give those models reliable access to live business context.

What's Next

This launch is just the beginning. We're expanding Agent Connectors in two key directions:

Write Operations: Beyond read access, we're adding write and trigger capabilities so agents can create records, update fields, and initiate workflows across systems.
Connector Library Expansion: We're scaling from the initial 10 connectors to hundreds over the coming months, bringing the full breadth of our connector ecosystem to agent workloads.

We plan to continually expand the connector library using our expertise in data movement and community contributions to the open-source GitHub repo.

Learn more here.

Get Involved

This is open source for a reason. We are all in uncharted territory, however we all know that the future of AI is Open-Source. We want to work with all of you to define what agentic data infrastructure looks like.

Try the connectors: github.com/airbytehq/airbyte-agent-connectors
Give us a star ⭐ if you find it useful
Contribute: Join #agent-connectors-discussions on the Airbyte Slack to share your feedback
Talk to us: DM me on LinkedIn or X if you're building agents and want to discuss your data infrastructure needs

The future of AI depends on solving the data infrastructure layer. Let's build it together!