Step One: Head down to the Workato site to start a trial of the platform - we're going in!

Minus the personal projects, recipes, and connections I already have in place, your portal should more or less look like this:

Now, for this lab, we are going to need to have:

• An OpenAI (platform.openai) account
• A Slack account
• A Google Drive account
• An Outlook account
• and a can-do attitude!

We will step through creating the project container and setting the necessary connections in this video:

Now that our space is ready and our connections are set - it's time to get cookin'!

First off - let's conceptualize what we would like to achieve in this lab before we get the carriage in front of our horse! We want a recipe that will trigger when we schedule an Outlook event. OpenAI will be used to extract and analyze vital meeting details, and message our team in Slack. IF the meeting is for issues with HTML connections, we will be amending a file in our team's Google Drive folder that helps prioritize and organize specifically HTML-related troubleshooting, which we will also confirm in the Slack chat. But IF HTML is NOT (IF NOT = ELSE) the topic of the meeting, Slack will send a message acknowledging that HTML is not the focus, so documentation will be kept in the chat but nothing more.

Whew - so let's break this down!

Step 1: We will build a recipe that is triggered when an Outlook event is created.

Step 2: We will then leverage the power of OpenAI's text analyzer to extract subject and body fields.

Step 3: We will have a message sent in Slack confirming meeting to team.

Step 4: Save Recipe & Test 1st Half!

But we're not done!

Just when you thought it was safe to go outside - BAM. THE SEQUEL!

Step 5: Before we continue on with the recipe, take a moment to go and delete the event we just created in Outlook. Careful not to clutter your real calendar with fake lab events! Then go into your Google Drive and create a Folder called "Blog Lab."

Step 6: IF the Slack message text contains "HTML Issues" (precisely, cap-sensitive), we will be amending a file containing the meeting details in Google Drive. This is for prioritization, documentation, and visibility to team and higher-ups.

Step 7: IF condition was meant, Slack will send a message confirming that the new issue and upcoming meeting have been logged in the team Drive.

Step 8: ELSE, Slack will say that since it's not an HTML-related issue, it will not be amended to the Drive folder.

Thank you so much for joining TTB today for this fresh, more experimental approach to a blog. We'd love your feedback in the comments below about your feelings regarding more interactive multi-media posts in the future!