How to Assign Unique Sequential Numbers in HighLevel

If you’ve ever needed to hand out unique, sequential numbers inside a HighLevel automation, think limited edition print buyers getting “Print #1, #2, #3,” or establishing order position in a flash sale, you know it’s not obvious where to start.

In a recent training prompted by an HL Pro Tools community request, our co-founder and CEO, Matt Deseno, walked through a clean, reliable way to build a “workflow counter” in HighLevel.

It’s a simple pattern that leverages sub-account Custom Values as a global counter, then immediately saves the assigned number back to the contact so it’s usable everywhere.

As Matt put it:

“High Level is incredibly powerful… sometimes it feels a little overwhelming just with all the possibilities.”

The goal of this walkthrough is to make one of those possibilities feel simple.

Start with the Goal and the Use Case

Before building, decide what your counter represents.

👉 Are you assigning a “Print Number,” “Order Position,” “Ticket Number,” or something else?

Common scenarios this helps with:

• Limited edition product runs where each buyer needs a unique number
  
• Flash sales and waitlists where position matters
  
• Event ticketing or seat assignments
  
• Any campaign where a sequential identifier keeps things organized

Clarity at this stage will guide your naming choices and how you reference the number later in templates and integrations.

Custom Values vs. Custom Fields: The Quick Sanity Check

A big part of making this work is understanding what lives where in HighLevel.

As Matt explained:

“When you see Custom Values over here, consider it company values or sub-account… If you see Custom Fields over there, those are typically contact fields.”

• Custom Values → Sub-account level (Settings). Perfect for storing the running total—the global counter.
  
• Custom Fields → Contact level (forms/surveys). Store data unique to each contact.

For this pattern, you’ll:

1. Create a Custom Value that holds the running total.
   
2. Increment that Custom Value inside a workflow using a Math Operation.
   
3. Copy the updated number into a Contact Custom Field so it sticks to the person who just entered the workflow.

Step 1: Create Your Shared Counter

• Go to Settings > Custom Values.
  
• Create a new Custom Value (ex: “Workflow Count,” “Unique Count,” “Print Counter”).
  
• Leave it blank or set it to 0, both work.

Step 2: Build the Counter Inside the Workflow

Head to Automations > Workflows and either create a new workflow or open the one where numbering should happen.

1. Add a Math Operation action.
   
   • Name it something clear like “Add 1 to Workflow Counter.”
     
   • Configure it:
     
     • Source: Custom Values
       
     • Field: Your “Workflow Count” Custom Value
       
     • Operation: Add 1
       
     • Update: Save back to the same Custom Value
       

This action is the engine of your counter. On the first run, it becomes 1. Every subsequent contact increments sequentially.

Step 3: Persist the Number to the Contact

Immediately after the Math Operation:

2. Add an Update Contact Fields action.
   
   • If needed, create a Contact Custom Field (ex: “Print Number,” “Order Number,” “Sequence Number”).
     
   • Map the value from your Custom Value (the workflow counter) into that Contact Custom Field.

✅ This step ensures the number is locked to the contact instead of just floating globally.

Step 4: Use the Number Everywhere You Need It

Once stored on the contact, you can:

• Merge it into emails/SMS using tokens.
  
• Pass it into zaps or webhooks for fulfillment/logistics.
  
• Display it on confirmations, receipts, certificates, or badges.

👉 Pro tip: Always reference the Contact Custom Field token (not the global Custom Value) to keep messaging accurate.

Step 5: Test and Document Your Setup

• Run test contacts through the workflow.
  
• Confirm the counter starts at 1 and increments properly.
  
• Check that the number appears in the right Contact Custom Field.
  
• Send yourself test emails/SMS with the token.
  
• Document naming conventions for your team.

Practical Considerations & Pro Tips

• Concurrency awareness: If many contacts hit the workflow simultaneously, monitor increments. Consider staging or small delays if needed.
  
• Multiple counters: Running several campaigns? Create separate Custom Values + Custom Fields per campaign.
  
• Resetting: For new launches, manually reset the Custom Value back to 0 (after confirming all old numbers are locked).
  
• Clear naming: Label actions plainly (“Add 1 to Workflow Counter,” “Map Counter to Contact”).
  
• Keep it simple: This pattern is lightweight and reliable—avoid overcomplicating.

Why This Works So Well

This approach uses Custom Values as a global counter (the “what’s next” number). By persisting that number to the contact level, you unlock flexibility and reliability:

• Use it in messaging.
  
• Pass it into integrations.
  
• View it right on the contact record.

Perfect for ecommerce launches, event ticketing, limited-quantity promotions, or any sequence-based campaign.

As Matt reminded:

The power in HighLevel is real, and the possibilities can feel endless. This is one of those tidy building blocks that turns possibility into practice.

Quick Setup Checklist ✅

• Create a Custom Value under Settings > Custom Values.
  
• Add a Math Operation to increment and save it.
  
• Create a Contact Custom Field and map the value into it.
  
• Reference the Contact Custom Field token in all templates/integrations.
  
• Test with sample contacts and document everything.
  
• Monitor during high-traffic launches.

Wrapping It Up 🎁

At the end of the day, this workflow counter is one of those “tiny hinge, big door” moves inside HighLevel. It’s simple to set up, but it unlocks a ton of possibilities: from running limited-edition drops, to keeping flash sales orderly, to giving every client or attendee a number that actually means something.

So next time you need to keep your campaigns organized (and impress your clients while you’re at it), remember this pattern. It’s one of those foundational building blocks that makes HighLevel less overwhelming and a whole lot more powerful.

👉 Keep it tidy.
👉 Test it before launch.
👉 And always persist the number to the contact.

Do that, and you’ll never have to stress about “what number comes next” again.