Can you send an email to Confluence Cloud?

The short answer

No. Confluence Cloud has no inbound email address, not for a page, not for a space, not for the site. Creating a page or space from an email is one of the oldest open requests on Atlassian’s tracker: filed in 2004, still “Gathering Interest”, with 253 votes at the time of writing (Atlassian: CONFCLOUD-1726). A newer request, “Email into Confluence”, notes that the feature exists only in Confluence Server and Data Center (Atlassian: CONFCLOUD-79455). People keep asking on Atlassian Community too, for example “Email to Confluence” and “Email management within Confluence”.

Data Center is different. It can create pages and blog posts from email sent to a configured mailbox, and a space can archive a mailbox (Atlassian: Create content with email, Mail Archives). If you moved from Server or Data Center and used those, this is why they are gone.

Way 1: save the email and put it on a page by hand

The method that always works. In Outlook, save the email as a file (classic Outlook: File → Save As, which gives a .msg; the new Outlook and Outlook on the web download an .eml or .msg) and upload the file to the page, or copy the text into the page, or print the email to PDF and attach that. The text becomes searchable page content but loses the attachments and headers; the PDF keeps the look but not the attachments; the .msg or .eml keeps everything but shows as a file. How to put an Outlook email on a Confluence page walks through all three with the Atlassian and Microsoft sources.

The weak spot is discipline: somebody has to remember, every time, and a thread of twenty emails is twenty uploads.

Way 2: automation that calls the Confluence API

Confluence Cloud has a REST API that can create a page (Atlassian: Confluence Cloud REST API, pages). An automation tool that watches a mailbox and can make an HTTP request can therefore turn “new email in folder X” into “new page under parent Y”: Power Automate, Zapier, Make, n8n or a small script of your own.

• What you get. A page per email, without anyone lifting a finger, and the text is searchable.
• What it loses. Attachments and inline images need extra steps (upload them as attachments, then reference them), HTML email bodies rarely survive the conversion to Confluence’s page format cleanly, and the technical headers are gone unless you store them too.
• What it costs. Someone has to build and maintain it, with an API token that may write to the space.

Way 3: a Marketplace app that gives a space an address

Some apps on the Atlassian Marketplace add an inbound address to Confluence Cloud: email sent to it becomes a page, or an attachment on a page. Points worth comparing before you install one: where the email is processed (the vendor’s servers or inside Atlassian), what happens to attachments, whether the original .eml is kept, and who can send to the address. An inbound address is an entry point into your wiki, so spam matters. MailView, the app Dortus makes, does not do this.

Way 4: if the emails are requests, use Jira Service Management

Often the real need is “customer emails should end up somewhere the team sees them”. That is what Jira Service Management is built for: it receives email at a project address and creates a request per email, with the attachments (Atlassian: Receive requests from an email address). Its knowledge base can live in a Confluence space, so the answers end up in Confluence while the emails stay in Jira (see Forwarding emails into Jira Service Management).

Once the email is on the page: keeping it readable

Ways 1 and 3 often end with a .msg or .eml file attached to the page. Confluence Cloud shows it as a file, not as an email; previewing .msg files is an open request (Atlassian: CONFCLOUD-74736). Readers download it and open it in a mail app, which fails on a Mac or a phone for .msg.

Full disclosure: Dortus makes MailView for Confluence. It shows an attached .msg or .eml as a readable email on the page: insert the Email (MailView) macro, pick the attachment, publish. Readers see sender, recipients, date, the formatted message, the images stored inside the email and its attachments, plus a phishing verdict with reasons. Emails on this page, under the page title, lists all email attachments of the page. The email is read in the reader’s browser; MailView keeps no copy and sends nothing outside Atlassian. It does not give the space an email address, and it does not copy the text into the page, so if people must find the email with Confluence search, paste the key text as well. Files over 10 MB show a download link. Confluence Cloud only; a Confluence admin installs it and it needs an active license.

Which way fits

An occasional email that belongs with a page: save it and attach it (Way 1), with MailView or a PDF beside it if readers should see it on the page. A steady stream of emails that should become pages: automation (Way 2) or an app with an inbound address (Way 3). Emails that are really requests: Jira Service Management (Way 4), with Confluence as the knowledge base.

FAQ

Questions

Spotted something wrong on this page, or a way we missed? Email support@dortus.com.

See also: How to put an Outlook email on a Confluence page, How to open .msg and .eml attachments in Confluence and Outlook .msg vs .eml