Skip to main content
A conversation your agent had becomes a transcript you can search, read, and label. This recipe runs a conversation, finds its transcript, fetches the turns, and attaches a custom property to it, which is how you tag conversations with your own outcome data.
Last verified 2026-08-15 by executing the recipe end to end.

The recipe

main.sh

How it works

  • Send runs the conversation. The userID in the path is the conversation’s identity, so it is also how you find the transcript afterwards.
  • Transcripts are written asynchronously. A conversation that has just finished is not immediately searchable, which is why this recipe polls rather than reading once.
  • Search transcripts filters the list. environmentAlias belongs in the request body here, not the query string.
  • Get transcript returns the turns themselves, which is the payload you would render in your own review tool.
  • Create property defines a label, typed string, number, or boolean, that you can then set on any transcript. Defining the property and setting its value are separate calls.

When it fails