Overview

Automatically process and validate TripAdvisor review claims for your Zealy quests. This template listens for a claim submission, looks up any prior failed claim for the same user & quest, and then routes the new submission to either a success or failure outcome (sending the corresponding task-completed or task-failed response).

How it works

1. The workflow is triggered when a user submits a quest claim (webhook trigger).
2. It queries the Domino/Zealy claims API to fetch the most recent claim for that user & quest with status = FAIL (limit 1).
3. Conditional check:
   • If a previous FAIL claim exists for that user & quest, the automation marks the current submission as validated (task-completed).
   • If no previous FAIL claim is found, the automation marks the submission as failed (task-failed) and returns the reason: "We couldn't find your review".
4. The task-completed / task-failed actions send the appropriate validation result back to the quests system (and can trigger any downstream notifications you’ve configured in Zealy or Domino).

Setup (what to provide)

• tripadvisorReviewURL (required): paste the TripAdvisor review URL for your venue. This should be the direct URL users are expected to submit or reference when proving they left a review.

Recommended flow for communities

• Configure the Zealy quest to require a proof field where users paste their TripAdvisor review URL or upload a screenshot.
• Use this Domino template to handle automatic validations: it will accept resubmissions that follow a prior failed attempt, and otherwise return a failure reason so moderators can review.

Best practices & tips

• Require a direct TripAdvisor review URL or screenshot in the quest claim. Screenshots should include your venue name, rating or reviewer name to make verification reliable.
• Tell users to allow a short propagation window after posting their review — TripAdvisor sometimes takes a few minutes to surface new reviews.
• If you want stricter verification (e.g., checking review content or screenshot analysis), extend the workflow to call an image/A.I. review action or to parse the submitted link.
• Test the flow with a few internal accounts before going live so you can confirm the success/fail routing behaves as expected.

Notes

• This template expects to be used with Domino/Zealy quest claims (it uses domino-quests actions). Ensure your Zealy connection is configured in Domino.
• The template logic accepts a submission only when a prior FAIL claim exists for the same user and quest (useful for validating corrected resubmissions). If you prefer the opposite behavior (approve the first valid submission), adjust the conditional or the claim query accordingly.

Example input

• tripadvisorReviewURL: https://www.tripadvisor.com/ShowUserReview-gXXXX-dYYYYY-rZZZZZZZ-Your_Venue_Name.html

Troubleshooting

• If valid submissions are being rejected, confirm users are submitting the exact TripAdvisor URL or expected proof format.
• If you need custom messages on failure/success, update the task-failed and task-completed action payloads.

Use this template to streamline TripAdvisor-based quest validations and reduce manual moderation workload while keeping clear feedback for participants.