CRM records and relationships

Allocate a business identifier

Allocates a formatted business identifier using a portal sequence.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Use this recipe

Your selection stays with you through signup.

What it does

Existing identifiers are stable; allocation collisions are surfaced as a reconciliation limitation.

What to customize

Set prefix, width, scope and target property.

Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.

Expected outcome

This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.

Sample input

sample-input.json

{
  "inputFields": {
    "field1": "{\"recordId\":\"d1\"}"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "planned",
    "output2": "dry_run",
    "output3": "provider writes suppressed"
  }
}

Returned fields

output1: allocated, existing or error
output2: identifier
output3: allocation detail

What changes when it runs

Reads existing identifier, increments a portal sequence, and patches the record when absent.

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe