Robolytix

Robolytix is the key online analytic and monitoring tool for Robotic Process Automation using Sonar technology to evaluate, audit, monitor and improve performance of robots operating on any application or RPA platform.

Getting started with Robolytix

Prerequisites

  • A Robolytix account

To use Robolytix with Integromat, it is necessary to have a Robolytix account. If you do not have one, you can create a Robolytix account at Robolytix.com

Connecting the Robolytix service to Integromat

To connect your Robolytix account to Integromat, follow the general instructions for Connecting to services.
When creating a connection, you are asked to provide an API key. To get your key, log in to your Robolytix account and follow the instructions. Generating API key is in more detail described in Robolytix documentation.
There are two main steps.

1. From the left navigation menu, select Settings. On the Settings page, select API keys in the menu and then click on New API key button.

Integromat-Robolytix-04-graph.png

2. Copy the unique key and add a new connection to Integromat with this key:

Integromat-Robolytix-07-graph.png

Overview

Process monitoring

Process monitoring is performing by using Sonar checkpoints. The Sonars are at the beginning of the process, the end(s) of the process, and any other points in the process between start and end(s).

Sonar Technology

The Sonar Technology allows you to place Sonars in any process, including hybrid solutions, processes that use a variety of tools and applications, including possible interaction with people.

Sonars can be located in the Integromat process, but also in parts of the process outside of Integromat. So you can watch the whole process online, not just the robotic part.

Robolytix collects real-time data from all Sonars (including those outside Integromat) and represents them as KPIs in dashboards.

Actions

Sonar

Each Sonar embedded in the process contains the following settings:

Connection Establish a connection to your Robolytix account.
Name The name of the Sonar should reflect the state of the process that indicates passing through this checkpoint.
Process Select a process from the list. The list contains all processes from your Robolytix account. If you don't see your process in the list, make sure the process you want is existing in your Robolytix account.
Type

The type of sonar determines its location within the process:

  • Start
    is the first checkpoint in the process,
  • Continuous
    are checkpoints anywhere in the process. Of course, more continuous Sonars means more powerful statistics,
  • End
    is the last checkpoint in the process. The process can have one or more "end" Sonars in different branches of the process.
  • Error
    a special type designed to receive error information for specific modules in the Integromat scenario. It is inserted by the "Add error handler" function of the module.

Process run identification

The process run begins with its start, which is the first pass of “start” Sonar this process. It continues through “continuous” sonars to “end” Sonar(s). For advanced reporting, we recommend identifying each separate run process by a unique identifier.

The unique identifier must be a variable generated by “start” Sonar and passed to all other Sonars in the process.

If the process starts in Integromat, we recommend using the “runid” variable of the starting sonar. Use the following trick to do this:

While editing the scenario, run this scenario to pass Sonar "start” successfully, whereby Integromat creates the "runid" variable for this scenario. Then edit all remaining sonars in the process. The “runid” variable that you add as a unique identifier is available in their settings.

Integromat-Robolytix-09-graph.png

If your hybrid process continues with sonars in other tools and applications outside of Integromat, you need to ensure that this variable is transmitting.

If run identification is not set, Robolytix stores the total number of Sonar passes. There are no extended outputs about the time course of such a process. However, in some cases, this is entirely sufficient. Therefore, run identification is an optional setting.

Popular use cases from our blog

automated-data-collection-crm-illustration

How to Automate Data Collection - Part 5: CRM Systems

automated-data-collection-chatbot-marketing-illustration

How to Automate Data Collection - Part 4: Chatbot Marketing

automated-data-collection-paid-ads-illustration

How to Automate Data Collection - Part 3: Paid Ads

automated-data-collection-email-illustration

How to Automate Data Collection - Part 2: Email Marketing Segmentation

personalized-customer-experience-illustration-integromat

5 Automated Solutions to Personalize Customer Experience

data-collection-automation-forms-pt-1

How to Automate Data Collection - Part 1: Online Forms

Didn’t find what you were looking for?

Expert

Find an expert

We feature a network of 450+ certified partners across the globe who are ready to help

Find an expert

Automate any workflow in your business

Sign up for a free account today. No credit card required, no time limits on free plan.