Q: Solutions

<h2 id="whataresolutions">What are Solutions?</h2> Solutions are ready-made cases for automation. In fact, Solution is a set of pre-configured automation templates that allows you to install and run a whole set of automation scenarios. You can create a Solution in your account and then share it with other users (more on that further down in the article). <h2 id="whatismarketplaceandmyinstallations">What is Marketplace and My installations?</h2> Marketplace is a section where you can find all available Solutions created by users. On the Marketplace, you can choose the Solution that suits your needs (as well as the scenario, if there are several of them), add the Solution to your account and use it. At the same time, each Solution can be changed according to your own personal needs - for example, add another scenario. Users select Solution and install it in their accounts. When the Solution is installed, it appears in the My installations section. It is a private copy that can be modified or started only by the user. This means that any changes you make to the Solution in the My installations section will not affect the original Solution on the Marketplace. Vice versa, if the original Solution on the Marketplace is updated, this will not affect the one that is already in your account. <h2 id="howtoinstallsolutions">How to install Solutions?</h2> Choose the Solution you need and click the Install button. <img src="https://storage.crisp.chat/users/helpdesk/website/d71b68b4c7a6c80/image_ce6bi4.png" alt="Find solution and click &quot;Install&quot;" /> Choose the scenario you want to inst

Q: Webhook model

A distinctive feature of this type is - the “Requests” tab always has a trigger with the first request widget that cannot be deleted. It consists of the only one Response tab. The reason is that the trigger responds to the incoming request, therefore it’s important to set up the response parser and select the content-type . For webhook triggers to work, create a field with the Webhook type in the Connection Fields tab. Check the Response to set up the tab. If you put a check on “Data array return”, the trigger in an automation will start for each entity when several objects (entities) arrive in the event. <img src="https://storage.crisp.chat/users/helpdesk/website/8e8a1b1770fa1000/3fe5e967-bc57-4d6b-bc94-2481ce_qduz9r.png" alt="" /> <h3 id="triggerfilter">Trigger filter</h3> This trigger has opportunity to set up filter. The setting is available in the list of triggers. Use static values to set up the filter. <img src="https://storage.crisp.chat/users/helpdesk/website/4a4e993c8cdd3000/d30a2d20-0176-4d3b-bb07-971e00_1dnn9a3.png" alt="" /> If the app uses one Webhook trigger, the filter setting is optional. This filter will start at any request. If there are more than one trigger, set up each trigger to make it work. Specify filters with one or more conditions using AND/OR operator between them. In the left field of each condition specify the variable key of the request., Start the value with data. if the variable is in the body of the request, with headers. if it is in headers. Follow the usual mapping rules. Sele

Question 1

New Google Sheets trigger

Accepted Answer

This trigger lets you keep track of all updates in the cells of your sheet. Trigger works by Webhooks and sends an event immediately when a cell is updated and a row is added.

You’ll need to make additional adjustments to your spreadsheets setup to use this trigger. First, connect your Google Sheets account to Albato.

Connecting Google Sheets to Albato

How to set up spreadsheet

Open your spreadsheet which you want to use in the integration
Go to the Extensions section → Apps Scripts
Remove the data and paste this code:

function generateData(e) {

let ss = SpreadsheetApp.getActive();

var spreadsheetName = ss.getName();// Spreadsheet Name

var sheetName = ss.getSheetName();// Sheet Name

var spreadsheetId = ss.getId();// id листа

var row = ss.getCurrentCell().getRow();// Row number

var column = ss.getCurrentCell().getColumn();// Column number

var values = ss.getActiveRange().getValues();// Array of new data

var user = e.user;// The user who made the changes

var date = new Date();// Date

sendWebhook(spreadsheetName, sheetName, row, column, values, user, date, spreadsheetId);

}

