Why should you care?

Hospital intake and ERP approvals repeat the same gates; automation removes manual copy-paste between systems.

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.Api/Triggers/LeadAutomationWorker.cs
public sealed class LeadAutomationWorker(IServiceScopeFactory scopes) : BackgroundService
{
    protected override async Task ExecuteAsync(CancellationToken stoppingToken)
    {
        await foreach (var leadId in LeadQueue.Reader.ReadAllAsync(stoppingToken))
        {
            using var scope = scopes.CreateScope();
            var agent = scope.ServiceProvider.GetRequiredService<ICrmCopilotAgent>();
            await agent.EnrichAndScoreAsync(leadId, stoppingToken);
        }
    }
}

What happened?

• LeadAutomationWorker drains a channel queue and calls EnrichAndScoreAsync per lead.
• Production swaps LeadQueue for Azure Service Bus.

Practice next

1. Publish lead IDs to Channel or Service Bus on create.
2. Register LeadAutomationWorker as hosted service.
3. Make EnrichAndScoreAsync idempotent with lead version checks.
4. Replace Channel with Azure Service Bus subscription.
5. Add schedule trigger for nightly ERP reconciliation agent.

Remember

Automate AgentNest AI steps with queues and workers. Keep enqueue async; process in background services. Design idempotent agent actions for retries.

Inbound lead pipeline

Marketing floods CRM with webinar leads after an event.

Outcome: LeadAutomationWorker enriches and scores overnight without blocking UI.