Connectors

Pick a trigger, point it at an agent, and ship. Eleven connectors cover HTTP, queues, schedules, databases, and real-time streams. Connic handles the glue code and runs the workers.

Quickstart Connectors Docs

Featured

HTTP Webhooks

Run an agent on any HTTP request with JSON, form data, or file uploads. No glue server is required.

InboundOutboundSync

Cron Scheduler

Run an agent on any cron expression. Connic hosts the scheduler for daily digests, hourly health checks, and weekly audits.

MCP Server

Expose your agent as an MCP tool. Call it from Cursor, Claude Desktop, or any MCP-aware client.

All connectors

HTTP Webhooks

Run an agent on any HTTP request with JSON, form data, or file uploads. No glue server is required.

InboundOutboundSync

Cron Scheduler

Run an agent on any cron expression. Connic hosts the scheduler for daily digests, hourly health checks, and weekly audits.

Apache Kafka

Consume topics to trigger agents. Produce results back to topics. Built for high-throughput event streams.

InboundOutbound

WebSocket

Stream tokens to the browser over a live socket. Build chat UIs that keep session state across turns.

MCP Server

Expose your agent as an MCP tool. Call it from Cursor, Claude Desktop, or any MCP-aware client.

AWS SQS

Drain SQS queues with an agent. Visibility timeouts, retries, and dead-letter handling are already wired up.

InboundOutbound

AWS S3

Run an agent the moment a file lands in a bucket. Extract from PDFs, caption images, transcribe audio.

PostgreSQL

Use LISTEN/NOTIFY to trigger an agent from new rows in milliseconds, without polling or a CDC pipeline.

Email (SMTP/IMAP)

Read an inbox to trigger an agent. Reply with a drafted message over SMTP. Attachments included.

InboundOutbound

Stripe

Run an agent on payment_failed, subscription.updated, dispute.created, or any other Stripe event. Connic verifies webhook signatures.

Telegram

Power a Telegram bot with an agent. Read user messages, reply in the chat, push alerts to any channel.

InboundOutbound

How connectors work

Three steps between an external event and a running agent.

01

Create and configure

Pick a connector in the dashboard and fill in its config. Connic provisions the endpoint, consumer, or schedule behind it; there is nothing for you to host.

02

Point it at an agent

Route incoming events to any agent in your project. The payload arrives as structured input your agent code can rely on.

03

Events trigger runs

Every matching event starts an agent run with retries, traces, and run history built in. Outbound connectors carry results back the other way.

Connectors FAQ

A connector is a managed trigger or channel that links an agent to an external system: an HTTP endpoint, a Kafka topic, a cron schedule, an inbox. You configure it in the dashboard, Connic runs the infrastructure behind it, and matching events start agent runs.

Inbound connectors trigger agent runs from external events. Outbound connectors let agents push results to external systems. Sync connectors hold a request open and return the agent's answer in the same exchange, like a WebSocket chat or a synchronous HTTP call.

No. Connic provisions and operates the endpoints, consumers, pollers, and schedulers behind each connector. You configure credentials and routing; scaling and retries are handled for you. Learn how pre-built connectors replace integration glue.

Connectors are the production path for triggering agents from external events. The REST trigger endpoint exists for your own first-party calls and for testing, not as a general integration surface.

Connectors are included with the platform. Runs they trigger use Project credit at the published run, compute, and storage rates.