feat: add HubSpot component

[AmeliaCelline]

Because

• Add HubSpot component for user story

This commit

• Created various tasks for HubSpot component which are:

1. Get Contact
2. Create Contact
3. Get Deal
4. Create Deal
5. Get Thread
6. Retrieve association

For more information about the task and using it in local VDP environment:
https://docs.google.com/document/d/1dP4cDxdPQfGu48oY5fFq9AlirP-osdRVJmulZ_1Ib1M/edit?usp=sharing

TODO:

• Create testing for the six tasks mentioned above
• Ticket task (Get Ticket, Create Ticket)
• Company task (Get Company, Create Company)
• Create testing for ticket and company tasks

After PR

• Insert message task
• Rewrite the code structure

[donch1989]

Hi @AmeliaCelline
Is this PR ready? I noticed the checklist items are not checked, so I'm unsure if it's complete.

[AmeliaCelline]

Hi @AmeliaCelline Is this PR ready? I noticed the checklist items are not checked, so I'm unsure if it's complete.

Hi, I decided to add more tasks, so for now, consider it incomplete

[donch1989]

Hi @AmeliaCelline Is this PR ready? I noticed the checklist items are not checked, so I'm unsure if it's complete.

Hi, I decided to add more tasks, so for now, consider it incomplete

Sure, then let's mark it as draft PR. Thanks

[chuang8511]

Hi @AmeliaCelline cc @donch1989
It is good you make a document to help me quickly understand HubSpot!
And, in tasks.json, I can see that you think clearly about the product design.

I left product opinions in json schema & coding opinions in the go files.
Today, I do not have enough time (& energy) to check clearly about your implementation.

After you check the opinions and modify the code, in the next stage, I will review the following sections.

1. If the coding styles follows what I mentioned?
2. If test code is well-structured?
3. If the user story can be done under the current product design?

In the implementation part, I think I won't check it too details if the 3 things we checked.
For the implementation part, I will quickly go through it in the next review.

p.s.
Some of the comments are opinions not decisions.
I believe you are already the profession in this domain because you research it longer than us.
So, I'd follow your decision if you have a clear & convincible reasons for each comment.

[chuang8511]

question
Do we need TASK_UPDATE_DEAL for this story?

[chuang8511]

Question
It seems the design here is like

1. Get Contact
2. If there is no Contact, Create Contact (with company info)
3. Get Company
4. If there is no Company, Create Company
5. Get Deal
6. If there is no Deal, Create Deal
7. Get Ticket
8. If there is no Ticket, Create Ticket
9. Get Thread
10. If there is update from the conversation, Insert Message.

So, now, Does it seem we miss insert Message to Thread?

[chuang8511]

Question

As a sales manager, he/she wants to supervise the status of each client.

If you fake the sales tool component first, is your design able to fulfil this story request?

If my understanding is correct, we may miss company-id in Contact object

[AmeliaCelline]

question
Do we need TASK_UPDATE_DEAL for this story?

Question
It seems the design here is like

I will answer these questions together.

1. First regarding the design. Initially when I was designing the component, I was thinking, how does HubSpot component fit together with the other already-made components and future possible components. For the "create" tasks, such as "create deal" and "create contact", I thought users will benefit from this when "Run on Event" pipeline is ready. Example: A WhatsApp message from a new client -> Create a new contact in HubSpot. For the "get" tasks, it is mainly for summarization purpose. With an email of the client, all the information about the client is obtainable (using the retrieve association task), then afterward can use LLM to summarize all those information.

2. Second, regarding the TASK_UPDATE_DEAL. I thought update was not needed because I don't see the use case of it. I don't see how the output of text summarization will lead to the need of update.

So, now, Does it seem we miss insert Message to Thread?

Yes, I was debating on this as well. I think I will create it after all.

If you fake the sales tool component first, is your design able to fulfil this story request?
If my understanding is correct, we may miss company-id in Contact object

Yes, I think you are right after all. I will provide options for the user to be able to create contact -> object association (including company).

I am not sure what you mean by fake the sales tool, feel free to elaborate it thanks.

[chuang8511]

@AmeliaCelline

Second, regarding the TASK_UPDATE_DEAL. I thought update was not needed because I don't see the use case of it. I don't see how the output of text summarization will lead to the need of update.

Maybe I missed some points. But, as I known, deal means the case that a sales is processing.
So, it means when a sales have a update with their clients in WhatsApp, the deal will be updated according to their message.

e.g. when a client said "I have sent the contract back to you", it means the deal should be updated as "contracting status".

Is this correct under this domain or industry?

I am not sure what you mean by fake the sales tool, feel free to elaborate it thanks.

Because we do not have any Sales tool component like WhatsApp, the story must not be done by this PR.
So, fake it means "we assume we have WhatsApp, after we add HubSpot, could we fulfil this story?"

[AmeliaCelline]

Maybe I missed some points. But, as I known, deal means the case that a sales is processing.
So, it means when a sales have a update with their clients in WhatsApp, the deal will be updated according to their message.

Yes, I think you are right. The update task does have its use case once more sales tool component is integrated. I think I can make "Update Ticket task" and "Update Deal task" as soon as I am done with WhatsApp "send message task". I believe once these 2 additional tasks are completed, the HubSpot design should be able to fulfill the story.

Note: Just wanted to let you know that unfortunately, the WhatsApp component will not have "receive message" task, as it can only be implemented through webhook.

[AmeliaCelline]

@chuang8511 Maybe it is better if I create a new PR specifically for those 2 update tasks? I think this PR is getting too big

[chuang8511]

Want to make sure if we lack these 2 tasks, can you build a demo pipeline like I mentioned in Slack?
If yes, I think you can do it in another PR.
If no, I think you need to do it with this PR.

[chuang8511]

the WhatsApp component will not have "receive message" task, as it can only be implemented through webhook.

Does it mean there is no API to fetch users' message in a Chatroom?

[AmeliaCelline]

Want to make sure if we lack these 2 tasks, can you build a demo pipeline like I mentioned in Slack?
If yes, I think you can do it in another PR.
If no, I think you need to do it with this PR.

Yes, I believe I can build a demo pipeline without those two tasks.

Does it mean there is no API to fetch users' message in a Chatroom?

From my understanding so far, the official WhatsApp Business Platform API cannot retrieve user messages in a chatroom. The only way to get the content of the message is when we receive the message notification sent to the webhook endpoint that we set up.

[chuang8511]

Hi @AmeliaCelline
I left some comments. Please take a look.
If time is not enough, those are not blockers.
We can improve them in the next PR.
Others LGTM.

Please make sure you have gone through all use cases with the pipelines!
Thanks for your contribution!!!

[donch1989]

@chuang8511 @AmeliaCelline
I think we can merge this. If any issues arise, we can address them later.