Skip to main content

What can we help you with?

How to trigger an ElectroNeek bot from Zapier

g.melihov
  • Updated

Introduction

The ElectroNeek platform supports integration with the Zapier automation service. Zapier has only one action applicable to ElectroNeek - "Launch bot". This action serves as a trigger for the bot published to Orchestrator. In this article, we will look at a simple example of an algorithm that is triggered by Zapier.

 

‌Preriquisities

Let's assume that you already have access to Zapier and the ElectroNeek RPA is available there. Basically, there are 4 steps required for ElectroNeek bots to work with Zapier:

  1. Create a bot in ElectroNeek Studio Pro;
  2. Publish the bot in Orchestrator;
  3. Assign Bot Runner to this bot;
  4. Create Zap.

So, in the ElectroNeek ecosystem, you need to have access to Bot Runner and Orchestrator SaaS. Access to Studio Pro is optional, as you can work with a bot already created by someone else.

 

Connecting to Zapier

As described above, to connect to Zapier you need to create a bot, publish it to Orchestrator, and assign Bot Runner to it. You can read about how to do this in these articles:

Once everything is ready on the ElectroNeek side, you can proceed to create the Zap. To do this:

  1. Navigate zapier.com and log in;
  2. Press "Create Zap";
    Screenshot_253.png

  3. Select the trigger you want. Follow the instructions on the screen (in some cases you need to check the trigger, authorize accounts, and so on);
    Screenshot_255.png

  4. On the "Action" page, select "ElectroNeek RPA";
    Screenshot_256.png

  5. In the "Action event" parameter, select "Launch bot";
    Screenshot_257.png
  6. Press «Sign in to ElectroNeek RPA»;
    Screenshot_258.png
  7. You will see a page with the token input field. To generate a token, navigate to "Orchestrator" → "Integrations" → "Zapier";
  8. Test the process - the pop-up message will open again. You will see the returned values: workflowUid, workflowName, workflowDescription, timeStamp:
    1. workflowUid - contains a unique identifier of the algorithm that can be used to find the bot in Orchestrator:  https://electroneek.com/account/orchestration/scripts/{{workflowUid}}
    2. workflowName - contains the name of the launched bot;
    3. workflowDescription - contains the description of the bot that you specify when publishing bots to Orchestrator;
    4. timeStamp - contains the date and time when the request to launch the bot was sent. 
  9. If everything works - run Zapier, the bot will run under the specified conditions.

Note:

  1. The "Launch bot" action only launches the bot, it doesn't wait for the bot to finish working, and does not reflect the work status in any way. This will be handled in a separate way in the future.
  2. We improve our product quite often, so check the instructions if something goes wrong: the steps may change.

Related articles