3 min read

Workato 101: Everything You Need to Know

By Yogi Kanakamedala on Dec 2, 2021 10:15:00 AM

Workato 101 Blog Header

Workato is a powerful iPaaS (Cloud-Based Integration Solution) tool that enables your organization to integrate your go-to applications and automate workflows seamlessly. An easy-to-use, block-coding approach to building recipes allows you to unlock the ability to create limitless integrations and automation.

Building Blocks

Automations in Workato are defined by a recipe that contains step-by-step instructions on performing tasks or processes. A recipe is made up of two key components: a trigger and one or more actions. But before we can start looking at triggers and actions, we must first learn about application connections.

Application Connection

An application connection contains information that Workato uses to connect and authorize the use of an application. For each application, you need a new connection that has credentials to connect to the application. Workato uses the application's API to change its objects; therefore, it may require OAuth-based authorization, API keys, or other authorization methods.

First, make sure that your account has the necessary access to make changes within the instance.

For example, a connection made to Jira Cloud will require your email and API key, and a connection made to a hosted Jira environment will need your username and password. Once you make the necessary connections and Workato can access the application, a trigger can be configured to kick off the recipe.

Trigger

A trigger is the starting point for any Workato recipe, and almost any application can be configured to act as a trigger. Note, for all new applications, a new application connection is required. For example, a trigger can be a newly created issue in Jira. In this case, anytime a new issue is created, the recipe will start, and all of the tasks that you define are automatically executed.

Sometimes, triggers can be generic and could cause the recipe to run during unnecessary events. In this case, a trigger condition can be applied to eliminate excessive noise. To continue with the previous example, if you want to perform tasks on a newly created issue from only one project in Jira, then apply a trigger condition to ensure that the recipe starts when a new issue is created for that specific project.

Once the recipe's starting point is defined, you can add the subsequential actions required to complete—and eventually automate—your process.

Action

Before you start a recipe, you first need to define the process. This is done with the help of actions. An action is a single operation performed within an instance. For example, you can create issues or comments in Jira, post a message to Slack, update the standard of custom records in Salesforce, and much more.

Actions can also be logical elements such as conditions, loops, or error monitoring to help you create the desired automation. This can help perform more complicated processes and save time and resources for your business. For even more complex requests, you can run Ruby or JavaScript code as an action to help fill in the gaps between the built-in actions.

Next Steps

Workato is an effective tool when appropriately leveraged, unlocking the full potential of each device. Many of your day-to-day tasks can be automated to reduce human error and increase efficiency so your teams can instead focus on more critical tasks. For comprehensive information about any application connection, please refer to the Workato Documentation.

Our consultants are experienced in integrating a wide variety of technology platforms. Check out the press release on Praecipio Consulting receiving 2020 Workato Partner Award for IT Automations. We are ready to answer any questions you might have.

Contact us to learn more and see how you can maximize Workato to connect your go-to apps and align your entire organization with digital business goals.

Topics: workato integration strategic-solutions-expert
3 min read

How to Effectively Communicate Across All of Your Tools

By Morgan Folsom on Aug 5, 2021 12:33:48 PM

2021-q4-blogpost-Why more tools does not mean better communication_1

One of the coolest parts of working with the Atlassian suite is the ability to see the wide variety of industries that use the tools in different ways. In my role working with clients I have seen how every company has adapted the tools slightly differently to make them work best for their processes, and help them make that process even smoother.

 While doing so I get to see firsthand how they communicate internally and externally. 

It becomes clear that while many of the tools that we use in our day-to-day jobs are great at facilitating communication, it can be hard to figure out exactly which tool we should be using for what. Here at Praecipio Consulting, I could reach out to my colleagues or clients lots of different ways – a Slack message, a comment on a Jira issue, a comment on a Confluence page, an email, or I could skip all of that and just call them directly. Sometimes, I'll see a combination – a Slack message to verify if a call is okay, or an email that follows a comment on a Jira issue to make sure that I've seen it. 

While Jira and Confluence is often the most direct way, many organizations run into the issue of mismanaged notifications that means people filter out all of their notifications (for detailed guides on how to fix that in either tool see How to Solve: "Too Many Jira Email Notifications" or How to Solve: "Too Many Confluence Email Notifications"). Ultimately, what's most important is that the team is consistent enough in their usage that you know where to find the information you need. 

Given that, here are my recommendations:

Jira

Use Jira comments for all communications specific to the issue at hand. This keeps the information tied to the subject, easy to find in the future, and permanent. You won't have to worry about having deleted an email if you've got all of the comments on the issue themselves. 

Confluence

Follow the same guide as above – if you've got a Confluence page about a subject, keep the collaboration in one place! You can use either inline comments or page comments to track the communication. Even resolved inline comments stick around, so if you need to reference this in the future, no problem. 

Chat (Slack, Teams, etc.)

Great for informal chats, quick clarifications, and funny gifs – but I try to keep any official decisions either out of the chat, or copied to the issue/page that holds the content on the subject we're discussing. If you're using a tool like Workato to integrate your Jira and Slack instances, you can even have your Slack messages added to the issue directly. 

Email

If you're going to be emailing about a ticket, just include the issue key in the Subject and CC your Jira email address, and the email will be added to the comments of the issue. This way, for folks who prefer working in email, the communications aren't lost. Otherwise, I try to send as few emails as possible.

Call (Phone, Slack, Zoom, etc.)

I'm a millennial, so let's just say this is rarely my first choice. Most of the time, for quick conversations I prefer chat, but, especially as more workers are moving remote, this can replace the quick stop by your desk that you may be used to. 

Ultimately, the above is how I manage communications internally and with clients, but which tool you use for which purpose is far less important than that you're consistent. The less time you have to spend hunting down information the better, so agree as a team how you'll communicate and stick to it!

If you are having trouble managing your teams' communications, contact us and one of our experts will be glad to help.

Topics: jira best-practices confluence workato workflows culture slack

Praecipio Consulting is an Atlassian Platinum Partner

This means that we have the most experience working with Atlassian tools and have insight into new products, features, and beta testing. Through our profound knowledge of Atlassian environments and their intricacies, we can guide your organization as you navigate these important changes.

Atlassian-Platinum-Solution-Partner

In need of professional assistance?

WE'VE GOT YOUR BACK

Contact Us