hubspot-crm-card

Get Hubspot Reply Threads

Changed on

Email and form conversations for the record the card is placed on.

HubSpot appends portalId, userId, userEmail, and appId. userEmail stays in the signed query and is used only to verify that signature. It is not parsed as a field, logged, sent to Sentry, or forwarded. The list uses the same thread ids as the reply draft. A thread that was never ingested is included when HubSpot says it is email or a form. A HubSpot chat channel is omitted. When the record has no email thread and Anana wrote it from a phone call or website chat, the list is one follow-up for a guest who has an email.

get/api/v1/public/hubspot/reply-threads

Request

  • Base URL: https://api.getanana.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.getanana.com/api/v1/public/hubspot/reply-threads
  • Auth: none declared

Query parameters

portalIdstring required
objectTypestring required
objectIdstring required
appIdstring nullable

Response

Successful Response

status'ok' | 'portal_not_connected' | 'ambiguous_portal' | 'thread_not_found' | 'not_email_thread' | 'list_incomplete' required
noticestring nullable

Changes