Skip to content

hubspot — Migrate Contact Lists v1 API to v3 before April 30, 2026 deprecation #20175

@s0s0physm

Description

@s0s0physm

Summary

HubSpot is deprecating the Contacts Lists v1 API on April 30, 2026. Three methods in hubspot.app.mjs, the lists prop definition, and three components use the deprecated endpoints and must be migrated to the Lists v3 API.

Impacted

common/constants.mjs

  • API_PATH.CONTACTS = "/contacts/v1" — base path constant used by impacted methods; needs a dedicated LISTS v3 path constant

hubspot.app.mjs

Method Current (v1 — deprecated) Migration Target (v3)
getLists() GET /contacts/v1/lists POST /crm/v3/lists/search
getListContacts() GET /contacts/v1/lists/{listId}/contacts/all GET /crm/v3/lists/{listId}/memberships
addContactsToList() POST /contacts/v1/lists/{listId}/add PUT /crm/v3/lists/{listId}/memberships/add
lists prop definition calls getLists() update after getLists() migration

Actions

  • actions/add-contact-to-list/ — calls addContactsToList(), fully impacted
  • actions/create-email/ — uses lists prop definition for includeContactLists and excludeContactLists; both dropdowns will break

Sources

  • sources/new-or-updated-contact/ — uses lists prop definition for list filtering; underlying membership checks already use v3

Not Impacted

  • sources/new-contact-added-to-list/ — already on v3 Lists API

Notes

  • v3 contact IDs use recordId instead of v1's vid
  • translateLegacyListId() (GET /crm/v3/lists/idmapping) is already in hubspot.app.mjs and can map legacy v1 list IDs to v3 IDs if needed

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    deprecatedAPI has been deprecatedtriagedFor maintainers: This issue has been triaged by a Pipedream employee

    Type

    Projects

    Status

    Prioritized

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions