New App! Generate Sequential Numbers

Tired of finding workarounds with the HubSpot RecordID to attach numbers to your deals or customers? :1234:

Today we would like to introduce our second app on the Marketplace!:tada: Baskey’s “Generate Sequential Numbers” app allows you to automatically assign sequential numbers via workflows starting from a number of your choice. With this app you will be able to create any number such as invoice numbers on deals, ticket numbers or customer numbers linked to companies and more. You can modify these in whichever way you like by adding a custom prefix or suffix to the number or deciding on a specific length. This ensures clear, traceable IDs without manual entry and reduces errors in assignment and tracking. It can also help with synchronization with third-party systems that require a specific number format!

You can check out the app on the marketplace and visit our documentation site for more info! We always provide a 14 day free trial when first installing the app. After that it is 9,99 per month or 99,99 for the yearly subscription.

If you have any questions regarding our apps, you can simply ask us via apps@baskey.eu or book a free of charge meeting with one of us! We are always happy to help, so don’t hesitate to contact us!

Also check our other apps which can be useful to create simple automations within workflows in HubSpot: https://baskey.eu/apps/

Congratulations on the app launch, @AnnaBaskey!

Sequential numbering is one of those seemingly simple features that many HubSpot users struggle with, especially on lower-tier plans. I’ve built custom workflows and Make.com scenarios to solve this exact problem for clients, so it’s great to see a native marketplace solution.

A few questions from an implementation perspective:

1. Concurrency Handling: How does the app handle race conditions when multiple deals/tickets are created simultaneously? For example, if two workflows trigger at the same time, does it guarantee no duplicate numbers?

2. Number Gaps: If a workflow enrollment fails or a deal is deleted after number assignment, does that create permanent gaps in the sequence? Or is there a mechanism to reclaim unused numbers?

3. Multi-Object Support: Can the same app instance manage different sequences for different objects? For example, Deal Invoice Numbers starting at 1000, Ticket Numbers starting at 5000, and Company Customer IDs starting at C-001?

4. Integration with External Systems: You mentioned synchronization with third-party systems. Does the app expose any API or webhook capability to notify external systems when a new number is assigned?

5. Prefix/Suffix Flexibility: Can the prefix/suffix include dynamic values? For example, incorporating the year (INV-2026-0001) or deal owner initials (JD-0001)?

The pricing is very competitive compared to building custom solutions. For context, I typically recommend clients use custom coded workflow actions or Make.com for this, which requires more technical knowledge and ongoing maintenance.

One technical consideration for potential users: Make sure to test the workflow enrollment timing. If the number is assigned at the top of a workflow but other enrollment criteria fail later, you might assign numbers to records that don’t ultimately meet your criteria.

Looking forward to seeing how this evolves. The marketplace definitely needs more workflow automation utilities like this.

Hello @amjadkhatri! Thank you so much for reaching out and the interest in our app! I have finally gotten all the information so in the following, you’ll find some answers to the raised questions.

  1. This is indeed tricky, because HubSpot Workflows tend to just throw all enrolled deals at third party apps like ours at once - and expect the apps to handle it. So, we do. We have a system in place (written in go), using robust concurrency features to ensure handling of racing conditions. When enrolling records one by one, like new clients getting client numbers, there is no problem whatsoever. IF you enroll a very large number of records at once, HubSpot might not get an immediate response from our app, and as a default waits for 2 hours before trying again. This is nothing we can influence from our side, but a standard workflow mechanism..
  2. Unfortunately, there are no mechanisms to reclaim unused numbers, so there would be permanent gaps if you delete numbers or records. This is also due to the fact that we don’t save the numbers. You could theoretically run a backup workflow with a different prefix / different numbers, that fills those gaps in those cases. However, this might be very computationally expensive and highly depends on the use case.
  3. Regarding multiple object support, this is easily possible with the “database column” input field. Essentially, you can create as many numbers in as many records as you like, you define the starting number in the workflow action itself. We don’t limit your imagination as a user at this stage when it comes to numbering absolutely everything in your HubSpot portal :wink:
  4. No, not at this point. However, you can use HubSpot Webhooks to integrate the generated number in an external system, like any other HubSpot data. The app has no Webhook on its own, but you can send webhooks after a workflow has finished from HubSpot.
  5. It is possible to include e.g. deal tokens (“data variables”) in the prefix/suffix fields and also custom code action outputs as even more dynamic tokens. To include specific information you could also create individual workflow branches for example for each owner, add the “sequential number” action in each branch, but use the same column name for all actions - this way you can have individual pre-fixes, but only one sequential count of numbers. Also check out our documentation for more information on this!

We hope this answers your questions! If you have any more questions, feel free to reply to this! We really appreciate your input and are always happy to answer questions and get new ideas on how we might improve our apps!