Connic
Connectors

Overview

Connect your agents to the outside world. Connectors enable your agents to receive triggers, send results, and integrate with external systems.

Enterprise Integrations

Connect agents to any system

Connectors are integration points that define how agents are triggered, how they receive input, and where they send results. Each connector can be linked to one or more agents. When triggered, it dispatches the input to all linked agents.

Multi-Agent Linking

Connect one trigger to multiple agents simultaneously

Multiple Modes

Inbound, outbound, and sync integration patterns

Secure by Default

Built-in authentication and encryption for all connectors

Connector Modes

Connectors operate in one of three modes, each designed for different integration patterns:

Inbound

Fire-and-forget async triggers

Outbound

Deliver results externally

Sync

Request-response pattern

Inbound Mode

Fire-and-forget triggers for asynchronous agent runs

Inbound mode is designed for fire-and-forget scenarios. When an inbound connector receives a request, it immediately queues the agent run and returns a response with the run ID.

Best for:

  • Background processing tasks
  • High-volume webhook ingestion
  • Event-driven architectures
  • When you don't need immediate results

Response:

{"status": "ok", "run_ids": ["uuid-1", "uuid-2"]}

Outbound Mode

Deliver agent results to external destinations

Outbound mode sends agent results to an external URL when runs complete. This is useful for integrating with external systems that need to receive agent outputs.

Best for:

  • Sending results to external APIs
  • Integrating with third-party services
  • Building event pipelines
  • Notifying external systems

Outbound Payload:

{ "run_id": "uuid", "agent_name": "my-agent", "status": "completed", "output": "Agent response..." }

Sync Mode

Request-response pattern with immediate results

Sync mode waits for the agent to complete and returns the result in the same HTTP response. This provides a traditional request-response pattern.

Best for:

  • REST API integrations
  • Interactive applications
  • When you need immediate results
  • Short-running agent tasks

Response:

{ "status": "ok", "result": { "run_id": "uuid", "output": "Response..." } }

Default timeout is 5 minutes. For longer tasks, use Inbound mode with an Outbound connector.

Ready to connect?

Create your first connector from the marketplace. HTTP Webhooks are a great place to start as they let you trigger agents from any system that can make HTTP requests.