search

appsmithorg / appsmith

Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
https://www.appsmith.com
Apache License 2.0
34.57k stars 3.73k forks source link

[Feature] HubSpot Files API Saas Integration #11983

Open felixsuarez0727 opened 2 years ago

felixsuarez0727 commented 2 years ago

HubSpot Files API Saas Integration

Description:

Files hosted with the files tool can be uploaded and used in your HubSpot and external content, as well as attached to records using the engagements API. For example, if your company is building their website using HubSpot CMS, you can use the files API to upload and store assets in HubSpot, then serve it through the HubSpot CMS. (Each will be an action).

Documentation:

https://developers.hubspot.com/docs/api/files/files

API Actions Progress

Action EngSpec Doc SaaS Manager App SaaS App Run Test App Run QA
Upload File No No No No No
Import File Yes Yes Yes Yes No
Delete File Yes Yes Yes Yes No
Get File Yes Yes Yes Yes No
Create Folder Yes Yes Yes Yes No
Search File Yes Yes Yes Yes No

Notes

github-actions[bot] commented 2 years ago

We have found issues that are potential duplicates:

github-actions[bot] commented 2 years ago

We have found issues that are potential duplicates:

btsgh commented 2 years ago

Testcases are available here:

  1. Basic Test Cases
  2. Import File
  3. Delete File
  4. Get File
  5. Create Folder
  6. Search File
btsgh commented 2 years ago

Issues found so far while testing:

  1. When we run the IMPORT_FILE_TEST api in the Files HubSpot Test datasource, created by Felix, the import seems to run fine, but the output seen on the response tab is - "{ ""id"": ""AAAAEZ6whGI"", ""links"": { ""status"": ""https://api-na1.hubspot.com/files/v3/files/import-from-url/async/tasks/AAAAEZ6whGI/status"" } }" When we go the above status URL, it gives the following message : {"status":"error","message":"Csrf token is missing from the request.","correlationId":"66edde4a-4228-4165-9c06-d30f50e3a443","engagement":{"hapikey":"Not engaged, auth is missing","oauth-token":"Not engaged, auth is missing","service-to-service":"service-to-service not engaged. Metadata for service-to-service request not found.","internal-cookie":"internal-cookie not engaged. Cookie not found in the request.","app-cookie":"Engaged"}}

  2. In case of Import File, the fields (especially the mandatory ones) are not self-explanatory and its tough for the user to understand what to enter in the fields.

  3. Import fails in this scenario - https://www.loom.com/share/992d9c726aa8423abc3cf06484b6560e

  4. Delete file gives an error on RUN. However, it looks like the file does get deleted, though the error is shown. In Delete file, What is the object ID? Is this same as the ID that we get in Search files?DeleteFile_Fails.png

  5. How to search for all folders? (E.g. I create a folder, there seems to be no way to find if the folder has got created?)

  6. API Return Codes and Number of Records data are not present. And sometimes we don't see the Connect widget options either. ResponseCode_NotPresent.png

  7. Upload debug does not work incase of import UploadDebug_Import.png

felixsuarez0727 commented 2 years ago

HubSpot CMS Files Observations

# Question/Observation Related Issue Resolved
1 When we run the IMPORT_FILE_TEST the output seen on the response tab - Yes
2 Import File, the fields are not self-explanatory #14296 Yes
3 Import fails - Yes
4 Delete file gives an error #14108 Yes
5 In delete file, What is the object ID? - Yes
6 How to search for all folders? - No
7 API Return Codes and Number of Records data are not present - No
8 Upload debug does not work incase of import - Yes

Updates about observations

  1. This status is not a link to take you to the file is only to check the status of the task, to use the link you need oAuth2, and currently we do not support this type of authentication. But this URL does not affect uploading the file. It is successfully added.
  2. The tooltips and subtext will be added, so this problem will be resolved with this.
  3. We need to understand more the problem.
  4. When the action runs the field is removed, the problem is the way to represent the response that shows {}, it is a general problem, not of this integration, we are working on it. (Resolved)
  5. I am investigating a new change in this field.
  6. These had not been included in the initial proposal, Hubspot is constantly updating, as they are migrating from v2 to v3. So in the future, we can create these new actions.
  7. We need to understand more the problem.
  8. Yatin said: Debugging is difficult as response code is missing. Response body Json is difficult to view.
prapullac commented 2 years ago

@felixsuarez0727 : Can you please close the issue and then add QA tag for the same