Auto-increment/sequential number field for Opportunities

[tidewatch]

We are currently moving from Nutshell CRM to Twenty, and we ran into a gap that feels small on the surface but is very important in day-to-day operations.

In our current setup, every new lead/opportunity automatically receives the next sequential number. We use that number as our internal project number everywhere else across the business: quotes, folders, emails, file naming, job tracking, internal communication, and general reference. We are trying to avoid a process where employees manually assign project numbers, as it introduces mistakes, duplicates, skipped numbers, and inconsistent tracking.

Not having this functionality natively in Twenty is less than ideal, and we have yet to find a stable workaround.

Why this matters

For many teams, an opportunity often becomes the start of an internal job, project, or client file. A reliable sequential project number gives the business a shared reference that can be used across CRM, documents, accounting, operations, and production.

Without native support, teams are pushed toward:

• manual numbering by staff
• complicated workflow chains
• custom code for a basic CRM function
• possible numbering conflicts when records are created close together
• extra migration friction for teams moving from other CRMs

Feature request

It would be extremely helpful to have a native field type or built-in automation for sequential numbering, for example:

Option 1: Auto-number field type

A dedicated field type, like:

• Auto Number
• Sequence
• Incrementing Number

Option 2: Object-level numbering rule

A setting on an object, such as Opportunities, that automatically assigns the next number when a new record is created.

Suggested capabilities

Ideally, this feature would support:

• automatic assignment on record creation
• guaranteed uniqueness
• conflict-safe generation
• configurable starting number
• optional prefix and suffix
• optional zero-padding
• support for Opportunities and custom objects
• support for records created manually, via import, API, and workflows
• optional lock after the first assignment, so the number cannot be changed accidentally
• optional per-object or per-pipeline sequence rules

Why this would help

This is useful not only for sales. It can also support:

• project numbers
• job numbers
• customer reference numbers
• ticket numbers
• order-style tracking IDs
• legacy CRM migration

Many businesses need a simple, human-readable identifier generated automatically that can be referenced outside the CRM.

We would love to see Twenty support this, as it would remove significant friction and make the platform easier to adopt for operational teams, not just sales teams.

Thanks for considering it.

[BOHEUS]

The best approach to this problem is:

• create a custom number field in Opportunity with unique constraint (if you want to make sure that only 1 number can be assigned to 1 opportunity)
• in workflow triggered by creating a new Opportunity record use GraphQL API to get current highest value of number in HTTP Request node
• pass the response to Code node and add 1 to the value
• pass the updated value to Update record

The problem itself isn't difficult to solve with workflows as they're already mature enough for such use cases

[tidewatch]

Appreciate the help here and on Discord. We managed to get it working in the end.

That said, I do think this would benefit many users if it were more native. Digging through GraphQL is more than some users would want to deal with for a standard CRM need.

Still, I have to say the level of customization available is very impressive.

[BOHEUS]

Noted, it'll be added either as workflow or documentation page for future reference

[adamstirtan]

I implemented a workflow for this one for anyone interested. Here's how it works:

1. Trigger: On Opportunity created/updated
2. Delay 3 seconds (this was required because the UI seems to null out the Name)
3. Code node: Generate next name (code below)
4. Update opportunity name

export const main = async (params: {
  opportunityId: string;
}): Promise<object> => {
  const { opportunityId } = params;

  if (!opportunityId) {
    throw new Error("No Opportunity ID provided");
  }

  const dataGraphqlEndpoint = "https://YOUR_INSTANCE/graphql";
  const twentyApiKey = "YOUR_API_KEY";

  const query = `
  query GetPreviousOpportunity($currentId: UUID!) {
    opportunities(
      filter: {
        id: {
          neq: $currentId
        }
      }
      orderBy: {
        createdAt: DescNullsLast
      }
      first: 1
    ) {
      edges {
        node {
          id
          name
          createdAt
        }
      }
    }
  }
`;

  const response = await fetch(dataGraphqlEndpoint, {
    method: "POST",
    headers: {
      Authorization: `Bearer ${twentyApiKey}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      query,
      variables: {
        currentId: opportunityId,
      },
    }),
  });

  if (!response.ok) {
    throw new Error(
      `GraphQL request failed: ${response.status} ${response.statusText}`,
    );
  }

  const result = await response.json();

  if (result.errors?.length) {
    throw new Error(
      `GraphQL query failed: ${result.errors[0].message}`,
    );
  }

  const previousOpportunity =
    result.data?.opportunities?.edges?.[0]?.node;

  // No previous Opportunity means this is the first one.
  if (!previousOpportunity) {
    return {
      previousOpportunity: null,
      nextName: "NO1001",
    };
  }

  if (!previousOpportunity.name) {
    throw new Error(
      `Previous Opportunity ${previousOpportunity.id} has no name`,
    );
  }

  // Expecting something like NO1000
  // Customize this for your naming scheme
  const match = previousOpportunity.name.match(/^NO(\d+)$/);

  if (!match) {
    throw new Error(
      `Previous Opportunity name "${previousOpportunity.name}" is not in the expected NO#### format`,
    );
  }

  const previousNumber = parseInt(match[1], 10);
  const nextNumber = previousNumber + 1;
  const nextName = `NO${nextNumber}`;

  return {
    previousNumber,
    nextNumber,
    nextName,
  };
};

Everyone has their own format, my client here uses "NOXXXX" be sure to customize yours.

Having done this, I think this is too much to ask most people who just need a unique and incrementing Name for their opportunities.

[adamstirtan]

One more thing worth noting. The UI seems to fight this. Where's what I see in my timeline when the workflow runs. For some reason the Name is emptied after clicking "New Opportunity".