Hey guys, I noticed a pretty big gap in the current HubSpot toolkit in Composio. When I checked the docs https://docs.composio.dev/toolkits/hubspot there are no tools available for working with leads (crm.objects.leads). This is quite surprising because leads are one of the core objects in hs (alongside contacts, companies, deals). Especially when building qualification workflows, it's fundamental to be able to: Read lead data Update lead properties Change lead status Qualify / disqualify leads Right now an agent simply cannot properly run a lead qualification process. What’s the best way to handle this? Is support for crm.objects.leads planned soon? Is there any workaround (custom tools, direct API calls via http toolkit, etc.) that actually works well? Or maybe I’m missing something and the functionality is hidden somewhere? Would love to hear your thoughts or any official info from the Composio team. Thanks!

You’re not missing a hidden Leads section. HubSpot Leads are supported through the generic CRM-object tools rather than lead-specific tool names. Use

objectType: "leads"

with: •

HUBSPOT_SEARCH_CRM_OBJECTS_BY_CRITERIA

or

HUBSPOT_READ_APAGE_OF_OBJECTS_BY_TYPE

to list/search leads •

HUBSPOT_READ_CRM_OBJECT_BY_ID

to read one lead •

HUBSPOT_PARTIALLY_UPDATE_CRM_OBJECT_BY_ID

to update it To change qualification status, first use

HUBSPOT_READ_A_CRM_PROPERTY_BY_NAME

for

hs_lead_label

to get the valid labels in that HubSpot account, then update

hs_lead_label

with the generic update tool. The connection must have [

crm.objects.leads.read

](http://crm.objects.leads.read) and

crm.objects.leads.write

. HubSpot restricts these scopes to Sales Hub Professional or Enterprise, and they are not part of Composio-managed HubSpot’s default scope set. For Leads access, use a custom HubSpot auth config with your own OAuth app, enable those scopes in HubSpot, add them under Optional Scopes, and reconnect. So you do not need the HTTP toolkit for this. We do not have an ETA to share for dedicated lead-named wrappers, but the docs should make the generic Leads path easier to discover. Thanks for flagging that.