Jump to content
Vodia PBX forum
Suri

Hubspot CRM Intergration

Recommended Posts

Hello,

We wanted to test the CRM integration between Vodia system and Hubspot, we have got the Hubspot API in settings. We are running v62.1.

On this link ( https://doc.vodia.com/actionurl ), where it says serveraddress and username and password, is that supposed to be our hubspot credentials? The help link on CRM integration redirects to the Action url page and I could not find older discussion threads to set up and test Hubspot integration. Do we need something in between the two platforms that takes the events from Vodia and forwards it to the other party? 

If there are any other links to help with this, please let me know. 

Share this post


Link to post
Share on other sites

I have done that. On Hubspot side though, it does not have Vodia listed as integrators. Does this mean we need a thrid party app in between? 

Share this post


Link to post
Share on other sites

No you don't need a third party. The PBX talks directly to the hubspot API. Too bad hubspot did not list us yet - we see them practically every day on the commuter rail LoL. 

Share this post


Link to post
Share on other sites

Okay. Do we need any specific account type to get the integration working like marketing, sales or service? 

Once we have the API keys in the platform, do we setup the individual extension's "Action URL" page to get that particular extension send information to hubspot?

I was reading through this thread to see how the integration was supposed to work in general 

"You enter the CRM URL (version included) in a setting together with the username and password of the account in the CRM where the entries should be made. These settings are extension based so every person who has an account in the CRM will have his/her calls recorded in his/her account on the CRM." Is this valid for hubspot as well? Do we set up the crm url and the account login credentials in Action url page for whatever action we want to create an entry? 

Share this post


Link to post
Share on other sites

As far as I can tell the basic Hubspot account can do the integration. You don't need to use the ActionURL in the PBX - it is all done for you. What it does is after a call look up the phone number, and add a log entry for the contact about the call. If the number does not exist, it creates a new contact and then adds the log (optional). A problem with Hubspot is phone numbers are used just as strings, on other words 212-123-1234 is different that (212) 123 1234 or +12121231234. So if Hubspot users manually enter phone numbers in their own format, they cannot be found through the API. The other thing is that there is a log entry for calls, but there is no way to indicate the direction of the call (which is kinda important IMHO), this is probably because Hubspot assumes only outbound calling. We tried to raise the issue with Hubspot, but we were not able to get an answer.

Share this post


Link to post
Share on other sites

Thank you for the response. It seems to be trying to connect to hubspot and it does receive some content but we do no see any activity on the hubspot side. I had contacted them as well regarding this and they said we would need to talk to the vodia support for this. 

On the hubspot end, I have manually created a contact with the phone number (say 123456789) and validated it using the standard hubspot phone number validation process. 123456789 is one of the numbers assigned to an extension in our vodia domain. When I make a call from that Hubspot contact to my mobile, the call goes through and I can see the call messages in domain log file in our Vodia system. But when I make a call to or from the same extension, from or to my mobile, the log entries look like this (I was only logging webserver and webclient events at this time). It has the cdr report for the call which looks like it is being forwarded to hubpsot. But, there is no activity on hubpost end, there is no contact added or log entry added for that particular call. 

 

[5] 11:17:28.243 WEBC: Action URL request https://app.hubspot.com/
[7] 11:17:28.244 WEBC: https:app.hubspot.com:443: DNS A returned 104.16.251.5
[7] 11:17:28.244 WEBC: https:app.hubspot.com:443: Connect to 104.16.251.5
[7] 11:17:28.244 SIP: Use codec PCMU/8000 for call-leg 991
[9] 11:17:28.246 WEBC: https:app.hubspot.com:443: Send request (143 bytes)
GET / HTTP/1.1
Host: app.hubspot.com
Authorization: Basic VXNlcm5hbWU6UGFzc3dvcmQ=
Content-Type: application/json
Content-Length: 0

[9] 11:17:28.246 WEBC: Initialize TLS connection
[9] 11:17:28.589 WEBC: Received 765 bytes
HTTP/1.1 301 Moved Permanently
Date: Tue, 05 Mar 2019 00:17:28 GMT
Content-Type: text/html
Content-Length: 178
Connection: keep-alive
Set-Cookie: __cfduid=dbbf19b607034c2df3ffc1407dc4214521551745048; expires=Wed, 04-Mar-20 00:17:28 GMT; path=/; domain=.hubspot.com; HttpOnly
Access-Control-Allow-Credentials: false
Location: https://app.hubspot.com/home
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 4b27e8383f0a1d44-MEL

[9] 11:17:28.589 WEBC: https:app.hubspot.com:443: Return content (178 bytes)
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
[5] 11:17:28.589 WEBC: Action URL response
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
[9] 11:17:31.799 SIP: Using outbound proxy sip:xxx.xxx.xxx.xx:16797;transport=udp because of flow-label
[7] 11:17:31.874 SIP: Port 992: Clear last request
[7] 11:17:34.018 SIP: Port 992: Clear last INVITE
[7] 11:17:34.019 SIP: Use codec PCMU/8000 for call-leg 992
[5] 11:17:34.021 WEBC: Action URL request https://app.hubspot.com/rest/call/
\{"cdr":\{"from:""\"61488888888\" <sip:614888888888@vodia1.domain.com.au>","to":"{tv}","duration":"{duration}"\}\}
[9] 11:17:34.021 WEBC: https:app.hubspot.com:443: Send request (266 bytes)
POST /rest/call/ HTTP/1.1
Host: app.hubspot.com
Authorization: Basic VXNlcm5hbWU6UGFzc3dvcmQ=
Content-Type: application/json
Content-Length: 110

\{"cdr":\{"from:""\"614888888888\" <sip:6148888888888@vodia1.domain.com.au>","to":"{tv}","duration":"{duration}"\}\}
[9] 11:17:34.272 WEBC: Received 752 bytes
HTTP/1.1 500 Internal Server Error
Date: Tue, 05 Mar 2019 00:17:34 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 186
Connection: keep-alive
Set-Cookie: __cfduid=d0152c84ca5b544fdfe51e695e252d6761551745054; expires=Wed, 04-Mar-20 00:17:34 GMT; path=/; domain=.hubspot.com; HttpOnly
Access-Control-Allow-Credentials: false
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 4b27e85ba8231d44-MEL

[9] 11:17:34.272 WEBC: https:app.hubspot.com:443: Return content (186 bytes)
<html>
<head><title>500 Internal Server Error</title></head>
<body bgcolor="white">
<center><h1>500 Internal Server Error</h1></center>
<hr><center>nginx</center>
</body>
</html>
[5] 11:17:34.272 WEBC: Action URL response
<html>
<head><title>500 Internal Server Error</title></head>
<body bgcolor="white">
<center><h1>500 Internal Server Error</h1></center>
<hr><center>nginx</center>
</body>
</html>
[7] 11:17:37.576 SIP: Port 992: Clear last request
[5] 11:17:37.577 SIP: BYE Response: Terminate 73587ecf@pbx
[9] 11:17:39.012 WEBS: Request /rest/domain/vodia1.domain.com.au/log
[9] 11:17:39.012 WEBS: REST: GET /rest/domain/vodia1.domain.com.au/log

Share this post


Link to post
Share on other sites

The HubSpot API integration of Vodia would not go to https://api.hubspot.com it would go to something like https://api.hubapi.com/contacts/v1/contact/ and provide the API key. If you are trying to use this with an ActionURL this will be difficult/impossible because this cannot be done with just a single HTTP request. If you really want to code this yourself, there is a lot of information on HubSpot on how to write the integration, e.g. https://developers.hubspot.com/docs/overview

Share this post


Link to post
Share on other sites

Okay. I have removed all the action urls now so all we have got in the system is the hubspot api key and set it to send information for all calls, just the basic setting.

When I make a call into the domain, there is nothing in the logfile that shows that it is attempting to send information to hubspot. Hubspot has a contact with that phone number which I am calling to. Was there any particular setting that is required on the hubspot end? How do we verify that the integration is working in general? 

Thank you

Share this post


Link to post
Share on other sites

If there was something like this to setup hubspot initially or to reference when we want to see how it is supposed to work, it would be a lot easier. Could we expect a documentation regarding this to be available soon? 

Share this post


Link to post
Share on other sites

Hello,

Still waiting for reply on this, on how to test if the integration is working in general. The logs do not show anything about hubspot even though the correct api key has been used.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...