How can I use Automation to convert a page into a live doc?

Thom_q27683

Hi,

I use mailtowiki to email Microsoft Teams Meeting AI Recaps to my "personal" Confluence Space (replacing OneNote FTW!) and I have 10 to 20 meetings a week.

It's easy to email into Confluence but manually converting every page auto generated by mailtowiki into a Live Doc is robbing me of the typical Atlassian-induced joy I get from power using Jira & Confluence.

Not sure if I'm just missing the action or if it isn't yet possible.

How often are new actions being introduced into automations?

The flow would look something like this:

1. Send Email to mailtowiki: address I created for meeting notes
2. mailtowiki creates the page as instructed
3. Confluence Automation sees the page created & converts it to a live doc.

Is there a place where I could request this feature & track the possibility of a dream becoming reality?

Long Time Atlassian-lover,

-Thom

Darryl Lee

Hi @Thom - there's actually a way to do this via an Undocumented API endpoint.

(Disclaimer: Undocumented API endpoints are undocumented for a reason. Atlassian could change them whenever they want. I mean, they usually don't, but it's possible. That means your automation here would break. But you'd get an email notification about it, so that's ok, you can come back here and ask how to fix it :-)

Basically to figure this out, I watched what calls my web browser made when I converted one of my pages to a Live Doc, and then put that into an Automation Web Request.

So ok, assuming mailto.wiki is creating pages in the same Space, and that's the _only_ thing creating pages in that Space, your rule would look something like this: (You could also add a condition to check for specific labels, etc.)

Here's the details of those fields:

Web request URL

https://YOURSITE.atlassian.net/cgraphql?q=ConvertToLivePageDialogConvertPageToLiveEditMutation

Custom data

[{"operationName":"ConvertToLivePageDialogConvertPageToLiveEditMutation","variables":{"contentId":"{{page.id}}"},"query":"mutation ConvertToLivePageDialogConvertPageToLiveEditMutation($contentId: ID!) { convertPageToLiveEditAction(input: {contentId: $contentId}) { success errors { message __typename } __typename }}"}]

Headers

Content-Type: application/json

Authorization: Basic BASE64EMAIL:TOKEN

---

So how it works is, when the page is published, the rule sends a web request to convert to a live doc (again, this is the same request that happens when you manually click to convert a page to a live doc and confirm it.)

The Custom data sent includes the {{page.id}} Smart Value, which is the ID of the page that was just created.

To authenticate this call, you need to include the Authorization header, which will be your email address + your API token, base64 encoded. There's details on how to get that here:

Automation for Jira - Send web request using Jira REST API 

Anyways, it's ugly, but until Atlassian gives us a proper public API to do this, or better still, an Automation action, it will probably work fine.

OH, you might be wondering, will this work with the new Atlassian Service Accounts that were launched a few months ago. Well, I just tested, and I'm pretty sure the answer is NO, as I got this error: "Unauthorized; scope does not match", and I had enabled nearly all the Confluence scopes. Ah well... Like I said, it's unofficial. :-}