Skip to main content
Connic

Connectors

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

All connectors

16 matching entries

Telnyx Voice

By Connic

Answer incoming calls on your Telnyx number with a voice agent. Connic configures call routing and streams the conversation.

Sync
View details

Telnyx Messaging

By Connic

Receive and send SMS/MMS, WhatsApp, and RCS messages through your Telnyx account. Connect agents to customer conversations and notifications.

InboundOutbound
View details

HTTP Webhooks

By Connic

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

InboundOutboundSync
View details

Cron Scheduler

By Connic

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

Inbound
View details

Apache Kafka

By Connic

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

InboundOutbound
View details

WebSocket

By Connic

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

Sync
View details

MCP Server

By Connic

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

InboundSync
View details

AWS SQS

By Connic

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

InboundOutbound
View details

AWS S3

By Connic

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

Inbound
View details

PostgreSQL

By Connic

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

Inbound
View details

Email (SMTP/IMAP)

By Connic

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

InboundOutbound
View details

Stripe

By Connic

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

Inbound
View details

Telegram

By Connic

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

InboundOutbound
View details

Slack

By Connic

Connect a Slack bot to Connic. Trigger agents from mentions or send agent outputs to Slack channels.

InboundOutbound
View details

Twilio Messaging

By Connic

Receive SMS, MMS, WhatsApp, and RCS messages with an agent. Send replies, media, and WhatsApp templates through your Twilio account.

InboundOutbound
View details

Twilio Voice

By Connic

Answer incoming calls on your Twilio number with a voice agent. Use its tools and knowledge throughout one continuous conversation.

Sync
View details

How connectors work

Three steps between an external event and a running agent.

  1. Create and configure

    A connector and its configuration are selected in the dashboard. Connic provisions the endpoint, consumer, or schedule behind it, with nothing else to host.

  2. Point it at an agent

    Incoming events can route to any agent in the project. The payload arrives as structured input for the agent code.

  3. 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, or an inbox. Configuration happens 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. Teams configure credentials and routing; Connic handles scaling and retries. 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 first-party calls and 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.