History and lifecycle management

Record and explain field changes

Record tracked field transitions with deduplication and optional HubSpot note.

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

Only configured fields and explicit event IDs are recorded.

What to customize

Set trackedFields and destination.

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\":\"c1\",\"eventId\":\"e1\",\"occurredAt\":\"2026-09-13T00:00:00.000Z\",\"changes\":{\"status\":{\"old\":\"open\",\"new\":\"won\"}}}"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "recorded",
    "output2": "status:changed",
    "output3": "{\"recordId\":\"c1\",\"eventId\":\"e1\",\"at\":\"2026-09-13T00:00:00.000Z\",\"editor\":null,\"rows\":[{\"field\":\"status\",\"before\":\"open\",\"after\":\"won\",\"kind\":\"changed\"}]}"
  }
}

Returned fields

output1: recorded, duplicate, ignored, or error
output2: change statuses
output3: JSON details or reason

What changes when it runs

Reads input and store; writes a deduplicated history record and a HubSpot note.

Ready to try it with your rules?

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

Use this recipe