TABLE OF CONTENTS
Introduction
Event triggers in Keka allows you to automate notifications based on different events within the system. This article will guide you through managing event triggers in Keka.
Glossary
1. Event Trigger: A specific event or workflow in Keka that can automatically trigger notifications. For example, an employee being added in Keka.
2. Action Type: The type notification triggered by an event in Keka. It can include email, Slack notification, webhook, or push notification.
Action Type - Email: An action type that sends automated emails when an event trigger is activated.
Action Type - Slack Notification: An action type that sends automated messages to Slack channels when an event trigger occurs.
Action Type - Webhook: An action type that enables real-time communication and triggers actions in external applications when an event trigger occurs. It involves sending a JSON object representation of the event to a specified URL via HTTP.
Action Type - Push Notification: An action type that sends notifications to mobile devices using push notification services. Push notifications cannot be directly configured in Keka but can be viewed and disabled within event triggers.
3. Conditional Criteria: Conditions that define when an action should be executed within an event trigger. It allows actions to be performed based on specific criteria, such as employment status or department.
Accessing Event Triggers
To access event triggers, follow these steps:
Log in to Keka as an admin who has permission to manage event triggers.
Navigate to Settings and select Integrations and Automation. Go to the Event Triggers tab. Here, you will find a list of event triggers that are already added for you.
Managing Event Triggers
On the event triggers page, you will see a table with the following headers: Event, Category, Action Types, Last Modified, and Status. Clicking on the event name under the event type will open the event trigger.
Adding a New Event Trigger
To add a new event trigger, follow these steps:
Click on the +Add New button. Select a Category from the category drop-down. Once you select a category, you will see a list of available events. Events that have already been added will be disabled and marked as Already Selected.
Click on the Select Event button next to an event to add it to the event trigger list. You can also edit the added event trigger from this page.
Adding Actions to Event Triggers
To add actions to an event trigger, follow these steps:
Click on +Add Action. Select the desired action type from the drop-down menu: Email, Slack Notification, Webhook, or Push Notification.
You can only select a particular action type if it is available for that event trigger. Not all action types would be available for all event triggers.
Depending on the selected action type, additional configuration options will appear.
For example, if you select Send Email, you can specify the email recipients, subject, body, and more.
Configure the action based on your requirements. Click Create to add the action to the event trigger.
Editing, Disabling, or Deleting Actions
To edit, disable, or delete an action within an event trigger, follow these steps:
Click on the three dots inside the action card. Choose the desired action: Edit, Disable, or Delete.
Adding Conditional Criteria
You can add conditional criteria to event triggers to execute actions only when certain conditions are met. Here's how:
Click on +Add Conditional Criteria. Select the data point from the drop-down menu (e.g., Employment Status, Registration Status, Department, Location).
Choose the operator (e.g., equal to, not equal to) and specify the value based on the selected data point.
Add more filters by clicking on +Add New Filter. Click Add to create the conditional criteria.
By following these simple steps, you can easily set up and manage event triggers in Keka. We hope this guide helps you make the most of Event Triggers in Keka
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article