Skip to main content
connic

Connect your agents
to the systems you already run.

A connector gives an agent a webhook URL, a queue consumer, a schedule, an inbox or a phone number. connic hosts it, and every event becomes a run you can trace.

All connectors

33 matching entries

How a connector reaches your agent

Each connector supports one or more modes. The mode decides which way data moves between the system and the agent.

Inbound
An event starts a run on every linked agent. A webhook answers right away with the run IDs.
Outbound
Results go out when a run finishes, or when the agent or its middleware sends them during the run.
Sync
The caller waits for the answer in the same exchange, as with a sync webhook, a WebSocket session, an MCP tool call or a phone call.
  1. Add the connector

    Create it in the dashboard, or declare it as a YAML file in connectors/ that deploys with your agents.

    connectors/support-inbox.yaml
  2. Link agents

    One connector can start several agents, and an agent can listen to several connectors.

  3. Events become runs

    Agent Runs shows which connector started each run and keeps its input, so you can run it again.

  4. Results go back

    An outbound connector posts the result, replies in the channel or publishes the message.

Connectors FAQ

A connector links agents to another system. Inbound connectors start runs from events such as an HTTP request, a Kafka message, a schedule or an email. Outbound connectors deliver results, and sync connectors answer in the same exchange. connic hosts the endpoint, consumer or scheduler behind each one.

Inbound connectors start agent runs from outside events. Outbound connectors send results to other systems. Sync connectors keep the request open and return the agent's answer in the same exchange, as in a WebSocket chat, a sync webhook or a phone call.

No. connic runs the endpoints, consumers, pollers and schedulers behind each connector. You add the credentials and choose which agents a connector starts. Learn how pre-built connectors replace integration glue.

Use a connector for events from other systems. It gives each source its own URL or subscription, secret, mode and result delivery, and every run records which connector started it. The REST API is for managing and observing a project from your own code and tests.

Yes. Every connector type can be declared as a YAML file in connectors/. Each deploy creates, updates or retires those connectors for its environment, and a rollback restores them. The connectors in code docs list every field.

Connectors are included with the platform. The runs they start use Project credit at the published run, compute and storage rates.