OzyApprovals documentation
  • 👋Welcome to OzyApprovals
  • Product Guide
    • 🛠️Getting set up
      • Registration
      • Account Activation
      • Reset Password
      • Account Management
    • 🏛️Managing an Organization
      • Add Organization
      • Changing Organizations
      • Team Members
      • Approval Balance
      • Access Tokens
      • SLAs
      • Billing
    • ⏳Approvals
      • Processes
      • Stages
    • ⚡Intergrations
      • Make a connection
      • Triggers
        • When a Ticket Is Actioned
        • When a Ticket SLA Is Breached
      • Actions
        • Register an Approval Request
        • Create a Ticket
      • Search
        • Find an Approval Request
        • Find a Ticket
    • ☑️Action Requests
      • Authorized views
      • Search engine
    • 📜Reports
    • ❓FAQs
  • Use Cases
    • Discount Administration
    • Content Publication Approval
    • Leave Requests
    • Expense Reimbursement
    • Project Proposal Approval
    • Access requests
Powered by GitBook
On this page
  1. Product Guide
  2. Intergrations
  3. Triggers

When a Ticket SLA Is Breached

Based on Calendar or Business hours

PreviousWhen a Ticket Is ActionedNextActions

Last updated 1 year ago

This trigger is fired when a ticket SLA is breached at a particular approval stage. The trigger outputs the full ticket details including the SLA breach data.

Triggers can only be configured per stage.

Below is an illustration of how to set up a trigger for a particular stage.

Select the process. Once the process has been chosen, the stages under the selected process will be loaded for you to select.

Proceed to test the step to finish setting up the zap.

Choose an existing webhook or create a new one.

Select the process. Once the process has been chosen, the stages under the selected process will be loaded for you to select.

Click on the run once button and proceed to let a ticket to breach SLA. The trigger will only be activated if the ticket is of the stage selected. The trigger should pick up the data structure for use in subsequent stages

Select the process. Once the process has been chosen, the stages under the selected process will be loaded for you to select.

Regardless of the platform, the "When a Ticket SLA Is Breached" trigger returns the following data structure

{
  "id": "312",
  "ticket_id": "312",
  "process_name": "Overtime Approvals",
  "stage_name": "HR Approval",
  "sla_metrix": "CALENDAR",
  "sla_breach_duration": "0 days, 0 hours, 1 minutes",
  "date_created": "2023-10-07T00:23:15+03:00",
  "date_breached": "2023-10-07T00:25:02+03:00",
  "view_link": "https://ozyapprovals.com/index.php/account/user/views/browse/4",
  "stage_approvers": "user@gmail.com"
}

Sample of email that is sent out when SLA is breached

⚡
Select event
Selecting the stage
Testing the step
Select a trigger
Select a hook
Creating a new webhook trigger
Testing trigger
Select trigger
Select the trigger stage