Automations Overview

Automations run repetitive work for you. Instead of remembering to ping your team in Slack every time a video goes live, or to email everyone before a shoot, you describe the workflow once and Bluprint runs it automatically.

If you have used Airtable automations or Zapier, this will feel familiar: each automation is a small trigger → conditions → actions recipe. Automations live inside a Bluprint, so they can reach across every Channel in that workspace.

You will find them on the Automations page inside a Bluprint.

Expand

The Three Tabs

The Automations page is split into three tabs:

• Automations — every automation in this Bluprint, with its status and a plain-English summary of what it does.
• Templates — ready-made starter automations you can apply in one click.
• Execution Logs — a history of every time an automation ran, and whether it succeeded.

How an Automation Works

Every automation is built from three parts, shown as connected cards in the builder:

• WHEN (trigger) — the event that starts the automation.
• IF (conditions) — optional checks that must all be true for it to continue.
• DO (actions) — what actually happens.

Expand

Triggers (WHEN)

A trigger answers "what kicks this off?" There are three kinds:

• When an entity changes — an Idea, Calendar Event, Script, or other record is created, updated, or deleted. You pick the entity type and which events to watch.
• On a schedule — either a recurring time, or relative to a date field (for example, 3 days before a Calendar Event's start date).
• Manually — the automation only runs when you click the run button. Handy for one-off batch jobs.

Conditions (IF)

Conditions narrow down when the actions run. They reuse the same field/operator/value rows as the Idea Catalog filter builder, so "Status equals Published" or "Priority is any of High, Critical" work exactly as you'd expect. All conditions must be true. Leave them empty and the automation runs every time it is triggered.

Actions (DO)

Actions are what the automation actually does. You can add more than one, and they run in order:

• Send a Slack message — post to a connected Slack channel.
• Send an email — to your team or a custom list of addresses.
• Create or update a record — for example, set an Idea's priority, or create a Calendar Event.

Message and email fields support tokens like {{ row.title }}, which are filled in from the record that triggered the automation.

Building an Automation

Start from the two buttons in the top-right of the Automations page: New Automation to build by hand, or Create with AI to describe it in words.

Expand

1. Open the builder

   On the Automations page, click New Automation to start from scratch, or Create with AI to describe the workflow in plain English and let the agent assemble it for you.

2. Configure the trigger

   Select the WHEN card and choose what starts the automation. The right-hand panel changes to match the trigger type you pick.

3. Add conditions (optional)

   Select the IF card and add any checks that must pass before the actions run.

4. Add one or more actions

   Click Add action and pick a Slack message, email, or record change. Fill in the details — including any {{ row.field }} tokens.

5. Name it and enable it

   Give the automation a clear name and flip the Enabled switch on. A disabled automation never runs.

Expand

Testing with Run Test

Before relying on an automation, use Run test in the builder to fire it once on demand. For record-based triggers you'll be asked to pick a sample record to run against. The result lands in Execution Logs so you can confirm the actions did what you expected.

Templates

Not sure where to start? The Templates tab has starter automations for the most common workflows. Click Use Template and it opens in the builder, pre-filled and ready to tweak — nothing is saved until you do.

Expand

Execution Logs

The Execution Logs tab is your audit trail. Every run shows its status — Success, Failed, Skipped, Running, or Pending — along with which automation ran and what triggered it. You can filter by status or trigger type and search by name.

Expand

A Skipped run means the automation was triggered but its conditions weren't met — that's normal. Failed runs are clickable: expand one to see exactly which action failed and why, so you can fix it (a disconnected Slack workspace is a common cause).

Required Permissions

Creating, editing, and running automations requires the automations:create_update permission. If the New Automation button or a card's controls are disabled, ask a Team owner to review your role.

Next Steps

Ready for concrete recipes? See Automation Workflows for step-by-step example automations you can copy.