Point an agent at an IMAP inbox and it triggers on every new message, attachments parsed and ready. Reply over SMTP with a drafted response. Support, sales, and AP workflows in one connector.
Overview
The Email connector speaks the two protocols every mailbox already supports. Inbound, it connects to the mailbox over IMAP and polls for new messages; each one is parsed into a clean payload with sender, subject, text and HTML bodies, and decoded attachments, then dispatched to the linked agents. Outbound, it connects to the SMTP server and sends whatever email the agent returns as JSON: recipient, subject, body.
Parsing email means handling MIME structures, encodings, attachment junk like tracking pixels and signature logos. The connector does that once, on both directions, so the agent works with structured fields instead of raw RFC 822 messages.
How it works
Get the mailbox credentials
Server, port, username, and password for IMAP (inbound) or SMTP (outbound). For Gmail, enable 2-factor authentication and create an App Password.
Create the connector and pick a mode
Add an Email connector from the agent's Connector Flow. Inbound (IMAP) triggers the agent on incoming mail; Outbound (SMTP) sends emails when linked agents complete their runs. Combine both for full reply loops.
Configure filters or the output format
Inbound: choose the mailbox folder to monitor and optional sender, subject, and unread-only filters. Outbound: have the agent return JSON with to, subject, and body, plus optional cc, bcc, html_body, and reply_to.
Production patterns
Patterns teams ship in production, with Connic running the queues, workers, and schedulers.
Email arrives
support@your-domain.comAgent classifies the issue, searches the connected help docs, and either replies with a fix or hands the thread to a human with the answer pre-drafted.
Email arrives
support@your-domain.comAgent classifies the issue, searches the connected help docs, and either replies with a fix or hands the thread to a human with the answer pre-drafted.
Inquiry received
sales@your-domain.comAgent scores the lead, looks up the company, and replies with a tailored message in under a minute. The full thread lands in the CRM with notes attached.
Inquiry received
sales@your-domain.comAgent scores the lead, looks up the company, and replies with a tailored message in under a minute. The full thread lands in the CRM with notes attached.
Invoice attached
invoices@your-domain.comAgent reads the attachment, pulls vendor, line items, and totals into clean JSON, and posts it to the accounting system. AP closes the month a week early.
Invoice attached
invoices@your-domain.comAgent reads the attachment, pulls vendor, line items, and totals into clean JSON, and posts it to the accounting system. AP closes the month a week early.
Schedule triggers
OutboundAgent writes a tailored report for each recipient. Execs see metrics, ops sees incidents. The report is formatted, signed, and sent over SMTP on schedule.
Schedule triggers
OutboundAgent writes a tailored report for each recipient. Execs see metrics, ops sees incidents. The report is formatted, signed, and sent over SMTP on schedule.
Inbound filtering and attachments
The connector monitors a mailbox folder (default INBOX) and can process unread messages only, filter by sender address or domain, filter by subject text, and mark processed emails as read. The agent payload carries from, subject, body_text, body_html, and an attachments array. Images, PDFs, text formats, and Office documents are included with their content (text as plain text, binary as base64); tracking pixels, favicons, and signature images are filtered out, and attachments over 10MB arrive as metadata only.
Every processed email becomes a normal agent run, with full traces, token and cost tracking, and the same guardrails and approval rules as any other trigger. Useful when the agent's reply goes to a real customer.
Sending mail from an agent
An outbound connector sends an email whenever a linked agent completes a run. The agent's response must be a JSON object with to, subject, and body, plus optional cc, bcc, html_body, and reply_to; an output schema keeps that shape reliable. Delivery goes through the configured SMTP server with TLS, credentials encrypted at rest, and automatic retry on transient failures. See the full payload formats and an example agent in the Email docs.
Information
- Publisher
- By Connic
- Connectors
- Connectors
- Modes
- Inbound, Outbound
- Documentation
- Email docs
Frequently Asked Questions
imap.gmail.com or smtp.gmail.com with an App Password: enable 2-factor authentication on the Google account, generate an app password for Mail, and use that 16-character password in the connector instead of the account password.Bring the event source, payload shape, result destination, and any private-network or approval requirements. We will map Email to the right Connic connector mode, deployment path, and observability setup.
Talk to SalesMore connectors
Browse the marketplaceTwilio Voice
Answer incoming calls with a voice agent
Cron Scheduler
Run an agent on a cron expression
Stripe
Run an agent on payment events
MCP Server
Expose agents as MCP tools
Twilio Messaging
Receive and send SMS, WhatsApp, and RCS messages
Telnyx Messaging
Receive and send SMS/MMS, WhatsApp, and RCS through Telnyx