function sendWebhook(spreadsheetName, sheetName, row, column, values, user, date, spreadsheetId) {

var endpoint = "<https://webhook.site/ded7da72-670e-4a86-86aa-f13c9343455d>";

var jsonarray = JSON.stringify;

var payload = {

`"spreadsheetName" : spreadsh

Question 2

How to connect Wordpress to Albato

Accepted Answer

Currently, we have 3 methods available to connect Wordpress to Albato.

Application password
Basic Authentication
Jwt Token (Plugin)

**1. Application password **

On Wordpress interface:

You need to create a password in Wordpress, by going to User → Profile. type any password and save it.

The created password is displayed 1 time, you need to copy it and paste it into Albato.

On Albato’s interface:

You need to put the login from your admin Wordpress in the field “login”.
Put the password you created in Wordpress in the field “Password”

if you don’t have the ability to create a password in Wordpress, then you need to use a different type of authorization.

**2. Basic Authentication ** This type of authentication needs only your Wordpress user login and password. You need to use it if you are operating on a WordPress version

Question 3

Solutions

Accepted Answer

What are Solutions?

Solutions are ready-made cases for automation. In fact, Solution is a set of pre-configured automation templates that allows you to install and run a whole set of automation scenarios. You can create a Solution in your account and then share it with other users (more on that further down in the article).

What is Marketplace and My installations?

Marketplace is a section where you can find all available Solutions created by users. On the Marketplace, you can choose the Solution that suits your needs (as well as the scenario, if there are several of them), add the Solution to your account and use it. At the same time, each Solution can be changed according to your own personal needs - for example, add another scenario.

Users select Solution and install it in their accounts. When the Solution is installed, it appears in the My installations section. It is a private copy that can be modified or started only by the user. This means that any changes you make to the Solution in the My installations section will not affect the original Solution on the Marketplace. Vice versa, if the original Solution on the Marketplace is updated, this will not affect the one that is already in your account.

How to install Solutions?

Choose the Solution you need and click the Install button.

Find solution and click "Install"

Choose the scenario you want to inst

Question 4

What are "operations" and how do I count them?

Accepted Answer

Operations are the most important Albato unit for measuring the amount of data that has been transferred.

Let's get into detail about how to count an operation.

An operation in Albato is a run of an automation step. It means that each automation step creates one operation. The number of operations will differ for automations with API and webhooks triggers. Let's take a look at both examples.

How to count operations with a webhook trigger

When setting up an automation, pay attention to the icon next to the trigger’s name to identify the data transferring mode.

This is a webhook icon.

How do we count operations? Here is an example.

This automations has three steps.

Since Facebook is a webhook trigger, Albato doesn’t make any requests to receive the data. Facebook will send data (webhook) to Albato when a trigger occurs. This automation will spend three operations for a single run.

If we set up the Incoming data filter for the trigger, and it filters out the data, then we spend only one operation. Albato doesn’t charge for the filter operation in a trigger. You pay only for new data received by a trigger.

Ho

Question 5

Webhook model

Accepted Answer

A distinctive feature of this type is - the “Requests” tab always has a trigger with the first request widget that cannot be deleted. It consists of the only one Response tab.

The reason is that the trigger responds to the incoming request, therefore it’s important to set up the response parser and select the content-type .

For webhook triggers to work, create a field with the Webhook type in the Connection Fields tab.

Check the Response to set up the tab. If you put a check on “Data array return”, the trigger in an automation will start for each entity when several objects (entities) arrive in the event.

Trigger filter

This trigger has opportunity to set up filter. The setting is available in the list of triggers. Use static values to set up the filter.

If the app uses one Webhook trigger, the filter setting is optional. This filter will start at any request. If there are more than one trigger, set up each trigger to make it work.

Specify filters with one or more conditions using AND/OR operator between them. In the left field of each condition specify the variable key of the request., Start the value with data. if the variable is in the body of the request, with headers. if it is in headers. Follow the usual mapping rules.

Sele

Question 6

App Integrator Workflow

Accepted Answer

Create an app, name it, then, if necessary, create an authorization to configure a method for obtaining and updating authorization data, such as "Access token" and a "template" for filling an API request with authorization data. Further, you can use the created authorization in other entities, therefore, it will not be necessary to add variables each time in requests, in which the authorization data is placed.

Additionally, you can create the entities that are required to work with the integration. For example, “lists”, which can be static and dynamic, “lists of custom fields” and “webhook catcher”, all these entities are related to triggers or actions.

Create a trigger or an action, depending on what is required of the integration, the necessary fields are created, additional entities are attached, and the behavior of the API request is configured.

Featured & Frequently Read Articles

Browse All Categories