How can I use Automation to convert a page into a live doc?
5 answers
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. :-}
Oh, so you or others might be thinking:
"Undocumented API Endpoint?! That sounds DANGEROUS!!!"
Well. Not really.
The worst case scenario? Your page doesn't get converted to a Live Doc.
If you examine the "code" above (which is mainly the Custom data and the URL above, you'll see that the only thing the call is doing is:
convertPageToLiveEditAction
No more. No less.
So if they change that action's name, or the name of the operation, your page won't convert, and you'll get an email when it fails.
But that's about it.
OH OH, from a security standpoint, once you get the rule working, you'll want to check the "Hidden" box next to your Authorization header, so if another admin edits the rule or exports all the rules, they will not have your API token:
(And in reality they wouldn't have your actual API token (since it's Base64 encoded), but they'd have a valid Authorization header to be able to do all kinds of API calls as your account. Which you probably don't want.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.