Looply Academy
  • Getting Started
    • What is Looply?
    • Deployment Models
  • System Requirements
  • SAP Integration: ABAP Add-on & Access
  • Security & Identity - What IT Teams Need to Know
  • Authenticating Teams User Actions to Enterprise Systems
  • Signing Up & Onboarding Your Team
  • Looply Implementation Plan
  • Looply Integration Demos
  • Integrations
    • Microsoft Integration
    • SAP Integration
      • Installing the ABAP Looply Add-On
        • Gateway Service Setup - Single System
        • Gateway Service Setup - Hub scenario
      • Triggering or Resuming a Looply Workflow from SAP
      • Triggering SAP code from Looply
      • SAP Workflow Integration
      • Varo/Stelo Integration
      • SSL & IP address
      • SSO Authentication
  • App Management
    • Building Apps
    • Deploying apps to Teams App catalog
      • Looply Dashboard
      • Manual Installation
    • Installing Looply Apps
    • Uninstall/Update Looply Apps
    • Teams Admin center
  • Adaptive Cards
    • Building Adaptive Cards
      • Container Elements
      • Content Elements
      • Input Elements
      • Actions
    • Data Binding
    • Conditional Rendering
    • AI Assistant
    • Inline Functions
  • Workflows
    • Building Workflows
    • Triggering Workflows
    • Environment Variables & Profiles
    • Versioning Workflows
    • Using HTTP Requests
    • Using Functions
    • Using Conditionals
    • Using Branch Conditionals
    • Using Advanced Conditionals
    • Using Integrations
      • Adaptive Card Actions
      • SAP Requests
    • Using Redirects
    • Using Override Payload
    • Terminating Workflows
  • Data Vault
    • Variable Datastores
  • Monitoring & Logs
    • Monitoring Workflows
    • Error Notifications
  • API REFERENCE
    • Developer API Overview
    • Workflow API
    • Adaptive Card API
  • Team Management
    • Managing Organisations
    • Team Roles and Permissions
  • Resources
    • JavaScript Libraries
  • Tutorials
    • Creating MS Teams Apps
    • Designing Workflows
    • Building Adaptive Cards
    • Adaptive Cards with AI
    • Examining Workflow Executions
  • Support
    • Changelog
    • Contacting Support
Powered by GitBook
On this page
  • Configuring Error Notifications
  • Email Notifications
  • Webhook Notifications
  1. Monitoring & Logs

Error Notifications

Configure email or webhook notifications if your workflow fails in Looply

PreviousMonitoring WorkflowsNextDeveloper API Overview

Last updated 10 months ago

In modern workflow automation, ensuring that each step of a process is executed correctly is crucial. However, errors can sometimes occur, and timely notifications are essential to promptly address these issues and maintain workflow integrity. Looply provides robust error notification features that allow users to configure alerts to be sent via email or to a specified webhook whenever a step in their workflow fails. This ensures that users are immediately informed of any issues, enabling quick troubleshooting and minimal disruption to their automated processes.

Configuring Error Notifications

Looply offers flexible and customisable options for error notifications, tailored to meet the unique needs of each version of your workflows. You can choose to receive notifications directly to your email inbox or have them sent to a webhook, which can be integrated with your existing monitoring and alerting systems.

Email Notifications

Email notifications in Looply provide a straightforward way to stay informed about errors in your workflows. You can configure email alerts to be sent every time an error occurs, ensuring immediate awareness and quick response to any issues. Notifications can be sent to one or multiple recipients of your choosing, allowing you to keep all relevant team members informed.

To prevent email spam and manage the frequency of notifications, Looply also allows you to set a preferred frequency for receiving error alerts. You can choose to receive notifications every hour, day, week, or month, depending on your needs. This flexibility ensures that you stay informed without being overwhelmed by too many emails.

Email notifications can be configured by entering a Frequency and one or more Recipients from within the Workflow Settings menu of your selected workflow version.

Webhook Notifications

Webhook notifications in Looply offer a powerful and flexible way to integrate error alerts with your existing systems. You can configure webhook notifications alongside email notifications, enabling you to use both methods concurrently. This ensures you have multiple channels of communication, enhancing your ability to respond promptly to any workflow errors.

By setting up a webhook URL, Looply will send a POST request with detailed error information to the specified endpoint every time a step fails. This allows you to send error notifications directly to your own system, where you can handle them appropriately based on your unique requirements.

Looply provides the following configuration options for webhook notifications:

  • Webhook URL: Enter the URL to which Looply will send the error notifications.

  • Custom Headers: Specify any custom headers that need to be included in the notification request - such as an authorisation token or API key.

  • Basic Authentication: If accessing an authenticated URL, you can enter a username and password to enable basic authentication.

Once a webhook URL has been configured, Looply will automatically begin attempting to send POST requests with any information whenever an error occurs within your workflow.

Example Webhook Notification Payload

{
    "workflow_id": "02b2de0a-9a01-4e08-9844-4d9b8e3b37bc",
    "workflow_execution_id": "f39462a9-8b42-4d60-8a74-ca75b0a482cb",
    "organization_id": "2c3662ac-4367-547c-d1be-9f48fba22e63",
    "error": {
        "step": "My Function", 
        "name": "ReferenceError", 
        "message": "x is not defined"
    }
}
Workflow - Error Notifications