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

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 2

How to create Solution

Accepted Answer

Before the creation

Creating your own Solution, you will choose automations for various scenarios. Therefore, the automations scenarios that will form the basis of your Solution should be created in your account before you start creating the Solution.

Who can use your Solution

Currently users can create Solution:

for private use in their accounts. It suits you to create the same type of automations (for example, when setting up new advertising campaigns). In this case, you can create your Solution once and use it as a template for new automations.
to share the Solution with other Albato users. Click on the Share button, share your link and other users will also be able to use your Solution. More on that further down in the article.
for public use. You can make your Solution publicly available to all Albato users and it will be added to the Marketplace. Contact our technical support with such a request. Later this can be done via the interface.

Solutions builder

When you set up all the automations that are needed to create a Solution, go to the Solution builder.

Click the Create solution button, set a name for your Solution and select languages. These languages will be available to you and other users in case of publication. English is required by default and cannot be undone.

Then you will see the settings window of the created Solution. In this window you c

Question 3

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.

Question 4

Response

Accepted Answer

Set up the response parser in the Response tab for the completed HTTP request. The created fields will take values from the response and save them to the fields of the entity.

Unlike the Request tab, here in the right field select the displayed entity.

Content-type

Indicate the format of the request response to receive. Available options:

JSON
XML
urlEncoded

Specify the the request format in Response tab, as the request may be urlEncoded, and the response may be in JSON.

The response will be expected strictly in the selected format of the widget. If the response comes in a different format, parsing fails.

The path to the Array

Use this field if the response contains data in an array of unlimited objects (for example, API triggers that make a request to get a list of entities).

If the data in the response comes in this form:

{

"data":[

{

"name":"Ivan",

"phone":"+79681112233"

}

{

"name":"Vasiliy",

"phone":"+79681112244"

}

]

}

and you need to receive both objects, then put a check at a “Return data array” box. Specify the mapping to the array, in this case it is data. In the created fields, the mapping can be specified without a path to this array.

You can also check the box but leave the field empty, the data comes at the roo

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

API model

Accepted Answer

The API trigger makes requests to the app every five minutes. The main scenario is an entity list request, specifying dates (date of changing/creating from and to).

Create Requests widget for triggers, set up URL to send the request, add Authorization parameters, also set up the request body, response parser and error handling.

Dates in HTTP requests

The widget for the API trigger has two additional parameters in the “System parameters” tab: Request time (from) and Request time (to):

The first parameter Request time (from) transfer - 1 hour from the date and time of the bundle start. The second parameter Request time (to) transfer the date and time of the start. These parameters are dynamic and change automatically every five minutes. Specify these parameters correctly to Albato create and transfer it to the app when the bundle’s trigger starts.

As a result, the trigger gets a list of created/changed entities for the last hour every five minutes.

Get data array

Since the API trigger model requests lists of entities, an array of objects will be in response (an unlimited number of entities). The bundle’s trigger will start as many times as many entities are in the response. For example, if five deals are changed, the trigger will receive a list of changed deals. Changes will be transferred to the bundle; the bundle will start five times and all further steps will run five times.

Set up the “path to data array” field in the Response tab to make it work.

Frequently Read Articles

Browse All Categories