When connecting to WATS with the Zapier app, you will be prompted to connect when you have selected an action. The authentication requires:
- WATS Instance URL
- API Token
To use the WATS Zapier integration, you will need a headless API token and assign that token to a role that has the appropriate permissions for your Zap to work.
Follow these guides to create a token: Edit Roles & Permission and Tokens
Below is an overview of the different permissions needed for each action:
| Zapier Action | Required WATS Permission |
| New Report (Trigger) | System/Report |
| New RCA Ticket (Trigger) | Analytics/Root Cause |
| New Alarm or Notification (Trigger) | - |
| Find RCA Ticket (Search) | Analytics/Root Cause |
| Find Report (Search) | System/App |
| Find Dynamic Yield (Search) | System/Report |
| Find Dynamic Repair (Search) | Analytics/Reports/Repair & RMA/Repair analysis |
| Find WSJF Report (JSON) (Search) | System/Report |
| Find Serial Number History (Search) | System/App |
| Find Aggregated Measurements (Search) | System/App |
| Find Test Step Analysis (Search) | System/App |
| Find UUT Report (Search) | System/App |
| Verify Unit (Search) | Operator Interface/Unit Verification Report |
| Find UUR Report (Search) | System/App |
| Create RCA Ticket (Create) | Analytics/Root Cause |
| Update RCA Ticket (Create) | Analytics/Root Cause |
| Create RCA Email Reminder (Create) | Analytics/Root Cause |
| Get WATS Certificate (PDF) (Create) | System/App |
| Create Report (WSJF) (Create) | System/App |
Process Dropdown Trigger (Hidden Trigger) |
System/App |
Product Group Dropdown Trigger (Hidden Trigger) |
System/App |
ReportId Dropdown Trigger (Hidden Trigger) |
System/App |
Level Dropdown Trigger (Hidden Trigger) |
System/App |
Comments
0 comments
Please sign in to leave a comment.