proactive-orchestrator

name	Proactive Orchestrator
description	Event-driven orchestrator that chains existing skills, edge functions, and agent capabilities into automated workflows triggered by real-time events. Receives events from webhooks (MeetingBaaS, email, calendar), cron jobs (morning brief, pipeline scan), and Slack interactions (button clicks, approvals), then executes multi-step sequences with context-aware routing, HITL approval gates, and self-invocation for long-running chains. This is the conductor — it connects 30+ existing Slack functions, 6 specialist agents, and the sequence executor into coherent, event-driven sales workflows. NOT triggered by user chat messages. Triggered by system events only.
metadata	{"author":"sixty-ai","version":"1","category":"agent-sequence","skill_type":"sequence","is_active":true,"context_profile":"orchestration","agent_affinity":["pipeline","outreach","meetings","crm_ops","research","prospecting"],"triggers":[{"pattern":"meeting_ended","intent":"post_meeting_workflow","confidence":0.95,"examples":["meetingbaas webhook received","transcript ready for processing","recording complete"]},{"pattern":"pre_meeting_90min","intent":"meeting_prep_workflow","confidence":0.95,"examples":["upcoming meeting in 90 minutes","meeting prep trigger","calendar event approaching"]},{"pattern":"email_received","intent":"email_triage_workflow","confidence":0.9,"examples":["new email from prospect","email webhook fired","inbound email detected"]},{"pattern":"proposal_generation","intent":"proposal_pipeline_workflow","confidence":0.9,"examples":["generate proposal for deal","proposal requested by rep","intent detected: send proposal"]},{"pattern":"calendar_find_times","intent":"scheduling_workflow","confidence":0.9,"examples":["find available meeting times","scheduling request detected","calendar availability needed"]},{"pattern":"stale_deal_revival","intent":"deal_revival_workflow","confidence":0.85,"examples":["stale deal detected in pipeline scan","deal inactive for 14+ days","pipeline scan flagged deal"]},{"pattern":"campaign_check","intent":"campaign_monitoring_workflow","confidence":0.85,"examples":["daily campaign check","instantly campaign metrics","outreach performance review"]},{"pattern":"coaching_digest","intent":"coaching_workflow","confidence":0.85,"examples":["weekly coaching analysis","meeting pattern review","rep performance digest"]},{"pattern":"morning_brief","intent":"morning_briefing_workflow","confidence":0.95,"examples":["daily morning briefing","8am daily digest","start of day summary"]},{"pattern":"slack_approval_received","intent":"resume_paused_sequence","confidence":0.95,"examples":["rep clicked approve button","HITL approval received","slack action: approve"]}],"keywords":["orchestrator","event-driven","workflow","chain","sequence","proactive","automation","webhook","post-meeting","pipeline","approval"],"required_context":["org_id","user_id"],"inputs":[{"name":"event_type","type":"string","description":"The event that triggered this orchestration (meeting_ended, email_received, etc.)","required":true},{"name":"event_source","type":"string","description":"Origin of the event (webhook:meetingbaas, cron:morning, slack:button_approve, orchestrator:chain)","required":true},{"name":"payload","type":"object","description":"Event-specific data (meeting_id, email_id, contact_id, deal_id, etc.)","required":true},{"name":"parent_job_id","type":"string","description":"If this event was chained from another sequence, the parent sequence_jobs.id","required":false},{"name":"resume_step","type":"number","description":"If resuming a paused sequence (after HITL approval), the step index to resume from","required":false}],"outputs":[{"name":"sequence_job_id","type":"string","description":"The sequence_jobs.id for tracking this orchestration run"},{"name":"steps_completed","type":"array","description":"List of skill/action names that completed successfully"},{"name":"outputs","type":"object","description":"Accumulated outputs from each step, keyed by step name"},{"name":"pending_approvals","type":"array","description":"Actions waiting for HITL approval via Slack"},{"name":"queued_followups","type":"array","description":"Follow-up events queued for future execution"},{"name":"errors","type":"array","description":"Any errors encountered during execution"}],"requires_capabilities":["meetings","crm","email","messaging","calendar","enrichment"],"priority":"critical","linked_skills":["detect-intents","find-available-slots","email-send-as-rep","monitor-campaigns","coaching-analysis","meeting-digest-truth-extractor","post-meeting-followup-drafter","sales-sequence","proposal","lead-research","daily-brief-planner","deal-slippage-diagnosis"],"tags":["agent-sequence","orchestrator","proactive","event-driven","automation","pipeline","meetings","critical-path"]}

Available Context & Tools

@_platform-references/org-variables.md @_platform-references/capabilities.md @references/event-sequences.md @references/context-tiers.md @references/hitl-patterns.md

Proactive Orchestrator

The single edge function that transforms isolated capabilities into an autonomous sales copilot. Every event flows through this orchestrator — it decides what sequence of existing skills to run, in what order, with what context, and where to pause for human approval.

Design Principle

Extend, don't rebuild. The orchestrator calls existing edge functions and skills. It does NOT duplicate their logic. It is a router, context loader, and sequence runner — nothing more.

• No new queue tables — extends sequence_jobs with 3 columns
• No new preference tables — reads existing slack_user_preferences, notification_feature_settings, slack_user_mappings
• No polling heartbeat — every event has a clear trigger source
• Self-invokes when approaching the 150s edge function timeout

Architecture

EVENT SOURCE                     ORCHESTRATOR                        EXISTING CAPABILITIES
                                 (agent-orchestrator edge fn)

meetingbaas-webhook ────┐        ┌────────────────────┐        ┌──────────────────────────┐
                        │        │                    │        │ extract-action-items      │
proactive-meeting-prep ─┤        │ 1. Receive event   │───────>│ suggest-next-actions      │
                        │        │ 2. Load context    │        │ copywriter skill          │
slack-interactive ──────┤───────>│    (3 tiers)       │        │ generate-proposal         │
                        │        │ 3. Select sequence │        │ proactive-pipeline-anal.  │
email webhook ──────────┤        │ 4. Chain skills    │        │ proactive-meeting-prep    │
                        │        │ 5. Route output    │        │ Slack delivery modules    │
calendar webhook ───────┤        │ 6. Queue followups │        │ CRM update functions      │
                        │        │                    │        │ Apollo / Apify / Instantly│
cron: morning brief ────┘        └────────────────────┘        │ sequence executor         │
                                                               └──────────────────────────┘

How It Works

Step 1: Receive and Validate Event

Every orchestration starts with an OrchestratorEvent:

interface OrchestratorEvent {
  type: string          
  :         
  : 
  : 
  : <, >
  ?:   
}