How Reviewers Get Notified and Find Pending Reviews in gotoHuman

Updated

Reviewers in gotoHuman find pending work in one place — the Agent Inbox — and can be alerted to it through email digests or Slack notifications. The inbox collects every item that needs human input, whether the review was assigned to a specific person or to the whole team. From a notification, a reviewer can open the review directly instead of navigating to the inbox first.

Where pending reviews appear

gotoHuman is built around the idea that AI workflows should pause and request human input when a step is critical. The platform describes its review flow in four stages:

  1. Setup review — an admin creates a review type with a no-code editor, defining the content to be reviewed and the input to capture.
  2. Send request — the AI workflow requests a human review through an integration, referencing the review type and including the relevant content.
  3. Human review — reviewers find pending reviews in the Agent Inbox or open them directly via a notification.
  4. Handle webhook — completed reviews are sent back to the workflow via webhook so it can continue with the feedback.

The inbox is the central destination. According to the site, reviewers "find all items that need input in their inbox — whether reviews were assigned to them or to the whole team." That means assignment doesn't fragment the queue: personal and team-level reviews surface in the same place.

Notification options

gotoHuman offers several ways to alert reviewers that something is waiting:

Channel What it does
Agent Inbox Always-available list of all pending reviews, individual and team-assigned
Email digests Periodic email summaries of pending items
Slack notifications Alerts delivered into Slack
Short-lived public links Optional links included in notifications, if the team opts in

The public links are worth noting: they are described as short-lived and opt-in, so they suit quick access from a notification without requiring a full sign-in flow for every reviewer. Whether they fit your security posture depends on the sensitivity of the content being reviewed — for high-stakes decisions, you may prefer reviewers to open items through the inbox or a standard notification.

Opening and acting on a review

Once a reviewer reaches an item, the review itself is designed for in-place correction rather than just approval. Review types can capture text, images, markdown, and JSON, and can gather input through buttons, checkboxes, and similar fields. Reviewers can select options or turn on editing to fix AI-generated content on the spot.

For cases where editing isn't enough, gotoHuman adds iteration controls:

  • Retry loops — reviewers can trigger a retry on a field so the AI step regenerates the artifact.
  • Prompt editing — where a one-click retry won't do, the prompt can be passed along in the request so reviewers can change it.
  • Checkpoints — reviewers can navigate between generated versions of an artifact to compare and approve.

This matters for notification design: a Slack or email alert isn't just "something needs approval" — the reviewer may need to compare versions or send work back for regeneration, so opening the item is usually the start of a short review session, not a single click.

A practical setup sequence

If you're configuring this for a team, a workable order is:

  1. Create the review type in the no-code editor, choosing the fields and input controls reviewers will see.
  2. Wire your AI workflow to send review requests through an integration, referencing that review type.
  3. Decide on notification channels — enable email digests, Slack notifications, or both — and decide whether to opt in to short-lived public links.
  4. Confirm the webhook that returns completed reviews to your workflow is receiving feedback correctly.
  5. Test with a sample request: verify it appears in the Agent Inbox for both an individually assigned reviewer and a team-assigned one, and that the notification opens the correct item.

The main thing to check in step 5 is assignment behavior — the site states the inbox covers both individual and team assignments, so a quick test confirms your team sees what you expect before you rely on it in production.

Choosing between channels

There's no single right notification setup; it depends on how your reviewers work.

  • Inbox only suits teams that check a queue on a schedule and want a single source of truth.
  • Email digests help reviewers who aren't in the tool all day but need a periodic nudge.
  • Slack notifications fit teams already working in Slack who want alerts where they already are.
  • Public links reduce friction for occasional reviewers, provided the content sensitivity allows it.

For high-stakes decisions — the kind gotoHuman is explicitly aimed at, such as customer messages and on-brand content — the safer default is to have reviewers open items through the inbox or an authenticated notification, and treat public links as a convenience for lower-sensitivity reviews.