Automation Workflows

This guide is a cookbook of practical automations. Each recipe lists the exact trigger, conditions, and actions to set in the builder, plus why you'd use it. New to the building blocks? Read Automations Overview first.

Every automation here lives on the Automations page inside a Bluprint. Your list ends up reading like a set of plain-English rules:

Expand

1. Celebrate a Published Video in Slack

Purpose: Give the whole team a little dopamine hit — and a heads-up — the moment a video goes live.

1. Trigger — WHEN

   Choose When an entity changes, set the entity to Idea, and check the updated event.

2. Condition — IF

   Add one condition: Status equals Published. This keeps the message from firing on every little edit.

3. Action — DO

   Add a Send a Slack message action, pick your channel (e.g. #content-team), and write the message with a token:

   🚀 {{ row.title }} was just published!
   

The condition is the important part — without it, any update to the Idea would ping Slack.

Expand

2. Email the Team Before Every Shoot

Purpose: Make sure nobody is surprised by a filming or release date. Bluprint emails everyone a few days ahead, automatically.

1. Trigger — WHEN

   Choose On a schedule, then Relative to a date field. Set the entity to Calendar Event, the date field to Start, and 3 days before.

2. Conditions — IF

   Leave this empty so it applies to every upcoming event.

3. Action — DO

   Add a Send an email action addressed To team members. Use tokens in the subject and body:

   Subject: Upcoming: {{ row.title }}
   Body:    "{{ row.title }}" is happening on {{ row.from }}. Time to prepare!
   

3. Auto-Flag Scripted Ideas as Critical

Purpose: Keep your pipeline honest. The moment an Idea is scripted, it should jump up everyone's priority list — no manual bookkeeping.

1. Trigger — WHEN

   When an entity changes → entity Idea → updated.

2. Condition — IF

   Status equals Scripted.

3. Action — DO

   Add a Create / update a record action. Set the operation to Update, entity to Idea, then add the Priority field and set it to Critical. Update actions change the record that triggered the automation.

This pattern — update the triggering record — is how you keep fields in sync without anyone touching them. Swap in any select or text field you like.

Expand

4. Post a One-Off Update On Demand

Purpose: Sometimes you just want a button. A manual automation runs only when you click it — great for ad-hoc "we're going live in 10" pings or batch jobs.

1. Trigger — WHEN

   Choose Manually / button. There's nothing to configure — it never runs on its own.

2. Action — DO

   Add any action, such as a Send a Slack message to #ops.

3. Run it

   From the automation's card (or the builder), use the Run button whenever you need it. The result shows up in Execution Logs.

Tips That Apply to Every Recipe

• Start from a Template. The Templates tab already contains versions of recipes #1 and #2 — apply one and tweak it instead of starting blank.
• Test before you trust. Use Run test and check Execution Logs before enabling an automation for real traffic.
• Watch the right fields. For entity-change triggers, narrowing to the field you care about (like Status) keeps automations from firing on unrelated edits.
• Stack actions. A single automation can, say, update a record and send a Slack message — actions run in order.