Review a contact and move its lead status only after the evidence and owner approval are present. The team reads one bounded scope, shows the exact change, executes it once after approval, and returns provider evidence.
Designed for
Revenue operations teams maintaining lead ownership and status
Operating goal
A grounded contact decision and one approved lead-status update
2 steps from trigger to verified handoff, with success and failure paths.
1 MCP layer and 2 connected tools with explicit auth and risk levels.
3 guardrails, 2 evals, and 1 harnesses before production use.
Reads the bounded HubSpot scope and prepares the smallest useful action.
Balanced reasoning model
Executes one native HubSpot operation after human review.
Structured output model
Loads the workflow goal, allowed actions, escalation policy, and output contract before the agent plans work.
A workflow skill that captures the operating contract, tool boundaries, and escalation rules for HubSpot Lead Routing Team.
Centralizes high-risk action checks for writes, secrets, customer data, billing, deploys, and public communications.
Exposes task resources, prompt templates, connector tools, and audit records behind a permission-aware boundary.
Read one contact with a fixed property allowlist.
Set one contact to an explicit HubSpot lead status.
Open it in Codelit, refine it with the agent chat, then generate the architecture or product plan from the same workflow spec.
Open in Agent WorkflowReview a lead and create one approved follow-up task without broad SOQL or field access. The team reads one bounded scope, shows the exact change, executes it once after approval, and returns provider evidence.
A support workflow that reads product docs, checks account and billing state, drafts empathetic replies, and escalates sensitive requests with source-linked evidence.
A meta-agent workflow that generates red-team cases, runs regression suites, scores agent behavior, and blocks production rollout when a workflow violates its safety contract.