Messaging, documents, and calendar work
Generate contextual notes and summaries
Generate a labeled operational summary and optionally create a CRM note.
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
Current values are distinguished from explicit previous/current comparisons.
What to customize
Configure included fields and labels.
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\",\"fields\":{\"status\":\"paid\",\"amount\":\"100\"}}"
}
}Sample output
sample-output.json
{
"outputFields": {
"output1": "planned",
"output2": "dry_run",
"output3": "Operational summary\nStatus: paid\nAmount: 100"
}
}Returned fields
- output1
- created, generated, empty, or error
- output2
- current or comparison
- output3
- rendered summary
What changes when it runs
Formats selected values and creates an associated HubSpot note outside preview.
Ready to try it with your rules?
Map your inputs, test a sample and publish the version you’ve checked.