Why should you care?

Ops teams want if-new-lead-then-enrich-and-assign without opening Visual Studio for each customer playbook.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Automation/WorkflowDefinition.cs
public sealed record WorkflowDefinition(
    string Id, string Trigger, IReadOnlyList<string> Steps, bool RequiresApproval);

public sealed class AutomationRegistry
{
    readonly Dictionary<string, WorkflowDefinition> _defs = new()
    {
        ["crm.new-lead"] = new("crm.new-lead", "crm.lead.created",
            ["EnrichLead", "ScoreLead", "AssignOwner"], false)
    };
    public WorkflowDefinition Get(string id) => _defs[id];
}

What happened?

• AutomationRegistry maps trigger crm.lead.created to ordered agent steps stored as data-driven workflow definitions.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Emit domain events crm.lead.created to Service Bus.
2. AutomationWorker loads WorkflowDefinition and runs steps.
3. Admin UI CRUD on definitions stored in SQL JSON column.
4. Add JSON schema validation on workflow definition uploads.
5. Simulate workflow dry-run without side effects.

Remember

Automation platforms store triggers and agent steps as data. AgentNest registry drives workers from domain events. Expose admin configuration for tenant playbooks.

Custom lead routing

Enterprise CRM customer adds ScoreLead threshold in admin UI.

Outcome: Updated WorkflowDefinition routes hot leads without code deploy.