Workflow Sample: Automatic Posting to a Blog System (OAuth 2.0 Connection)

"Official Blog Site" of an enterprise is no longer unusual.
Or rather, it is getting to be 'for granted' as well as 'Website'. Needless to mention, it is very convenient for publicity of latest business information. It also could be a tool for communication with customers.

This article has taken the form of a blog of "Workflow sample", as well...
Questetra Inc., is running a blog called "Questetra Blog"...
(Whoops, the official blog of Google's, well well, how many would be there?)

The following Workflow definition, "Official Blog Publishing flow" is (obvious to look into the Process diagram, though) a mechanism that a draft which have reviewed will be automatically posted to blog system. I wish to ensure the readability and accuracy of the article through various devices such as "mechanical automatic cooperation" or "human reviewing process" as in this example.

[Official Blog Publishing flow]

[Official Blog Publishing flow:'2.Reviewing' screen]

[List of Process Data Item]

In this example, posting of the manuscript to the blog system is automated in HTTP communication. Because blog posting is a 'day-to-day operation' for the PR section, it is very convenient to reduce the incidence of mistakes for them. (Message Throwing Intermediate Event (HTTP))

It is OAuth 2.0-based communication that is a mechanism truly to symbolize the "Cloud era", that is very significant for "familiarize yourself with the OAuth 2.0" also.

* What is OAuth 2.0? ⇒ "What is “OAuth”, the Cloud Technology which Everyone should Know?"

Well though,,, if the blog system has a "post by mail function", it will be much easier rather to use Email Transmitting function (Message Throwing Intermediate Event (email)), than setting the API communication of OAuth 2.0 all the way. (About communication error, it is easier to detect with OAuth!)

By the way, the Calendar API communication which I have introduced in the last article(*), began with 'POST Request in plain texts (application/x-www-form-urlencoded)', this particular example it begins with 'POST Request in json text (application/json)'. For those who are in a position to operate or to manage the cloud service, you should also be noted "differences in the API specification to connect with", by all means.
* Cloud-based Workflow and Google Calendar (OAuth 2.0 federation)

[OAuth 2.0 communication parameter setting screen]

<HTTP Request to be sent>
POST https://www.googleapis.com/blogger/v3/blogs/#{data['1']}/posts?isDraft=true
Content-Type: application/json

{
"content": "Hello<br> Hello<br> Hello<br>"
"title": "A Happy New Year"
}

By the way, as of today, you cannot use the API of "Google Blogger" immediately. However, it will be available in about a week after making an application. I recommend you to make application as soon as possible, if you were interested.

* References of Blogger API: https://developers.google.com/blogger/docs/3.0/reference/posts/insert

[Download]