Define
Create an automation rule or a multi-stage email sequence for an approved operating objective.
Licensed operations · TaiGong Drill 1.3.4
Automation rules, multi-stage email follow-up, and scheduled jobs are licensed capabilities.
01 / Operating loop
Define · Trigger · Execute · Review
Repeat the process without hiding how it ran.
The automation module records rules and executions so an operator can inspect what was configured, what triggered, and what happened next. It does not replace authorization, provider setup, or human ownership.
Trigger
Use the supported schedule, event condition, or manual trigger available to the licensed workflow.
Execute
Create the governed execution and call the underlying campaign or follow-up capability it depends on.
Advance
Use a licensed stage to send a follow-up email after a supported campaign event.
Review
Inspect execution history and campaign evidence before changing the rule or scheduling another run.
02 / Versioned availability
Core campaign · Licensed automation
What automation includes in 1.3.4.
The base campaign lifecycle remains separate from the automation entitlement. Connected modules retain their own license and provider requirements.
| Operational capability | Status | Delivered boundary |
|---|---|---|
| Email campaign creation, start, pause, resume, results, and evidence | Core | Manual base campaign operations and evidence remain available without the automation feature. |
| Automation rules | Licensed | Create, manage, and evaluate rules through the automation feature group. |
| Manual automation trigger and execution history | Licensed | Run an eligible rule manually and review its recorded executions. |
| Scheduled jobs and rule evaluation | Licensed | Background schedules and periodic rule checks are part of the licensed automation runtime. |
| Multi-stage email follow-up | Licensed | Stage definitions send follow-up email after supported campaign events. |
| Automated awareness-training assignment | Unsupported | Courses and batches are licensed separately, but the 1.3.4 automation action types do not assign training. |
| Automated SMS or enterprise-IM campaign action | Unsupported | The campaign automation action constructs an SMTP email campaign; it does not create SMS or IM campaigns. |
| External HR data | Integration-only | REST integration supplies external data; TaiGong does not include an HR system. |
| Automation webhook action | Integration-only | Posts a governed event payload to an external endpoint from within the licensed automation feature. |
| MCP automation access | Integration-only | The MCP adapter inherits TaiGong authentication and server-side automation entitlements. |
| Autonomous AI campaign agent | Unsupported | No autonomous planner or agent runtime is delivered as TaiGong Drill 1.3.4 automation. |
03 / Practical patterns
Explicit triggers · Inspectable results
Use automation where the rule can be stated clearly.
Good automation starts with a defined audience, event or schedule, action, license boundary, and owner. If those inputs are ambiguous, the workflow should remain manual until they are resolved.
Run periodic checks and jobs without inventing an AI operator.
The worker evaluates supported schedules and automation rules at defined intervals. Execution history gives the operator a record to review.
Send a follow-up email after a supported event.
Stage definitions connect campaign events to later email content. They do not switch the sequence to SMS or enterprise IM.
Send a governed event to an external system.
An automation rule can post an event payload to a configured webhook. The destination remains an external integration, not a TaiGong delivery channel.
Automation does not create SMS, IM, or training actions.
The 1.3.4 campaign action requires a template, landing page, and SMTP profile. SMS, enterprise IM, and awareness training remain separate manual workflows.
04 / Operating controls
License · Scope · Review
Automate a reviewed process, not an undefined one.
Confirm written authorization, feature entitlements, provider configuration, target scope, schedule, stop conditions, and an accountable owner before enabling a rule or stage sequence.
Automation with visible boundaries
Walk through one rule from trigger to evidence.
Bring a recurring process you operate today. We will separate the core campaign steps, automation entitlement, channel dependencies, and review points.