Assignment and routing
Distribute work by owner weights
Stable weighted owner distribution with exclusions and duplicate protection.
Make it your own
Review the setup and limits below, then open an editable copy in Turbyn.
Use this recipeYour selection stays with you through signup.
What it does
Stable weighted hashing over the sorted eligible owner pool; repeats select the same owner for unchanged policy.
What to customize
Set positive owner weights; pass an optional owner array in field2.
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": "contact-42",
"field2": "[{\"id\":\"senior-a\",\"weight\":3},{\"id\":\"trainee-b\",\"weight\":1} ]"
}
}Sample output
sample-output.json
{
"outputFields": {
"output1": "trainee-b",
"output2": "selected",
"output3": "{\"weight\":1,\"eligible\":2,\"policy\":\"stable-hash\",\"applied\":false}"
}
}Returned fields
- output1
- owner ID or invalid status
- output2
- selected or explicit validation/no-capacity reason
- output3
- explanation
What changes when it runs
Returns a selected owner ID for a downstream workflow assignment; performs no CRM or store writes.
Ready to try it with your rules?
Map your inputs, test a sample and publish the version you’ve checked.