IMAP
Email-in for tickets and lead capture from a shared inbox.
Last updated 2026-05-05
The IMAP integration polls one or more inboxes (typically a [email protected] shared mailbox) and converts incoming messages into Tickets, Leads, or replies on existing threads. Routing rules — by recipient address, subject regex, or sender domain — pick which entity to create. TLS connections are required; the service refuses STARTTLS-less hosts. Polling interval is per-mailbox (default 60 seconds, minimum 30) and runs in the worker app.
For richer two-way mail (drafts, sent items in your real inbox) use the Google / Microsoft OAuth integration instead — IMAP is fire-and-forget read-only.
Related endpoints
GET /api/tenant/imap/inboxes— list configured inboxes.POST /api/tenant/imap/inboxes— add an inbox (host, port, user, encrypted password).POST /api/tenant/imap/inboxes/:id/test— test the connection without saving.POST /api/tenant/imap/inboxes/:id/poll-now— manual poll (admin).
See the source at apps/web/src/app/(tenant)/settings/integrations/imap and apps/worker/src/jobs/imap-poll.ts.