WATS Zapier App - Triggers

Triggers automatically start your Zap when new data appears in WATS. They poll your WATS instance at regular intervals (1-15 minutes depending on your Zapier plan).

New Report

This trigger fires when a new WATS test report is created and uses the GET /api/report/query/header endpoint. It supports filtering by serial number, part number, revision, batch number, station name, process code, status (Passed/Failed), report type (UUT/UUR), and date ranges, and advanced users can also provide custom OData filter expressions. The design is reliable and configurable, making it well suited for automation workflows that need flexible, precise control over which reports initiate Zap runs.

Configuration Guidelines

Date From (default: 1 hour ago)

• Match this to your Zap polling frequency with a small buffer

• Zap runs every 15 minutes → Set to -30m for example

Top Count (default: 1000)

• If you produce more than 1000 reports within your Date From window, increase this limit

Order By (default: timeStamp)

• Only change to start if you need strict chronological ordering by test execution time and accept the risk of missed reports. See Get UUT History for a detailed explanation of why timeStamp is recommended over start in this scenario.

New RCA Ticket

This trigger fires when a new WATS Root Cause Analysis (RCA) ticket is created and uses the GET /api/RootCause/Tickets endpoint. It supports filtering by ticket status and view type, and you can also narrow results with a search string to target specific tickets. Each newly detected ticketId generates a separate Zap run. The design is straightforward and configurable, so you can shape the automation to fit your process, whether that means updating details, moving the ticket to another system, or triggering other next steps as soon as it’s created.

New Alarm or Notification

This trigger fires when a new WATS Alarm or Notification event is created and uses the POST /api/internal/trigger/GetAlarmAndNotificationLogs endpoint. It supports filtering by alarm type, level, and product group, and each newly detected alarm generates a separate Zap run. The trigger returns rich context about the event, including basic log details, product and process information, yield metrics, counts, measurement statistics, test step data, asset status, and report links when applicable. The design is configurable, so you can quickly automate responses to the different rules you’ve set up in WATS.