Welcome to Albato Help

Albato Copilot


IN THIS ARTICLE

Albato Copilot helps new users understand how Albato works without technical complexity, while enabling experienced users to build automations faster and more efficiently.

Albato Copilot is a separate feature available as a chat inside the Albato interface. With it, you can create, set up, and launch automations using a text description of your task.

To start using Albato Copilot, click the button in the left sidebar after signing in to your account.

copiloten1.png

In the chat window, describe the workflow you want to automate, answer a few follow-up questions, and launch the automation.

copiloten2.png

Copilot saves all your requests in the History tab. You can return to previous conversations, manage them, and edit your requests.

copiloten3.png
 

What Copilot can do

Albato Copilot can:

  • create new automations from scratch based on a task description;
  • edit existing automations, including ones created manually;
  • set up field mapping inside steps;
  • answer questions about Albato, since it is connected to the knowledge base and documentation.
 

How Copilot works

Working with Albato Copilot starts with a simple chat.

  1. You describe your task, for example: "I want to receive notifications when a calendar meeting is canceled".
  2. During the conversation, Albato Copilot asks follow-up questions. After you describe the task, it will clarify which app connections should be used.
  3. If those connections are not set up yet, Copilot will suggest how to create them.
  4. Based on your answers, Albato Copilot creates the automation.
  5. After all details are confirmed, you can move on to the final review and launch the automation.
  6. The completed automation will then appear in your account.

You can see an example of how Albato Copilot works in this video:

 
 

Current limitations

We continue to improve and train Albato Copilot, and more features will appear in future versions.

Like any AI assistant, it cannot guarantee that all data and logic will always be correct. Errors are possible, so we recommend reviewing every automation carefully before using it in a live workflow.

Did this answer your question?