Channels
Email and Teams
IMAP/SMTP email and Microsoft Teams channel configuration.
Email and Microsoft Teams are more operationally sensitive than simple chat. They can involve spoofing risk, long-lived conversation references, and external delivery rules, so configure them deliberately.
The Email channel polls IMAP for inbound messages and replies through SMTP.
| Field | Meaning |
|---|---|
enabled | Start email polling. |
consentGranted | Must be true after explicit operator consent. |
imapHost, imapPort, imapUsername, imapPassword | Inbound mailbox connection. |
imapMailbox, imapUseSsl | Mailbox and TLS behavior. |
smtpHost, smtpPort, smtpUsername, smtpPassword | Outbound mail connection. |
smtpUseTls, smtpUseSsl | SMTP security mode. |
fromAddress | Sender address. |
autoReplyEnabled | Whether Facio sends email replies. |
pollIntervalSeconds | IMAP polling interval. |
markSeen | Mark messages as seen after processing. |
allowFrom | Allowed sender addresses or patterns. |
verifyDkim, verifySpf | Anti-spoofing checks. Keep enabled unless upstream filtering already handles it. |
allowedAttachmentTypes | Attachment MIME allow list. Empty disables attachment intake. |
maxAttachmentSize, maxAttachmentsPerEmail | Attachment limits. |
Use email only when there is an explicit workflow reason and the mailbox is dedicated to Facio. Avoid connecting personal mailboxes.
Microsoft Teams
Teams uses a built-in HTTP webhook server for Bot Framework activities.
| Field | Meaning |
|---|---|
enabled | Start the Teams webhook server. |
appId, appPassword, tenantId | Microsoft Bot Framework app identity. |
host, port, path | Local HTTP listener, default path /api/messages. |
allowFrom | Allowed Teams sender IDs. |
replyInThread | Keep replies threaded. |
mentionOnlyResponse | Response when the bot is mentioned without a task. |
validateInboundAuth | Validate inbound Bot Framework bearer tokens. |
refTtlDays | Retention for conversation references. |
pruneWebChatRefs, pruneNonPersonalRefs | Keep reference storage focused on useful conversations. |
For production, place the Teams webhook behind HTTPS and keep inbound auth validation enabled.