Wire your events once, then build unlimited campaigns, and reuse the same events across all of them. The AI orchestrator validates, enriches with live data, and handles the rest.
listLinkRoutes · validateOrchestratorCode viewTaskUrl route also expects opportunityId, I'll add it from the event.saveOrchestratorCode viewTaskUrl with taskId and opportunityId from the event. You can promote the campaign.</> View codeviewTaskUrl.userId, taskId and opportunityId.opportunityId, userId & taskId are presenttask.detail & user.profileSend the events you already emit, even incomplete. The orchestrator handles almost everything: and the few cases it can't are turned into precise dev tasks your favourite LLM picks up and implements, with full context.
signal-task-oncreateDeclareduserIddeclared + seenstringtaskIddeclared + seenstringopportunityIdmissingstringopportunityId to the eventAt send time, the orchestrator calls your systems for exactly what it needs: uses it once, then drops it. No copy of your customer base, ever, and the AI never sees your users' data.
Once the event is wired, every new campaign is built and shipped from the dashboard, no redeploy, no stack to babysit. Engineering stays in control; the team keeps moving.
Nothing is a black box: inspect every execution, and understand what the AI generates before it ships.
Before anything goes live, the orchestrator shows a plain-language summary plus a step-by-step "how it works": event, enrichment, recipients, send. You know exactly what will happen.
</> View codepost_id, url, primary_author.StaffEach channel is validated, with the workflow run, the orchestrator trace, the spam score, the recipients and the step-by-step results: exactly what you review.
› PARAMS {…} · → RESULT {…}Let the AI orchestrate the rest: validation, live data, dev tasks and delivery.