222 - Integrate HubSpot API to the request data form for updating contact list

[nozomione]

Issue Number

Closing #222

Purpose/Implementation Notes

• Integrated the HubSpot API to the request data form for updating CCDL-data-requesters contact list in Hubspot:
  • Request Search Data Form via Search (terms with no search results)
  • Request Experiment Data Form via the "Request Experiment" button (experiments with non-downloadable samples)
• Migrated the API version from v1 to v3

Changes includes:

• Added src/data-requests/hubspot
• Added the following env vars to Vercel and next.config:
  • HUBSPOT_ACCESS_TOKEN
  • STAGE_HUBSPOT_ACCESS_TOKEN
• Revised src/data-requests/slack to fix a bug (at c923248b1742c0e111fda9e114185334cbb84150)
• Revised pages/api/data-requests (at d33d11a4e0d8e77ade01c1b6d2e5f5b1b7e9d52c)

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist

• [x] Lint and unit tests pass locally with my changes
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation (if appropriate)
• [ ] Any dependent changes have been merged and published in downstream modules

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
refinebio-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 7, 2024 9:26pm

[nozomione]

🗒️ Currently HubSpot API requests fail due to an unauthorized error 404 with the message This hapikey doesn't exist.

The dev error:

I've tested production and it also fails causing the CCDL-data-requesters contact list to remain unchanged (it seems that the date of the last contact added to the list was 10/14/2021).

The production error:

Based on the error message, this may be resolved by updating our HubSpot API key 💡 Tagging @davidsmejia.

Update Note:

• Due to the Vercel's Node.js v16 deprecation on 9/11/2023, currently we'll hold off updating the secrets/env var values for HubSpot API Key (outdated) in production (uses v16).
• Regarding dev, we'll migrate the HubSpot API version to v3 (see the issue for more details).

[nozomione]

Regarding 434e5e23903e9895012ba55f79a8c53ffb72ef1d, currently via FE, when a user submits a new data request using the same email address to submit the previous one, we will concatenate that new data to the existing data of the Dataset Request Details property (set as multi-line text), resulting in a long string.

Instead of string concatenation, alternately we can;

• filter the Dataset Request Details property to view its submission history (property value, source, and date are available) via each user's contact page
• fetch the Dataset Request Details property's submission history via API (e.g., using this endpoint, we can easily gather and analyze user-submitted data to assist them)

Let me know if this concatenation logic can be removed from the script!

The Dataset Request Details property history in a user contact page (it's a test data):

e.g.,) The concatenated property values on each request: