Fix HubSpot Secondly Limit Errors in Zapier

When you connect HubSpot to Zapier, you may sometimes see a “You have reached your secondly limit” error. This message comes from HubSpot and signals that your workflows are trying to use the HubSpot API faster than your account allows. In this guide, you will learn what this error means and how to adjust your Zapier workflows so they stay within HubSpot limits.

This how-to article is based strictly on the official HubSpot error documentation and explains step-by-step how to resolve the issue without changing any platform behavior.

What the HubSpot secondly limit error means in Zapier

HubSpot applies rate limits to control how many API requests can be made in a short period of time. When your Zapier workflows send too many requests in a single second, HubSpot returns the error saying that you have reached your secondly limit.

This limit is enforced on HubSpot’s side, not on Zapier’s side. Zapier simply shows the error it receives from HubSpot so you can understand why some tasks did not run successfully.

Why you see the HubSpot rate limit in Zapier

Several situations can cause the secondly limit error to appear in Zapier:

• Multiple Zaps using the same HubSpot account running at the same time.
• Workflows that perform many actions in HubSpot in quick succession.
• Bulk imports or large batches of updates triggered through Zapier.
• Other tools or custom integrations using the same HubSpot account alongside Zapier.

Because all these sources share the same API quota, Zapier tasks may fail temporarily when HubSpot stops accepting new requests for that brief period.

How HubSpot rate limits affect Zapier tasks

HubSpot’s secondly limit is strict: once your account hits it, HubSpot blocks additional requests until the limit window resets. When this happens, any Zapier task that tries to access HubSpot during that time returns the error.

Typical effects you may notice include:

• Individual Zap runs that show a temporary HubSpot error.
• Batches of tasks that fail around the same time with the same message.
• Delays in data syncing between HubSpot and other apps connected through Zapier.

Because the limit is temporary, many tasks will succeed when retried later, once HubSpot allows new requests again.

Step-by-step: Fix the HubSpot secondly limit error in Zapier

Use the steps below to reduce how often this HubSpot error appears inside Zapier and to keep your automations running smoothly.

Step 1: Confirm the error details in Zapier

1. Open your Zap in the Zapier editor.
2. Go to the Run or Zap history section for the affected Zap.
3. Locate a task that shows an error related to HubSpot.
4. Open the detailed error message and confirm that it states you have reached your secondly limit.

This confirms that the issue is not with your Zap configuration but with HubSpot’s rate limiting.

Step 2: Check all Zaps using the same HubSpot account

Because HubSpot limits apply to the entire account, not just to a single integration, you should review every Zap that uses the same HubSpot connection.

1. In your Zapier dashboard, filter Zaps by the HubSpot app.
2. List all active Zaps that use HubSpot triggers or actions.
3. Note which ones run most frequently or process large volumes of data.

High-frequency or bulk-processing Zaps are usually the main contributors to hitting the HubSpot secondly limit.

Step 3: Reduce how often your Zapier workflows call HubSpot

The most effective way to avoid the secondly limit error is to reduce how many API requests your Zaps send to HubSpot per second. You can do this in several ways:

• Spread out triggers: Avoid scheduling multiple Zaps to trigger at the same time if they each write to HubSpot.
• Reduce batch sizes: Where possible, limit the number of records processed in a short period.
• Combine actions: If your workflow uses several HubSpot actions in a row, see whether some data can be updated in one step instead of many.
• Limit nonessential updates: Remove or simplify actions that are not critical to your process.

These adjustments lower the chance that HubSpot will reject requests coming from Zapier in any given second.

Step 4: Stagger or delay Zapier runs that hit HubSpot

If you have multiple Zaps that must all run, try scheduling them so that they do not all send HubSpot requests at the same time.

Approaches include:

• Using different trigger times or schedules for similar workflows.
• Adding filter or path logic so only necessary tasks reach HubSpot.
• Introducing intentional delays between actions that send data to HubSpot.

By staggering runs, your account uses the HubSpot API more evenly instead of in short, intense bursts that trigger the secondly limit.

Step 5: Coordinate other HubSpot integrations with Zapier

Your HubSpot account might also be connected to other apps or custom integrations outside of Zapier. These tools also consume the same API pool and can contribute to the secondly limit.

1. Review all tools connected to your HubSpot account.
2. Identify any that perform heavy or frequent API operations.
3. Try to spread out large jobs or imports so they do not run at the same time as busy Zaps.

This coordination helps ensure that Zapier and your other tools are not all hitting HubSpot at once.

What to do when the HubSpot limit persists in Zapier

If you still encounter the secondly limit error after reducing and staggering your requests, you have a few remaining options.

Monitor Zapier task history for patterns

Use the Zapier task history to track:

• What time of day the error is most common.
• Which specific Zaps produce the largest number of HubSpot tasks.
• How many tasks retry successfully after a delay.

Recognizing patterns can guide you toward additional adjustments, such as shifting high-volume Zaps to quieter times.

Review HubSpot documentation and plan limits

Since the error is enforced by HubSpot, you should review HubSpot’s own documentation for exact limit values and how they apply to your plan. Official guidance is available in the article you originally saw in Zapier: HubSpot error: You have reached your secondly limit.

If your workflows legitimately require higher throughput, you may need to consider whether a different HubSpot plan or configuration is appropriate.

Contact support if needed

If the error continues despite carefully reducing usage, contact the appropriate support team:

• HubSpot support: For questions about your API quota, current usage, and whether your account is hitting other limits.
• Zapier support: For help reviewing your Zap setup, triggers, and actions for potential optimizations.

Provide examples from your Zapier task history along with timestamps so support teams can better analyze what is happening.

Best practices for stable HubSpot workflows in Zapier

To keep your HubSpot integrations stable over time, follow these ongoing practices:

• Regularly review high-volume Zaps for unnecessary actions.
• Use filters and conditions to prevent unneeded HubSpot updates.
• Monitor task history for recurring rate limit errors.
• Coordinate schedules between Zapier workflows and other tools using HubSpot.

These habits will help you avoid hitting the secondly limit and keep your automations reliable.

Additional resources for optimizing workflows

To further optimize your automation strategy beyond the specific HubSpot secondly limit issue, you can find broader automation and integration guidance at specialized resources such as Consultevo. While not affiliated with Zapier or HubSpot, consulting material like this can help you design workflows that naturally minimize rate limit risks.

By understanding how HubSpot enforces API limits and carefully shaping your Zapier workflows around them, you can keep your data flowing smoothly between apps while avoiding repeated “You have reached your secondly limit” errors.

Need Help With Zapier?

Work with ConsultEvo — a

Zapier Certified Solution Partner

helping teams build reliable, scalable automations that actually move the business forward.

Get Zapier Help