Connectors
Pick a trigger. Point it at an agent. Ship. Eleven connectors cover HTTP, queues, schedules, databases, and real-time streams. No glue code, no workers to run.
Featured
HTTP Webhooks
By ConnicRun an agent on any HTTP request. Accepts JSON, form data, and file uploads — no glue server in between.
Cron Scheduler
By ConnicRun an agent on any cron expression. Daily digests, hourly health checks, weekly audits — no scheduler to host.
MCP Server
By ConnicExpose your agent as an MCP tool. Call it from Cursor, Claude Desktop, or any MCP-aware client.
All connectors
HTTP Webhooks
By ConnicRun an agent on any HTTP request. Accepts JSON, form data, and file uploads — no glue server in between.
Cron Scheduler
By ConnicRun an agent on any cron expression. Daily digests, hourly health checks, weekly audits — no scheduler to host.
Apache Kafka
By ConnicConsume topics to trigger agents. Produce results back to topics. Built for high-throughput event streams.
WebSocket
By ConnicStream tokens to the browser over a live socket. Build chat UIs that keep session state across turns.
MCP Server
By ConnicExpose your agent as an MCP tool. Call it from Cursor, Claude Desktop, or any MCP-aware client.
AWS SQS
By ConnicDrain SQS queues with an agent. Visibility timeouts, retries, and dead-letter handling are already wired up.
AWS S3
By ConnicRun an agent the moment a file lands in a bucket. Extract from PDFs, caption images, transcribe audio.
PostgreSQL
By ConnicHook an agent into LISTEN/NOTIFY. New rows fire an event in milliseconds — no polling, no CDC pipeline.
Email (SMTP/IMAP)
By ConnicRead an inbox to trigger an agent. Reply with a drafted message over SMTP. Attachments included.
Stripe
By ConnicRun an agent on any Stripe event — payment_failed, subscription.updated, dispute.created. Webhook signing is handled.
Telegram
By ConnicPower a Telegram bot with an agent. Read user messages, reply in the chat, push alerts to any channel.
How connectors work
Three steps between an external event and a running agent.
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.
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.
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.