SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Resolving HubSpot Destination 429 Rate Limit Errors in Segment

Issue

You are getting a 429 error (Too Many Requests) while syncing with HubSpot and want to find a way to batch your requests to prevent failed deliveries. This article explains how to manage HubSpot rate limits and throttle your data flow, since Segment's HubSpot Cloud-Mode (Actions) destination sends each event as an individual API call.

 

Product

Twilio Segment

 

Environment

Segment Console

 

Resolution

  1. Review the HubSpot API rate limits documentation to understand the maximum volume of data your specific HubSpot account tier can receive.
  2. Verify the frequency and volume of data being sent from your upstream source. Because the HubSpot (Actions) destination does not currently support built-in batching of requests, every record is sent as an individual API call.
  3. Implement custom throttling or batching logic directly within your source or upstream process. You must slow down the rate at which events are sent to Segment to stay within HubSpot's allowed limits.
  4. Monitor your destination's Event Delivery page in the Segment Console. Segment will automatically retry failed deliveries caused by rate limits, but if your volume is consistently too high, you will continue to see 429 errors until the source volume is reduced.
Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk