Skip to main content

​
What are Zapier Actions?

Zapier actions are operations that your automation workflows perform in your Opigno Enterprise LIP. They execute specific tasks like creating users, updating assignments, or managing learning content based on triggers from other applications.
Actions are the “do” part of your automation - they take data from triggers and use it to perform specific operations in your Opigno instance.

​
Available Actions

The Opigno Enterprise Zapier integration provides 2 actions that allow you to register users for training and live sessions in your learning management system. All actions use GraphQL mutations to create registrations and provide structured results for automation workflows.

​
Registration Actions

​
Register User to Training

Action Key: register_user_to_training_create
Description: Registers a user for a specific training/learning path in your Opigno Enterprise instance.
This action uses the createLpIndividualMembership mutation which:
  • Creates Individual Membership: Establishes a user’s enrollment in a learning path
  • Returns Membership Data: Provides membership ID and type information
  • Handles Errors: Returns detailed error messages for failed registrations
  • user_id (string, required): The ID of the user to register for the training
  • training_id (string, required): The ID of the training/learning path to register the user for
  • id (string): The membership ID created for the user’s enrollment
  • type (string): The type of membership created (typically ‘INDIVIDUAL_MEMBERSHIP’)
  • Automated Training Assignment: Register users for training based on job roles or departments
  • Compliance Training: Automatically register users for required compliance courses
  • Onboarding Automation: Register new employees for onboarding paths
  • Skill Development: Register users for learning paths based on performance reviews

​
Register User to Live Session

Action Key: register_user_to_live_session_create
Description: Registers a user for a specific live session in your Opigno Enterprise instance.
This action uses the registerToLiveSession mutation which:
  • Creates Live Session Registration: Establishes a user’s enrollment in a live session
  • Returns Registration Data: Provides registration ID, related learning path, and attendance status
  • Handles Errors: Returns detailed error messages for failed registrations
  • user_id (string, required): The ID of the user to register for the live session
  • live_session_id (string, required): The ID of the live session to register the user for
  • id (string): The registration ID created for the user’s enrollment
  • relatedLpId (string): The ID of the related learning path (if applicable)
  • isAttended (boolean): Whether the user has attended the live session
  • Live Session Management: Register users for scheduled live training sessions
  • Event Registration: Automatically register users for training events
  • Calendar Integration: Register users and sync with calendar systems
  • Attendance Tracking: Track and manage live session attendance

​
Setting Up Actions

All Opigno Enterprise actions use GraphQL mutations to create user registrations for training and live sessions. Each action requires specific input parameters and returns structured data for automation workflows.
1

Choose Your Action

  1. In Zapier, select Opigno Enterprise as your action app
  2. Choose from the 2 available actions based on your automation needs:
    • Register User to Training: Register users for learning paths/training
    • Register User to Live Session: Register users for live training sessions
  3. Review the action description and required parameters
2

Configure Authentication

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

Set Up Action Parameters

Both actions require specific input parameters:Register User to Training:
  • user_id (string): The ID of the user to register
  • training_id (string): The ID of the training/learning path
Register User to Live Session:
  • user_id (string): The ID of the user to register
  • live_session_id (string): The ID of the live session
Parameter Mapping:
  • Map data from previous Zap steps to these required parameters
  • Ensure the user_id corresponds to a valid user in your Opigno instance
  • Verify the training_id or live_session_id exists and is accessible
4

Handle Action Results

  1. Both actions return structured data with registration information
  2. Set up conditional logic based on the returned values:
    • Training Registration: Use membership ID and type for tracking
    • Live Session Registration: Use registration ID and attendance status
  3. Configure error handling for failed registrations
  4. Map action results to subsequent Zap steps
5

Test Your Action

  1. Use Zapier’s test feature with valid user IDs and training/session IDs
  2. Verify that registrations are created successfully in your Opigno instance
  3. Test with different users and trainings/sessions to ensure reliability
  4. Check error handling for invalid parameters

​
Data Mapping and Transformation

​
Field Mapping

When setting up registration actions, you’ll need to map data from triggers to action parameters: 
// Trigger data (e.g., from new user registration)
{
  "user_id": "123",
  "training_id": "456",
  "user_email": "john.doe@company.com"
}

// Action parameter mapping
{
  "user_id": "{{user_id}}",
  "training_id": "{{training_id}}"
}

​
Data Transformation

Use Zapier’s formatter to transform data before sending to actions:
ID Validation: Ensure user_id, training_id, and live_session_id are valid before making registration requests to prevent GraphQL errors.
Duplicate Registrations: Actions will fail if trying to register a user who is already registered for the same training or live session.

​
Error Handling

​
Common Action Errors

Symptoms:
  • “Unauthorized” or “Forbidden” errors
  • Actions fail to execute
Solutions:
  • Verify API credentials are correct
  • Check user permissions for creating registrations
  • Ensure API user has access to the specified training/session
  • Regenerate API tokens if expired
Symptoms:
  • “Registration failed” error messages
  • Actions fail with GraphQL error details
  • Invalid user_id or training_id/live_session_id parameters
Solutions:
  • Validate all input parameters before making requests
  • Ensure user_id corresponds to a valid user in Opigno
  • Verify training_id or live_session_id exists and is accessible
  • Check for duplicate registrations (user already registered)
  • Review GraphQL mutation error messages for specific issues
Symptoms:
  • “User already registered” or similar error messages
  • Actions fail when trying to register existing users
Solutions:
  • Use search actions to check for existing registrations first
  • Implement conditional logic to handle duplicate registrations
  • Use different actions for updating existing registrations
  • Set up proper error handling workflows for duplicate scenarios

​
Best Practices

​
Action Optimization

  • Parameter Validation: Always validate user_id, training_id, and live_session_id before making requests
  • Error Handling: Implement proper error handling for GraphQL mutation failures
  • Duplicate Prevention: Check for existing registrations before creating new ones
  • Testing: Always test actions with real data before going live

​
Data Management

  • ID Validation: Ensure all IDs correspond to valid entities in your Opigno instance
  • Registration Tracking: Use returned registration IDs for tracking and follow-up actions
  • Error Logging: Log registration failures for debugging and monitoring
  • Audit Trails: Monitor action execution for compliance and debugging

​
Security Considerations

  • Access Control: Ensure API user has appropriate permissions for creating registrations
  • Data Privacy: Be mindful of sensitive user information in registration data
  • API Limits: Monitor API usage to avoid rate limiting
  • Permissions: Regularly review and update user permissions for registration actions

​
Advanced Action Patterns

​
Conditional Registration Actions

Set up registration actions that only execute under specific conditions:
Conditional Registration Logic
// Only register user for training if they meet criteria
if (userDepartment === "Sales" && trainingType === "Sales Training") {
  // Execute register user to training action
  await registerUserToTraining(user_id, training_id);
} else {
  // Skip registration or send notification
  await sendNotification("User not eligible for this training");
}

​
Multi-Step Registration Workflows

Chain multiple registration actions together for complex workflows:
1

Check Existing Registration

Use search actions to check if user is already registered
2

Register for Training

Register user for the main training program
3

Register for Live Session

Register user for associated live session (if applicable)
4

Send Confirmation

Send confirmation email with registration details
5

Update External System

Update CRM or HR system with registration status

​
Next Steps

Explore more automation capabilities:

Zapier Searches

Learn how to find and retrieve specific data from your Opigno instance.

Zapier Triggers

Discover how to set up automated triggers for your workflows.
⌘I