What are Zapier Searches?
Zapier searches allow you to find and retrieve specific data from your Opigno Enterprise LIP. They’re used to look up existing records, validate data, or find information needed for your automation workflows.Searches are essential for preventing duplicate data, validating user information, and retrieving context needed for other actions in your Zaps.
Available Searches
The Opigno Enterprise Zapier integration provides 2 searches that allow you to retrieve specific training progress information from your learning management system. All searches use GraphQL queries to fetch data and provide structured results for automation workflows.Training Progress Searches
Get Score of User for Training
Search Key:get_score_of_user_for_training_searchDescription: Retrieves the score achieved by a user for a specific training/learning path.
GraphQL Query
GraphQL Query
This search uses the
learningPath query which fetches:- Learning Path Data: Training ID and training details
- Attempt Metrics: User’s attempt data including global score
- Training Information: Complete training metadata
Required Input Parameters
Required Input Parameters
- client_uuid (string, required): The user context UUID that uniquely identifies the user in Opigno Enterprise (equivalent to
user_idin actions). This UUID must be created using thesetUserContextmutation and passed in API requests via theOpigno-Client-UUIDheader. Learn more about User Context Management. - training_id (string, required): The unique identifier of the training/learning path to get the score for. This is the Learning Path ID that can be obtained from the Catalog or My Learning queries. See Learning Path for more details.
Returned Data
Returned Data
- id (integer): Training ID that was queried
- score (integer): The user’s global score for the training (0 if no score available)
Use Cases
Use Cases
- Progress Tracking: Monitor user performance on specific trainings
- Performance Analytics: Generate reports on training effectiveness
- Conditional Logic: Trigger different actions based on score thresholds
- Compliance Monitoring: Track completion scores for mandatory training
Get Status of User for Training
Search Key:get_status_of_user_for_training_searchDescription: Retrieves the current status of a user’s progress on a specific training/learning path.
GraphQL Query
GraphQL Query
This search uses the
learningPath query which fetches:- Learning Path Data: Training ID and training details
- Attempt Metrics: User’s attempt data including completion status
- Training Information: Complete training metadata
Required Input Parameters
Required Input Parameters
- client_uuid (string, required): The user context UUID that uniquely identifies the user in Opigno Enterprise (equivalent to
user_idin actions). This UUID must be created using thesetUserContextmutation and passed in API requests via theOpigno-Client-UUIDheader. Learn more about User Context Management. - training_id (string, required): The unique identifier of the training/learning path to get the status for. This is the Learning Path ID that can be obtained from the Catalog or My Learning queries. See Learning Path for more details.
Returned Data
Returned Data
- id (integer): Training ID that was queried
- status (string): The user’s current status for the training (e.g., ‘COMPLETED’, ‘NOT_STARTED’, ‘IN_PROGRESS’)
Use Cases
Use Cases
- Progress Monitoring: Check if users have started or completed training
- Workflow Automation: Trigger different actions based on completion status
- Compliance Reporting: Track mandatory training completion status
- User Management: Identify users who need to complete specific training
Setting Up Searches
All Opigno Enterprise searches use GraphQL queries to retrieve specific training progress data. Each search requires specific input parameters and returns structured data for automation workflows.1
Choose Your Search Type
- In Zapier, select Opigno Enterprise as your search app
- Choose from the 2 available searches based on your data needs:
- Get Score of User for Training: Retrieve user’s score for a specific training
- Get Status of User for Training: Retrieve user’s completion status for a specific training
- Review the search description and data structure
2
Configure Authentication
- Connect your Opigno Enterprise account using your API credentials
- Ensure your API user has appropriate permissions to access training progress data
- Test the connection to verify authentication works correctly
3
Set Up Search Parameters
Both searches require the same input parameters:Required Parameters:
- client_uuid (string): The UUID of the user whose data you want to retrieve
- training_id (string): The ID of the training/learning path to query
- Map data from previous Zap steps to these required parameters
- Ensure the client_uuid corresponds to a valid user in your Opigno instance
- Verify the training_id exists and is accessible to the user
4
Handle Search Results
- Both searches return structured data with training ID and either score or status
- Set up conditional logic based on the returned values:
- Score Search: Use score values for performance-based automation
- Status Search: Use status values for completion-based workflows
- Configure fallback actions for cases where no data is found
- Map search results to subsequent Zap steps
5
Test Your Search
- Use Zapier’s test feature with valid user UUIDs and training IDs
- Verify that results match your expectations
- Test with different users and trainings to ensure reliability
- Check error handling for invalid parameters
Performance Optimization
Search Efficiency
- Parameter Validation: Always validate client_uuid and training_id before making requests
- Error Handling: Implement proper error handling for GraphQL query failures
- Result Processing: Handle default values appropriately (score = 0, status = ‘NOT_STARTED’)
- Conditional Logic: Use search results to drive conditional workflows efficiently
API Usage Management
- GraphQL Queries: Both searches use the same
learningPathquery with different response mapping - Error Handling: Searches throw descriptive errors when GraphQL queries fail
- Parameter Mapping: Ensure proper mapping of input parameters to GraphQL variables
- Result Validation: Validate search results before using them in subsequent steps
Troubleshooting Searches
Search Not Returning Expected Data
Search Not Returning Expected Data
Common causes:
- Invalid client_uuid parameter (user doesn’t exist)
- Invalid training_id parameter (training doesn’t exist)
- User doesn’t have access to the specified training
- Training hasn’t been started (returns default values)
- Verify client_uuid corresponds to a valid user in Opigno
- Check that training_id exists and is accessible
- Ensure user has proper permissions for the training
- Handle default values appropriately (score = 0, status = ‘NOT_STARTED’)
GraphQL Query Errors
GraphQL Query Errors
Common causes:
- Invalid training_id format or value
- Insufficient API permissions
- Opigno instance configuration issues
- Network connectivity problems
- Validate training_id format before making requests
- Ensure API user has appropriate permissions
- Test GraphQL queries directly against Opigno API
- Check Opigno instance logs for detailed error messages
- Implement proper retry logic for transient failures
Unexpected Search Results
Unexpected Search Results
Common scenarios:
- Score returns 0 when user hasn’t started training
- Status returns ‘NOT_STARTED’ for new assignments
- Training ID doesn’t match expected training
- Check for default values in search results
- Verify training_id mapping is correct
- Implement conditional logic for different result scenarios
- Log search parameters and results for debugging