Design tool review
Fields
Fields are the building blocks of your review interface. Map them to properties in your request to display data or capture user input.- Display dynamic data (AI-generated or not) for reviewers to verify and edit.
- Collect input, feedback, and decisions from reviewers.
- Add context to help reviewers make accurate, informed choices.
Layout
You can structure the review interface by adding columns and grids, which you can then add fields to. This gives you control over which fields should be grouped and which information should be easily scannable side-by-side. Grouping (also as a simple vertical “Group”) can also be helpful for defining a single rule (see below) for conditionally showing multiple fields.Rules
You can define rules to only show certain fields or groups conditionally (e.g. based on a button selection or some other field input). Any fields excluded by these rules will not be considered part of the current review - meaning no input validation will be performed on them, and they won’t be included in the webhook event upon review submission.
Interface width
You can increase the width of the review interface if more horizontal space is needed, especially when using columns or grids to show fields side by side.Review title
When adding a text field to your tool review, you can configure it to be used as the review title in the field’s settings. This title will be displayed in the Agent Inbox and in notification emails and Slack messages, making it easier for reviewers to identify and prioritize pending reviews.The review title can be overridden for individual requests by passing a
title attribute in your review request. This is useful when you want to dynamically set the title based on request-specific data.Auto-approval
You can set up a tool review to have its related requests automatically be approved. This is useful to keep monitoring even autonomously acting agents in gotoHuman and to easily switch back to human reviews at any time (think agent, prompt, or model updates).Auto-approval can also be set or overridden with each review request using the
autoApprove request parameter (or meta._gthAutoApprove set to true).Request schema
When you add fields we already show you the data you need to send in your requests to fill or capture input from fields. But you are free to send any payload and just map a request property for each field. Read more about how to send a review request.Setup tool webhook (optional)
If you want your tool to be executed at a separate URL, you can add a tool webhook that will be called for all approved tool reviews.Regardless, all review submissions will be sent to your agent webhook. If a tool webhook is set up, its result will also be delivered to the agent webhook so you can passthrough response data. You can add a tool webhook endpoint on the details page of the tool review.
Webhook schema
The schema of thereviewResult in the event we deliver to your agent and/or tool webhook will match the structure of the review data you send in your request - plus any additional user input you capture.We show you a preview of this response webhook in the tool review editor. It’s dynamic, so playing with the review preview will show you how edits, inputs and selections will be reflected in the webhook event. Read more about webhooks here.
Assign to specific reviewers
You can configure a review to be assigned only to selected reviewers from your team. This is useful when you want certain types of reviews to always go to specific team members based on their expertise or role. On the details page of a tool review, you can select which users should receive reviews of this type. Only the assigned reviewers will see these reviews in their Agent Inbox and receive notifications.While you can set reviewers in the template settings, you can also dynamically assign reviewers for individual requests. This can also be used to selectively override any template default assignments.