Hello All!
We have introduced our brand new HubSpot App to generate sequential numbers - HubSpot Marketplace
The app features:
- Choose a starting number
- Available across all objects including custom objects
- Add prefix and suffix
- Ability to reset numbers per month, per year etc.
- Hands on support team available to answer any questions and provide assistance when you need it most.
We are also proud to provide this app as not only a workflow action, but we can also support accounts who are on lower tiers. If interested in the non-workflow version please email our team at support@hubaptly.com who can walk you through the steps.
Let me know what you guys think!!
Hi @jack2026
Congratulations on the launch!
I can see this being useful for businesses that need sequential numbers for records such as invoices, projects, or internal reference IDs, especially since it supports custom objects as well.
One question: if a record is deleted or a workflow fails partway through, does the app preserve the sequence, or does it intentionally skip that number? I’m curious how you’ve designed it to handle those scenarios.
Wishing you all the best with the launch!
Hi @jack2026, Nice, sequential numbering is one of those things people end up hacking together with workflows and custom properties, so a dedicated app makes sense. Curious how it handles concurrency if two records get created at the same time, does the app guarantee no duplicate/skipped numbers, or is there a slight lag on the reset logic? That’s usually where these things break for high volume accounts.
@MMarchezi Thankyou! If a record is deleted, lets say 003 is deleted, the next number in the sequence would still be 004 so it would skip it by default. That is providing you haven’t configured the ‘reset’ option within the app which would allow you to re-use it. Same if a workflow fails, it preserves the next number and is queued as such. 
Hey @TeeTech We built the app specifically with scalability and volumes in mind. We absolutely can assure you that no duplicate or skipped numbers would occur, we use very robust queuing logic. Specifically this is one of the issues I have seen having worked as a Hubspot Consultant for many years and partly why we introduced the ‘Enterprise Plan’.
ogether with workflows and custom properties, so a dedicated app makes sense. Curious how it handles concurrency if two records get created at the same time, does the app guarantee no duplicate/skipped numbers, or is there a slight lag on the reset logic? That’s usually where these things break for high volume accounts.
@jack2026 Good to hear it’s built with queuing logic specifically for that and that’s the right way to solve it. Out of curiosity, does the Enterprise plan handle it differently under the hood (e.g a database-level lock or atomic increment), or is it more about higher volume limits and support priority? Would be useful to know for anyone deciding which tier they actually need for high-throughput use cases.