Access key: Credentials needed to connect your account in a specific app to Albato (and subsequently to another app).

Action: Automation steps that are executed instantly whenever a trigger fires. Actions typically make changes to data; e.g., creating, updating, or deleting records.

API: An API call is a request made by an application to another system to fetch or update data, often using defined protocols and endpoints.

Application: An app that can integrate with other systems either via API or a webhook. 

Apps: In the “Apps” section, you can see all apps and connections created within your Albato account.

Automation: An integration scenario involving multiple apps and a certain logic. Each automation has a trigger (an event that kicks off the automation) and one or more actions.

Automation groups: Users can group their automations based on their personal needs.

Automation status: This shows the current status of an automation (started, paused, deleted, etc.)

Connection: An integration between Albato and your account on another app. You can set up automations with the connected apps and move data between them.

Filter: A filter lets you set conditions in the first automation step to filter out unwanted data from entering your automations.

Operation: A successfully completed step in an automation scenario, e.g.: Lead received, Message sent, Contact updated, etc.

Steps: Each automation includes X steps in its scenario. Automation steps include a trigger, one or several actions, and, optionally, internal Albato tools.

Template: An automation template with pre-defined apps and integration scenarios. Your customers can run templates with just a few clicks, and without needing to build workflows from scratch.

Trigger: An event that happens in a sending app and starts an automation. A trigger is always the first step of any integration scenario. Triggers can fire in real time or on a schedule. Triggers can work either through API or webhooks.