Skip to main content

Pluga Glossary

In this article we will discuss some of the terms and expressions we use here at Pluga

Fátima Catarino avatar
Written by Fátima Catarino
Updated over 2 months ago

Action

What will happen after the trigger is activated. For example: in the automated workflow For each opportunity reported as a sale on RD Station CRM, create a sale in Conta Azul, whenever an opportunity is reported as a sale on RD Station CRM, a new sale will be created in Conta Azul.

API

A type of interface that web systems created to facilitate communication between them. It works like an access gateway, and it is through the APIs that Pluga has access to the data from the source app and is able to send data to the target app. Think of it this way: for a person to be able to communicate with another, there are different gateways, right? WhatApp, Slack, phone… For two robots to be able to communicate, they need an API. 😉

Automation

The connection between two web apps that executes a specific task for you. It is composed of two parts, which are the trigger and the action. The logic is this: when something happens in app A, perform an action in app B.

Some examples of automations are:

  • When a new row is created in Google Sheets, create/update a lead in RD Station Marketing

  • For every payment approved at iugu, a notification is sent to a specific channel on your Slack

  • For every opportunity reported as a sale on RD Station CRM, create a sale in Conta Azul

Here at Pluga there are three types of automated workflows:

  • Regular Automation: those that can be implemented with the Free plan.

  • Premium Automation: those that demand greater care and require more personalized support. For this reason, they are only available with Pluga's paid plans. You can check out all the functionalities available in each plan here.

They can be distinguished from the regular automations by their black border in the automation card:

Event

The act of transferring data from App A to App B automatically, meaning the number of times a given automated workflow is performed. Take for instance the automation For each opportunity reported as a sale on RD Station CRM, create a sale in Conta Azul, if 10 opportunities are reported as a sale in RD Station CRM, 10 sales will be created in Conta Azul, and, with this, 10 events will be counted. You can learn more about the status of each event here.

History (Log)

Where the events processed by your automated workflow in the last three months are stored. Each History (Log) saves the events for that automation. You can learn more about the History (Log) and how it can help you by checking out this article. You can also download the information in your History (Log) whenever you want, and this article shows you how to do that!

Mapping

Where you set up the fields for your automated workflows, indicating which information from the source app should go to each field in the target app. The mapping is configured when each automated workflow is created, but it can be edited at any time, and this article shows you how.

Trial

A test period that allows access to all paid features for 7 days.

Trigger

What activates your automation. For example, in the automation For each opportunity reported as a sale on RD Station CRM, create a sale in Conta Azul, the trigger is when an opportunity is reported as a sale in the RD Station CRM.

Usage

The number of active automated workflows and the amount of events that they have had in the current cycle. You can check this on your subscription and usage dashboard.

Webhook

A way of integrating web systems that allows messages to be sent and actions performed through an URL generated by the app that receives the data and performs the commands.

Are any terms missing? Just contact us. 😊

Questions?

If you still have questions, just click on the chat button at the bottom right and start a conversation with us or send an email to: support@pluga.co

Did this answer your question?