Skip to main content

​
What are Zapier Triggers?

Zapier triggers are events that automatically start your automation workflows when something happens in your Opigno Enterprise LIP. They monitor your system for specific changes and initiate actions in other applications when those changes occur.
Triggers are automatically subscribed to event-registering webhooks in your Opigno instance. When an event occurs, Opigno automatically sends the required information to Zapier, which then passes that data to other apps in your Zap.

​
Available Triggers

The Opigno Enterprise Zapier integration provides 6 triggers that monitor different events in your learning management system. All triggers use webhook subscriptions that are automatically registered when you set up the integration. Zapier handles all webhook infrastructure automatically—no manual configuration required.

​
Training Events

​
User Registered to Training

Trigger Key: register_user_to_training_trigger
Description: Fires when a user registers for a training/learning path in your Opigno Enterprise instance.
This trigger uses the registerUserToTrainingTrigger query which fetches:
  • Learning Path Data: Training ID, title, and publication timestamp
  • User Context: User ID, UUID, and display name
  • training_id (string): Unique identifier of the training
  • user_id (string): Internal user ID in Opigno
  • user_uuid (string): Unique user identifier (UUID format)
  • user_display_name (string): User’s display name
  • training_name (string): Title of the training
  • timestamp (string): Publication timestamp of the training
  • Welcome Email Automation: Send personalized welcome emails to newly registered users
  • CRM Integration: Add new learners to your CRM system automatically
  • Slack Notifications: Alert your team when users register for training
  • Onboarding Workflows: Trigger multi-step onboarding sequences

​
User Completed Training

Trigger Key: user_completed_training_trigger
Description: Activates when a user successfully completes a training/learning path.
This trigger uses the userCompletedTrainingTrigger query which fetches:
  • Learning Path Data: Training ID, title, and publication timestamp
  • User Context: User ID, UUID, and display name
  • training_id (string): Unique identifier of the completed training
  • user_id (string): Internal user ID in Opigno
  • user_uuid (string): Unique user identifier (UUID format)
  • user_display_name (string): User’s display name
  • training_name (string): Title of the completed training
  • timestamp (string): Completion timestamp
  • Certificate Generation: Automatically generate and send completion certificates
  • Achievement Recognition: Post completion announcements on social platforms
  • Progress Tracking: Update external systems with completion data
  • Next Steps Automation: Trigger follow-up training recommendations

​
Live Session Events

​
User Registered to Live Session

Trigger Key: user_registered_to_live_session_trigger
Description: Fires when a user registers for a live session.
This trigger uses the userRegisteredToLiveSessionTrigger query which fetches:
  • Live Session Data: Session ID and bucket information (ID, title, type, status)
  • User Context: User ID, UUID, and display name
  • live_session_id (string): Unique identifier of the live session
  • user_id (string): Internal user ID in Opigno
  • user_uuid (string): Unique user identifier (UUID format)
  • user_display_name (string): User’s display name
  • live_session_bucket_id (string): ID of the session bucket
  • live_session_bucket_name (string): Name of the session bucket
  • Calendar Integration: Add live sessions to user calendars
  • Reminder Automation: Send reminder emails before live sessions
  • Attendance Tracking: Update external systems with registration data
  • Resource Distribution: Share session materials with registered users

​
User Attended Live Session

Trigger Key: user_attended_live_session_trigger
Description: Activates when a user attends a live session.
This trigger uses the userAttendedLiveSessionTrigger query which fetches:
  • Live Session Data: Session ID, bucket info, start/end dates, and bucket requirements
  • User Context: User ID, UUID, and display name
  • live_session_id (string): Unique identifier of the attended live session
  • user_id (string): Internal user ID in Opigno
  • user_uuid (string): Unique user identifier (UUID format)
  • user_display_name (string): User’s display name
  • live_session_bucket_id (string): ID of the session bucket
  • live_session_bucket_name (string): Name of the session bucket
  • live_session_start_date (integer): Start date timestamp of the session
  • timestamp (integer): End date timestamp of the session
  • Attendance Tracking: Update HR systems with attendance records
  • Follow-up Automation: Send post-session surveys or materials
  • Certificate Generation: Issue attendance certificates
  • Analytics Integration: Track live session engagement metrics

​
Certificate Events

​
Certificate Expired

Trigger Key: certificate_expired_trigger
Description: Fires when a user’s certificate expires.
This trigger uses the certificateExpiredTrigger query which fetches:
  • Certificate Data: Certificate ID, related training info, expiration date, download URL, validation date, and status
  • User Context: User UUID and display name
  • certificate_id (string): Unique identifier of the expired certificate
  • user_uuid (string): Unique user identifier (UUID format)
  • user_display_name (string): User’s display name
  • related_training_id (string): ID of the training the certificate was for
  • related_training_name (string): Name of the training the certificate was for
  • timestamp (integer): Expiration timestamp
  • Renewal Notifications: Send automated renewal reminders to users
  • Compliance Tracking: Update compliance systems with expired certificates
  • Re-training Automation: Trigger re-enrollment in required training
  • Manager Alerts: Notify managers of team member certificate expirations

​
Training Management Events

​
New Revision for Training

