Skip to main content
Automations let you define when Arca should take action automatically. Each automation watches for a specific trigger event, optionally filters it by conditions, then runs one or more actions. Automations run instantly in the background the moment the trigger fires.

​
Getting started

Go to Settings > Automations to see all automations in your workspace. From here you can create, enable or disable, edit, and delete automations.
Only workspace Owners and Admins can create, edit, or delete automations. Members and Viewrs can view the automations list but cannot make changes.

​
Creating an automation

1

Open the automations page

Go to Settings > Automations and click New automation.
2

Name your automation

Give your automation a descriptive name so it’s easy to identify in the list later, for example Close resolved bugs or Assign new tasks to team lead.
3

Choose a trigger

Select the event that should start the automation. Each trigger can have optional filters to narrow down exactly when it fires. For example, you can trigger only when a status changes to a specific value, or only when a task is moved to a specific list.
4

Add conditions (optional)

Conditions let you restrict which tasks the automation applies to. All conditions must be satisfied for the automation to continue. For example, you can limit the automation to tasks in a specific folder, or only tasks with a certain priority.
5

Add actions

Add one or more actions for Arca to perform when the trigger fires and all conditions are met. Actions are executed in order.
6

Save the automation

Click Save. The automation is enabled immediately and will start running the next time its trigger fires.

​
Triggers

A trigger is the event that starts the automation.

​
Task triggers

​
GitHub triggers

​
GitLab triggers

​
Conditions

Conditions narrow down which tasks the automation applies to. You can add any combination of the following:
  • Folder: the task must be in one of the selected folders
  • List: the task must be in one of the selected lists
  • Assignee: the task must be assigned to one of the selected members
  • Priority: the task must have the selected priority
  • Status: the task must have one of the selected statuses
  • Status category: the task’s status must belong to one of the selected categories (Pending, In Progress, Completed, or Cancelled)
  • Label: the task must have one of the selected labels
  • Custom field: the task must match the selected custom field value
Conditions use AND between categories and OR within a category:
  • If you select multiple values in the same category (e.g. two statuses), the task matches if it has any one of them.
  • If you add conditions from different categories (e.g. a status and a priority), the task must satisfy all of them.
For example: Status is In Progress or Done AND Priority is High the task must be high priority and have either of those statuses.

​
Actions

Actions are the changes Arca makes to a task when the automation runs. You can add multiple actions to a single automation (subject to your plan’s action limit).

​
Task actions

​
GitHub actions

​
GitLab actions

​
Notification actions

​
Managing automations

Each automation card on the Settings > Automations page shows the automation name, its trigger, and how many times it has run.
  • Enable or disable: Use the toggle on any automation card to turn it on or off without deleting it. A disabled automation will not run until re-enabled.
  • Edit: Click the edit icon on any automation card to open it and make changes.
  • Delete: Click the delete icon to permanently remove an automation. This cannot be undone.

​
Automation history

The run count on each automation card shows how many times the automation has executed successfully. When an automation runs, the action is also recorded as an activity entry in the affected task’s activity feed, so you can trace exactly what changed and when.