I want to say as an engineer that cold calls aren't effective but I feel like it's just due to the numbers of how many calls you can make per hour.
If you can increase the number of dials like in this post it really makes more sense from a time perspective. We also know that regulations on phone calls are going nowhere anytime soon lol.
The previous limit on this endpoint was 500 associations per request and now it's 100. Essentially reducing throughput by 5x and they call it a "bug fix"
Honestly as bad as SFDC can be at least they don't continue to hurt developer experience and call it a bug fix
You preface the title with Tell HN. Helps boost visibility and gets the point across quickly. Else people would have thought your post was a link to an article or something and wouldn't have bothered reading through it.
The biggest thing is I no longer have access to the email address where I wrote the review and I wonder if they recognized that and went and edited it since I wouldn't be checking?
Drones have changed warfare at a local tactical level. But your drones and smaller autonomous systems aren't helping if you have overwhelming firepower superiority, ie in Gaza drones haven't inflicted too much damage if you can just drop a couple thousand JDAMS and level out a territory.
> HubSpot’s developer platform is a core part of our mission to empower organizations to grow better. Our APIs are designed to enable teams of any shape or size to build robust integrations that help them customize and get the most value out of HubSpot. All HubSpot APIs are built using REST conventions and designed to have a predictable URL structure. They use many standard HTTP features, including methods (POST, GET, PUT, DELETE) and error response codes. All HubSpot API calls are made under https://api.hubapi.com and all responses return standard JSON.
I'm getting a bit more estate transfer implications in their old docs but barely
> The API is built to allow you to create a functional application or integration quickly and easily. We know from experience - these are the APIs that power the HubSpot application. The ecosystem of developers creating integrations on top of the APIs is strong and diverse, ranging from webinar providers to CRMs to social media.
Not really sure where they mention it as a state transfer service. Not to mention even if it was, their lack of support for over 50% of their workflow/sequence/queue automations products make state transfer impossible anyways even for internal teams.
But seriously, I was hoping I could come work with you. I'm impressed by your developer prowess. I give you a short, somewhat vague explanation of how to deal with some of the issues you faced and within minutes you have it addressed and returned to joke around with me.
Most developers I know would spin their wheels for weeks with such little information, and once they finally get the job done they wouldn't have time to joke around because they'd be so far behind in everything else they need to get done.
definitely. There's still just such a huge bottleneck when we have 20+ users having to queue up, and they end up complaining that they don't want to wait so long for data to come back from hubspot
We tried a mix of caching as well as hubspot webhooks, but we were still having issues with data not updating fast enough and most of the data we load has to be somewhat on demand regarding tasks/sequences and outbounding features. ie you call or email someone, a task gets moved to the next task and the user wants to see that change somewhat quickly.
Fair enough and I get it, I've been there. But for a 17 year old company worth ~30 billion to have this many issues compared to both newer startups(Salesloft/Outreach) and large incumbents(Salesforce) is just unacceptable.
I'm not here saying every company is perfect, I have quite a few gripes with other services but they either:
A. Actually respond to issues and work with developers and actively help maintain their app integrations despite significantly smaller support teams(I've worked with at most 1-2 csms and an engineer or pm with most integrations but with hubspot I get routed from our app manager, to a csm to an entire engineering team and even the head of support all to just get an email that their oauth issues won't be fixed until q3 202x since developer experience isn't a priority)
or
B. Blatantly don't care but don't sell themselves to sales team that they have a great integration and great support for people building integrations. I'm at a point where I'm trying to actively push our mutual customers to anything but hubspot
I appreciate your sharing of yoir experience with the Hubspot API. I wasn't aware of how bad it is, and I'll keep it in mind.
Responding to the way that Hubspot handled your concerns: competitors Pardot and Marketo are not any better. I don't remember them ever correcting bugs that I reported. And simply getting through the gauntlet of "this isn't a bug, its a feature" Level 1 support is exhausting. Eloqua was much better - but only because I was working at a "partner consultant" org at the time and concerns/bug reports were fast-tracked to senior support techs.
Generally, Salesforce is what I consider "perfect software" (Joel's "good software takes 10 years" concept). It beats all the startups on so many fronts...
hey @thexumaker, I'm a new PM at HubSpot working on our APIs and some of the issues you've brought up are just what I'm looking to improve. Sorry to hear you haven't had a great experience with the APIs or getting contact with HubSpot PMs. I have my email on my profile, would love to get some more detail on your feedback --please feel free to reach out!
If you can increase the number of dials like in this post it really makes more sense from a time perspective. We also know that regulations on phone calls are going nowhere anytime soon lol.