Workflow Advance Options

For specialized use cases, workflows support advanced features extending the automation capabilities beyond standard integrations.

1. Create Variables

Variables dynamically fetch user-specific data during workflow execution. Instead of hardcoding values like names, emails, or departments, use variables to insert information automatically.

Variables

Variables are placeholders for pulling data from user profiles or application records at runtime.

Example variable syntax:

• {{user.first_name}} - User's first name
• {{user.email}} - User's email address
• {{user.department}} - User's department
• {{user.manager}} - User's manager name

Variables Use Cases

Welcome emails:

Subject: Welcome {{user.first_name}} to {{user.department}}!
Body: Hi {{user.first_name}}, your manager {{user.manager}} is excited to have you join the team.

Application provisioning:

• Create user accounts with dynamic usernames
• Assign licenses based on user attributes
• Set permissions based on role or department

Notifications:

• Send customized alerts with user-specific details
• Include dynamic information in Slack messages
• Personalize email templates

Benefits

• Reusable workflows - Same workflow works for any user
• Automatic personalization - No manual data entry required
• Reduced errors - Eliminates copy-paste mistakes
• Scalability - Process hundreds of users with one playbook

Available Variables

Variables pull from:

• User profile data (name, email, role, department, location, manager)
• HRMS integrations (employee ID, hire date, employment type)
• Custom user attributes configured in Zluri
• Application-specific data

Learn more about creating variables and dynamic inputs with all available attributes →

---

2. Custom Actions and HTTP Requests

Build tailored integrations for applications without native Zluri support. Configure custom API calls and HTTP requests to extend automation capabilities.

Custom Actions

Custom actions allow to:

• Call external APIs
• Send HTTP requests (GET, POST, PUT, DELETE)
• Integrate with internal tools
• Connect to proprietary applications

Custom Actions Use Cases

Custom internal tools: The organization uses proprietary software not in Zluri's integration catalog.

Specialized integrations: Need to call specific API endpoints not covered by standard integrations.

Advanced workflows: Require custom logic or data transformation during provisioning.

Third-party services: Integrate with external services via webhook or API.

Learn more about custom actions and HTTP requests →

---

3. Manual Tasks

Convert automated actions to manual tasks when automation is unavailable or preferred manual execution is required.

Manual Tasks

Manual tasks are workflow steps requiring human intervention. Instead of automated execution, Zluri assigns tasks to designated people with instructions for completion.

Manual Tasks Use Cases

No integration available: Application doesn't have Zluri integration (For example, GitHub Copilot).

Security requirements: Organization policy mandates manual approval for certain actions.

Complex procedures: Task requires human judgment or multi-step verification.

Approval workflows: Need documented human confirmation before provisioning.

Learn more about manual tasks →