6 Concepts to Master Codeless Automation
Some days it seems impossible to get everything done. As time goes by hectic days become normal. Racing through tasks and grinding through the daily routines without missing a beat becomes a challenge. When keeping up becomes daily, burn out is right around the corner. After burn out comes the inevitable “dropping the ball”. Missing deadlines, forgetting to CC someone, people depending on you are left wondering. Companies are demanding more productivity but being overworked isn’t the answer.
With the rise of cloud computing the number of apps in the workplace has exploded. Performing redundant tasks in multiple places has become common practice. From posting the same link on multiple social media accounts to entering data in a project management tool followed by emailing the same information out. These redundant tasks are time consuming and error prone.
With the growing demands on the information workforce it’s become crucial to decrease the amount of time and energy spent on mundane day-to-day tasks. Fortunately, we’re entering a time of codeless automation, creating simple workflows without the need for programmers and complex systems. Millions are finding tools like Microsoft Flow to help them throughout their day. Daunting at first, process automation is built on a few key concepts. Once learned, you can unlock their potential to stop grinding and start adding business value.
For example, with the popular approval workflow you can manage the approval of documents or processes across several services including Salesforce, SharePoint, Dynamics CRM, OneDrive, Zendesk, or WordPress. Or create a workflow that automatically tweets every message you post to your Facebook page. Another option is to configure an automated email summarizing your tasks from Microsoft Planner or Trello. Once you grasp the core concepts, the possibilities are (almost) limitless.
A workflow is a trigger with one or more actions that should perform one task. Think of a workflow as a series of actions that need to be performed together. Many workflows will only perform one action. For example, you can tweet every time you post to a Facebook page. If using a toolset like Microsoft Flow you can add additional actions such as posting to LinkedIn AND tweeting every time you post to a Facebook page.
A trigger is simply an event that starts the workflow. Every workflow starts with a trigger and each workflow can only have one trigger. The workflow can be started manually, scheduled daily, or on any number of events from other apps. For example, a trigger can watch your inbox and start the workflow when you receive an email. Sometimes, the trigger will pull information into the workflow. If you create a trigger that starts when you receive an email the workflow will contain information about the email like the subject, from, and body of the email.
Actions are what you want to happen when a trigger is invoked. They can get data or make changes to apps. For example, an action can save an email to OneDrive, add a row to excel, or work with a third party app like Trello or social media. Other examples of actions include sending an email, posting a tweet, and starting an approval. Actions will always come after the trigger in the workflow.
Connectors are less obvious than triggers and actions. A connector is used to connect your workflow with other apps. For example, if you wanted to create a workflow to post tweets on Twitter your workflow would need to know what account your using and you will need to authorize the workflow to post tweets on your behalf. These permissions are stored in a connector. The connectors will typically be based on apps like Twitter, Outlook, or OneDrive.
A condition, also known as, if-then-else statements will execute a series of actions based on an expression. It sounds more complex then it really is so lets take a look at a couple of examples.
If X+1=3 then do Y else do Z. In this example, Y will execute if X equals 2. If X is not equal to 2 then the workflow will execute Z.
If you wanted to tweet only when we post a message to Facebook when the Facebook message includes the text #Tweet then we could use a condition. If Tweet text contains #Tweet then post to Twitter else do nothing.
Sometimes you want to run an action on each item in a group. For example, you may want to save email attachments to OneDrive. Since emails can have multiple attachments we would need to perform OneDrive’s save action on each attachment on the email. This type of loop is called a For Each loop. The for each loop will perform the action on each item in the group.