Overview

Automate verification of user-submitted Google review screenshots for Zealy (or other quest) claims. This automation accepts a screenshot upload, runs an AI-driven validation to confirm the review is genuine and authored by the submitting user, and then either marks the task as completed or returns a failure with an explanation.

How it works

1. A user submits a quest claim with a screenshot (file upload).
2. The automation receives the claim (webhook trigger) and forwards the screenshot to an AI verifier.
3. The AI checks the screenshot against a set of rules (see checks below) and returns either REVIEW_STATUS: pass or REVIEW_STATUS: fail.
4. If the AI returns pass → the workflow marks the task completed (reason: "Success!").
5. If the AI returns fail → the workflow marks the task failed and returns: "You did not provide a screenshot of a 5 star review." (failure message from the template).

What the AI checks

• Google review UI validity: screenshot must show recognizable Google review UI (Maps, Business listing or search review panel), a reviewer profile (name/avatar) and a visible star rating.
• Review quality: the review must be substantive and specific (not a single generic sentence). Short or placeholder/bot-like text will fail. The automation expects roughly ~15 meaningful words or more for a pass.
• Place name match: the business/place name shown in the screenshot must match the configured placeName input (minor capitalization/formatting differences OK).
• Ownership indicator: the screenshot must indicate the review belongs to the logged-in user (e.g., a label like "Your review", edit/delete buttons, or other UI ownership cues). If ownership cannot be verified, the claim fails.

Setup (what to provide)

• placeName (required): the name of the place users must review — enter it exactly as it appears on Google.
• googlePlaceUrl (required): the Google Maps / Business / Search link to the place being reviewed. Use this in the quest description so users know where to post.
• Quest configuration: enable a file upload task for users to attach a screenshot of their published Google review.

Failure reasons (common)

• Screenshot does not show Google review UI or is heavily cropped/obscured.
• No reviewer profile/avatar or star rating is visible.
• The review text is too short, generic, or appears autogenerated.
• The place name in the screenshot does not match the configured placeName.
• No indicator that the review was authored by the submitting user (no "Your review" label or edit controls).

Outputs & notifications

• On success: the task is marked completed (reason: "Success!") via the task-completed action.
• On failure: the task is marked failed and the user receives the failure reason configured in the template.
• Webhook: the template includes a task-submitted webhook URL for claim intake and processing.

Best practices & tips

• Instruct users to take a full screenshot showing: the place name header, the review content, the star rating, and a clear owner indicator ("Your review", edit/delete buttons, or similar).
• Ask users to write a meaningful review (describe their experience, what they liked/didn't like) — one or two short sentences like "Great place!" often fail.
• Recommend users publish the review first and then screenshot the published view (draft or preview screenshots may not show ownership or published status).
• Tell users to avoid heavy cropping or overlays that hide UI elements. Screenshots of the mobile app or desktop Google Maps are both acceptable if UI elements are visible.
• Because screenshots include personal profile information, remind users about privacy and that screenshots will be processed by the automation.

Example inputs

• placeName: "Central Perk Cafe"
• googlePlaceUrl: "https://www.google.com/maps/place/Central+Perk+Cafe"

Notes

• The AI validates content in any language (it translates/transcribes as needed) but still enforces the same quality and ownership checks.
• Although the failure message references a 5‑star review, the AI's quality check accepts any star rating as long as the review is a genuine, substantive entry and ownership is clear.

If you need the template text customized (different success/failure messages or stricter wording), you can update the quest text and the failure/success messages in the workflow.