Skip to content
Expedify
Start free
Your First AI Agent
Course contents

Module · Real Channels & AI

Go live — then adapt a real template

Lesson 8 of 8 · 6 min

You can read a workflow now. You can see the trigger that starts it, the nodes that do the work, the references that carry data between them, the branch that splits the path, and the agent that decides. There is one thing left, and it is the smallest and the most consequential: turning it on.

Saved is not running

A workflow you have saved does nothing. It sits as a draft, and drafts do not respond to triggers. This is not a warning about being careful — it is the single most common “why isn't my automation working?”, and the answer is almost always that nobody pressed Activate.

The two states are worth stating plainly, because they are not symmetrical:

Responds to its trigger

Draft
no
Active
yes — every time, without asking

Can you test it

Draft
yes — running it manually works on a draft
Active
yes

Safe to edit

Draft
yes
Active
you are editing something live

What it costs

Draft
nothing
Active
real sends, real writes, real credits

Which gives you the order to work in, and it is the order this whole course was built in: build it, run it manually, read what happened, then activate. Running a draft by hand is a real execution against real data — it is not a simulation — so by the time you activate, the only thing that changes is who decides when it runs.

What changes the moment you activate

  • The trigger starts listening. A Database Change Trigger begins watching the table. A Scheduler joins the clock. A webhook's URL starts accepting posts.
  • It runs on volume you did not choose. A manual test is one record. Activation is every record, including the import somebody runs at 2am.
  • Its side effects become real and repeated. The send node that mailed you once now mails everyone who matches.

Before you activate anything with a Database Change Trigger, ask the lesson 2 question one more time. Does this workflow write back to the table it watches? If it does, fill in Ignored Fields with the columns it writes — or it will trigger itself, forever, at whatever volume your CRM can produce.

Then stop building from scratch

The marketplace ships finished workflows, and every one of them is rated intermediate — there is no beginner template. That was true when this course was designed and it is why the course exists. It is also no longer a problem for you, because “intermediate” only ever meant “assumes you can read a workflow”.

Here is what is waiting, and which lessons you already have for each:

Read from the live marketplace. Every one is a workflow, made of the nodes you have been reading.

Website Chatbot Customer Support Agent

Starts with
User Message Trigger
You learned it in
L2 triggers · L6 the agent

Post Call — Lead Status Update

Starts with
Database Change Trigger
You learned it in
L2 triggers · L3 the CRM write · L4 references

AI-Powered Lead Qualification System

Starts with
Webhook Trigger
You learned it in
L2 triggers · L5 branching

WhatsApp Agent with Knowledge Base & CRM Update

Starts with
an incoming WhatsApp message
You learned it in
L6 the agent · L7 channels

Outgoing Phone Call Customer Support Agent

Starts with
Database Change Trigger
You learned it in
L2 triggers · L6 the agent

How to adapt one without breaking it

Importing a template copies it into your org as a draft you own. It is yours to change, and the temptation is to change everything at once. Do the opposite:

  1. Open it and read it end to end before changing anything. Name the trigger, then each node's one job.
  2. Run it once, unmodified, and read the execution log. Now you know what “working” looks like for this template.
  3. Change exactly one thing — the prompt's wording, the template it sends, the field it writes.
  4. Run it again and compare. If something broke, you know precisely what broke it.
  5. Only then change the next thing.

The first thing to change is almost always the agent's prompt. A template's structure is usually right — it was built by someone who had the problem. What is wrong for you is its tone, its rules and its edge cases, and all three live in the prompt, which lesson 6 taught you to read.

Key takeaways

  1. A saved workflow is a draft, and drafts never fire. Activation is a separate, deliberate act.
  2. Running a draft manually is a real execution — use it to prove the workflow before you activate.
  3. Activation changes who decides when it runs, and multiplies every side effect.
  4. Check Ignored Fields before activating anything that writes to the table it watches.
  5. Import a template, read it, run it unmodified, then change one thing at a time.
  6. The prompt is usually the right first change; the structure usually isn't.

You can read a workflow

That was the whole promise. A workflow is a trigger, some nodes, and the connections between them (L1). The trigger decides when it runs and what data it starts with (L2). Every node is one job, one form (L3). {{ alias.field }} moves data between them (L4). A condition splits the path and only one side runs (L5). An agent decides instead of being told, and is blind unless you give it context (L6). A send reaches a real person and cannot be undone (L7). And nothing happens until you activate it.

Open a template. You will find nothing in it you have not already met — only more of it at once. That is the entire difference between intermediate and beginner, and you are on the other side of it.

Sign in to track progress