Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hello! I currently have a Zap set up to take Looker data via the Zapier integration, split it into line items (one record per Hubspot company ID), and a loop to update a company property within Hubspot. 

It works but takes up a task for each company, and there are over 5K Hubspot companies to update weekly (over 20k tasks a month).

My question is if I'm even doing this correctly or efficiently? My hope was that Zapier could take the entire Looker payload and process it into Hubspot as one or a handful of tasks.

Thanks in advance!

Hubspot appear to allow batch updates to companies via their API.

I’m not certain about this as it occurred to me, you could use a python code block to post to the API via requests. You would still need to limit the data as you’ll have constraints from Zapier and Hubspot to worry about.

You may get up to 100 company updates every 10 seconds. I’m assuming you could use a wait loop inside the code to slow down the requests, allowing you to double the count each run. You’ll need to watch the script as there are script runtime limits.

I’m assuming this is enough to send around 200 updates you could organise the data or run a series of code blocks or use Looping. It may be possible get all 5000 out in 25 cycles. However, looping has its own limitations.

If it works though you’ll reduce the number of tasks each week.

See Hubspot Docs:
https://developers.hubspot.com/beta-docs/reference/api/crm/objects/companies/v3#patch-%2Fcrm%2Fv3%2Fobjects%2Fcompanies%2F%7Bcompanyid%7D

Reply


Terms & Conditions