CRM & Marketing connector

    Plan governed AI workflows around HubSpot.

    Coordinate account, lead, and lifecycle work across CRM context, research, outreach, and human ownership. Explore example AgentRuntime patterns for HubSpot, then confirm connector availability and supported actions before production use.

    Catalogued connectorHubSpot

    Coordinate account, lead, and lifecycle work across CRM context, research, outreach, and human ownership.

    Use customer records as durable workflow context while agents and teams research, decide, update, and follow up.

    Example execution path● Planned
    01
    HubSpotProvide a trigger, context, or destination.
    02
    AgentRuntimeCarry durable state through the complete run.
    03
    Agents + rulesReason, validate, branch, and select actions.
    04
    People + systemsApprove, intervene, and complete the process.

    Example architecture only. Exact triggers, actions, scopes, and deployment requirements depend on the connector configuration.

    Start with a workflow outcome, not an isolated tool call.

    These are representative patterns for the CRM & Marketingcategory. They are not claims about currently enabled HubSpot actions.

    01

    Enrich and qualify a record

    Combine CRM data with research, apply qualification rules, and route the next action.

    02

    Run customer lifecycle workflows

    Coordinate onboarding, renewal, expansion, or re-engagement across systems and owners.

    03

    Keep account context current

    Write validated outcomes back to the CRM without hiding decisions in an opaque automation.

    Confirm the boundary before the workflow acts.

    Catalog coverage changes. Validate the actual connector build, authentication method, supported operations, and environment requirements with the AgentRuntime team.

    1. 01Limit workflows to the required objects and fields
    2. 02Define ownership before creating tasks or outreach
    3. 03Prevent duplicate updates and lifecycle actions

    Define the HubSpot workflow boundary.

    Bring the trigger, actions, access constraints, and human decision points. We will map the governed execution path.