History and lifecycle management

Prevent repeated submission processing

Track submission state so retries do not create duplicate CRM records.

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

Processing, completed, retryable, and uncertain states are explicit.

What to customize

Set scope and target endpoint.

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": "{\"eventId\":\"submission-1\",\"recordId\":\"c1\",\"properties\":{\"subject\":\"Help\"}}"
  }
}

Sample output

sample-output.json

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

Returned fields

output1: processed, completed, failed, uncertain, or error
output2: new, duplicate, retryable, or reconcile
output3: JSON details

What changes when it runs

Uses ctx.store state and creates one target CRM record.

Ready to try it with your rules?

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

Use this recipe