The connection was created incorrectly.
The client needs to follow the instructions to create a valid connection. Some applications require a webhook setup, while others need a special login and password or an API key for data transfer.
No administrator permissions.
In order to work with the API of some apps, the user must have administrator rights to create or modify the connection. For details, please refer to our blog, and the documentation of the service you are trying to work with.
Data transfer is not fully set up or the requirements for data transfer are not met.
In certain apps, internal processes must be tailored for data transfer, such as scripting. Beforehand, it's important to confirm the data transfer settings by reviewing the instructions or consulting technical support.
Trigger configured incorrectly.
Some triggers have settings that are required for correct data transfer.
Incorrectly filled action.
A user may incorrectly fill in fields when performing an action. For example, when creating a contact in a third-party app, the client could mistakenly enter a different parameter in the "email" field. Subsequently, the app waiting for an email would receive a wrong value and generate an error.
In most of the cases the name of the field will give you some hints related to the type of data the API service is waiting to receive, for example:
a field named "email" will most likely expect a string similar to "test@test.com".
an ID filed will most likely expect an integer value, eg "12323435345". Though in some cases it could also be a string, for example: "f55ac8df-26f8-41f5-b63a-fa80e97d2fec%7Cfe". When in doubt, please refer to the documentation in Albato's blog, and also the API docs of the service you are working with
Incorrectly filled-in incoming data filter.
If the message "Data did not pass the filter" appears, please check the automation log and select the "All Events" scenario from the "Filter Scenario" drop-down list. You may also temporarily remove the incoming data filter settings and test the data transfer if they do not fit the conditions of the scenario.
We recommend when working with text (strings) that you use the conditional containts, instead of equals. In some cases you may paste characters that are not visible, like extra spaces or new line characters, which will cause unexpected behavior.
Data is not transferred to the app.
This is most likely due to an incorrect parameter selection, an unfilled mandatory field parameter, or a parameter selected from another step.
For example, you may want to create an automation like this:
A lead is captured from a marketing form
This lead is sent to your CRM. A contact is either created, or updated
An order is linked to the contact in the CRM
You may encounter an error in step 3 if you don't send the lead ID comming from the CRM itself in step 2. A common error is that we send the lead ID from the trigger, but this ID will not be recognized by the CRM, hence an error will appear.
After updating the connection, the data fails to load.
You must verify if the account providing the connection has the necessary rights. This error may be caused by a lack of access rights. Alternatively, the request was received successfully, but the third-party app has queued the data for updating. The length of time it takes to update depends on the data of the third-party account. It is advisable to wait for some time. If the data is not received, please contact our technical support.
Google Sheets updated a row, but no new data came.
If your users have Google Sheets automation, it is important to note that only technical sheets can be used. Users shouldn’t modify the appearance of the rows and columns by changing their colors, deleting them, or using formulas. Before setting up any automation, it is important to read the rules for Google Sheets.
Link a contact/task to a transaction.
Create a new contact and fill in the necessary details to link a contact/task to a transaction. Then, proceed to create a new deal, and in the Contact ID field, select the "Contact ID" parameter from the previous New Contact step.
Tags or some values are not coming.
There are cases when requests for tags or other values are made during an automation, but they come to Albato empty and are not displayed in the Log. If you encounter this issue during an automation, feel free to reach out to Albato's technical support.