Trigger Key: new_revision_for_training_trigger
Description: Activates when a new revision of a training becomes available.
This trigger uses the newRevisionForTrainingTrigger query which fetches:
  • Learning Path Data: Training ID, title, and publication timestamp
  • training_id (string): Unique identifier of the updated training
  • training_name (string): Title of the training
  • timestamp (string): Publication timestamp of the new revision
  • Content Distribution: Automatically share new training announcements
  • Marketing Automation: Promote updated content through various channels
  • Team Notifications: Alert relevant teams about new training versions
  • External System Updates: Sync training catalogs with other platforms

​
Setting Up Triggers

All Opigno Enterprise triggers use webhook subscriptions that are automatically registered during setup. When events occur in Opigno, the system automatically sends the required information to the subscribed webhooks with trigger-specific data.
1

Choose Your Trigger

  1. In Zapier, select Opigno Enterprise as your trigger app
  2. Choose from the 6 available triggers based on your automation needs:
    • Training Events: User registration and completion
    • Live Session Events: Registration and attendance tracking
    • Certificate Events: Expiration monitoring
    • Training Management: New revision notifications
  3. Review the trigger description and data structure
2

Configure Authentication

  1. Connect your Opigno Enterprise account using your API credentials
  2. Ensure your API user has appropriate permissions for the data being accessed
  3. Test the connection to verify authentication works correctly
3

Understand Trigger Data

Each trigger is automatically subscribed to specific webhook events and receives relevant data:Training Triggers (register_user_to_training_trigger, user_completed_training_trigger):
  • Triggered when users register for or complete training
  • Receives user UUID, training ID, and event details
Live Session Triggers (user_registered_to_live_session_trigger, user_attended_live_session_trigger):
  • Triggered when users register for or attend live sessions
  • Receives user UUID, live session ID, and session details
Certificate Trigger (certificate_expired_trigger):
  • Triggered when certificates expire
  • Receives certificate ID, user UUID, and training details
Training Management Trigger (new_revision_for_training_trigger):
  • Triggered when new training revisions are published
  • Receives training ID and publication details
4

Test Your Trigger

  1. Use Zapier’s test feature to retrieve recent webhook data
  2. Review the output fields to ensure they contain the expected information
  3. Verify the data types match your automation requirements
  4. Confirm that events from your Opigno instance trigger the webhook correctly

​
Best Practices

​
Webhook Infrastructure

Automatic Webhook Registration: Zapier automatically subscribes to event-registering webhooks when you set up triggers. When events occur in Opigno, the system automatically sends the required information to Zapier. Ensure your Opigno instance can reliably send webhook notifications for consistent trigger operation.
Permission Requirements: The certificate trigger uses client UUID masquerading due to permission limitations. This is a temporary workaround that should be monitored for security implications.

​
Data Management

  • Validate Webhook Data: Verify that webhook payloads contain all expected fields (user_uuid, training_id, etc.)
  • Handle Missing Data: Triggers include fallback values for missing data, but verify critical fields are present
  • Test with Real Events: Always test triggers by performing actual events in your Opigno instance
  • Monitor Error Handling: Triggers throw descriptive errors when webhook processing or GraphQL queries fail

​
Security Considerations

  • API Permissions: Ensure your API user has appropriate permissions for all data being accessed
  • Webhook Security: Zapier securely handles webhook authentication automatically—no manual configuration needed
  • Data Privacy: Be mindful of sensitive user information in trigger data (UUIDs, display names)
  • Audit Trails: Monitor webhook deliveries and trigger executions for security compliance

​
Troubleshooting Triggers

Common causes:
  • No new events have occurred in your Opigno instance
  • Webhook subscriptions not properly established during setup
  • Authentication issues with Opigno API
  • Opigno system unable to send webhook notifications
  • Insufficient API permissions for the data being accessed
Solutions:
  • Verify that the expected events are actually occurring in Opigno (e.g., users registering for training)
  • Reconnect your Zapier integration to re-establish webhook subscriptions
  • Test API credentials and ensure they haven’t expired
  • Check that your API user has appropriate permissions for all queried data
  • Verify your Opigno instance can send outbound webhook requests
  • Review webhook delivery logs in Zapier’s trigger history
Common causes:
  • Webhook payload missing required fields
  • GraphQL query returning null values
  • Insufficient API permissions for specific data
  • User context not found for provided UUID
  • Event data incomplete in Opigno when webhook is sent
Solutions:
  • Review webhook payload structure in Zapier’s trigger history
  • Check API user permissions for all required data
  • Test with valid user UUIDs and training IDs
  • Verify that events in Opigno contain all necessary information before triggering webhooks
  • Check webhook delivery logs for payload details
Common causes:
  • Invalid training_id or user_uuid in webhook payload
  • API user lacks permissions for specific queries
  • Opigno instance configuration issues
  • Network connectivity problems between Opigno and Zapier
Solutions:
  • Review webhook payload data in Zapier’s trigger history
  • Verify that webhook data contains valid IDs
  • Ensure API user has appropriate permissions
  • Test GraphQL queries directly against Opigno API
  • Check Opigno instance logs for webhook delivery errors
  • Confirm API connectivity and webhook delivery reliability

​
Next Steps

Once you’ve set up your triggers, explore how to:

Zapier Actions

Learn how to configure actions that respond to your triggers and automate workflows.

Zapier Searches

Discover how to find and retrieve specific data from your Opigno instance.
⌘I