serverless-toolbox VS blog-crossposting-automation

I recently discovered you can ask ChatGPT to return a json object as a response, so I updated the AskChatGPT function in the serverless toolbox to accept an outputFormat property so it could automatically parse the response as json and return it to my workflow. Now with a single call, I can ask for a json object with all the writer analytics I want to track, which results in an output like this:

I'm happy to release the first version of my serverless toolbox - a GitHub repo that deploys a set of functional tools that you can integrate into your applications with loose coupling mechanisms.

In essence, his solution works like an automated assembly line for your blog posts. Once you write a post and commit it to your main branch on GitHub, AWS Amplify verifies the content and if everything checks out, a Lambda function retrieves your post and sets a workflow in motion. This workflow simultaneously transforms and publishes your post across Medium, Hashnode, and Dev.to.

This Lambda function is implemented in my blog crossposting app. It is called from a state machine to post articles to various publications. In this project, I created a Lambda function to generate payloads specifically for this function to use as simply as possible.

The code above shows how I use GitHub's SDK, octokit, to list commits in my repository in the past few minutes. Full source code here.