History and lifecycle management

Archive a record with scoped dependents

Plan and archive a record plus explicitly included dependents with protection checks.

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

Protected dependents block destructive work; partial failures are reported.

What to customize

Set object/dependent types and allowed/protected IDs.

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\":\"co1\",\"dependentIds\":[\"c1\"]}"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "planned",
    "output2": "dry_run",
    "output3": "No provider calls or changes were made."
  }
}

Returned fields

output1: planned, archived, partial, blocked, or error
output2: count or reason
output3: JSON per-record results

What changes when it runs

Reads associations and archives only scoped dependents and the root in live mode.

Ready to try it with your rules?

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

Use this recipe