Automations

Automations run actions for you when something happens in your Space — no manual follow-up required. Each automation is a simple when this happens, do that rule. Set them up in Space Settings → Automations.

[!NOTE] Automations require a Studio plan. See Billing for plan details.

How a Rule Works

Every automation has three parts:

Trigger — the event that starts the rule.
Conditions (optional) — filters that decide whether the rule should run (e.g., only when the stage changes to “In Review”).
Actions — one or more things Cuevue does in response.

You can enable or disable any rule, and the Activity panel shows a history of recent runs so you can confirm a rule fired as expected.

Triggers

A rule can start from any of these events:

A project’s stage, assignee, priority, or due date changes
A project is created or archived
A comment is added
A version is created
A review link is created
a tag is added or removed
a member is added to the Space

Actions

In response, a rule can:

Change a project: set stage, priority, due date, assignees, or tags; archive it
Create things: post a comment, create a review link, or create subtasks from a preset
Notify people: notify a user in-app or send an email
Reach other tools: post to Slack or call a webhook

[!TIP] Start from a recipe — Cuevue includes ready-made rule templates for common workflows so you can adjust one instead of building from scratch.

Slack & Webhooks

The post to Slack and webhook actions let automations reach outside Cuevue. Add the Slack incoming-webhook URL (or your endpoint URL) in the automation’s Secrets manager so the credential is stored securely rather than in the rule itself.

Examples

When a project moves to “In Review,” notify the producer and create a review link.
When a comment is added to a published version, post a message to your team’s Slack channel.
When a project is created, set a default due date and assign your editor.