Workflows

Execute business and data workflows. Use this tool to trigger complex backend processes like lead research, campaign building, content generation, sending emails/whatsapp, etc.

Input Schema

Parameter	Type	Description
action	string	The workflow action to execute. Enum: idealClientProfileMining, buildCampaigns, buildContent, buildSegments, buildSegmentsICP, leadFollowUp, leadResearch, enrichLead, leadGeneration, analyzeSite, assignLeads, leadInvalidation, dailyProspection, leadQualification, dailyStrategicAccounts, sendEmailFromAgent, sendWhatsappFromAgent, scheduleCustomerSupport, answerWhatsappMessage, dailyStandUp, customerSupportMessage, agentMessage, startRobot, promptRobot, stopRobot
payload	object	The parameters for the workflow. Must include site_id (automatically injected if not provided) and other specific fields depending on the action.

REST Endpoint

Each workflow action maps to its own route under /api/workflow/{action}.


POST /api/workflow/leadResearch
POST /api/workflow/enrichLead
POST /api/workflow/buildCampaigns
POST /api/workflow/buildContent
POST /api/workflow/buildSegments
POST /api/workflow/buildSegmentsICP
POST /api/workflow/idealClientProfileMining
POST /api/workflow/leadFollowUp
POST /api/workflow/leadGeneration
POST /api/workflow/analyzeSite
POST /api/workflow/assignLeads
POST /api/workflow/leadInvalidation
POST /api/workflow/leadQualification
POST /api/workflow/dailyStandUp
POST /api/workflow/sendEmailFromAgent
POST /api/workflow/sendWhatsappFromAgent
POST /api/workflow/startRobot
POST /api/workflow/promptRobot
POST /api/workflow/stopRobot
POST /api/workflow/agentMessage
POST /api/workflow/customerSupportMessage

The site_id field is required in the request body for all workflow routes.


POST /api/workflow/enrichLead
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
 
{
  "site_id": "YOUR_SITE_ID",
  "lead_id": "LEAD_UUID"
}

Response:


{
  "success": true,
  "result": { ... }
}