Triggers

Manufactory supports (almost) real-time triggers and we sometimes call them triggers event-based triggers.

This is unique - because many other systems don’t offer you the ability to act quickly on incoming data patterns.

Event-based triggers are fired based on actor actions. For example, a trigger could be set up to fire when an actor logs in or logs out, or when an actor takes a specific action within a system or application with or without a specific time-frame or even a specific occurrence count.

A Manufactory trigger consists of the following:

• A condition is a specific rule or set of rules that must be met in order for the trigger to fire.
• A criteria is a specific set of conditions that must be met in order for the trigger to be executed.

Conditions can be based on a variety of factors, such as actor actions, system events or updating actor’s attributes. For example, a condition could be set up to trigger a notification when a certain amount of time has passed since an actor last logged into an application, or when a specific event is stored.

Criteria, on the other hand, are a set of conditions that must be met in order for the trigger to be executed. For example, a criteria could be set up to trigger an alert when a user logs in from an unrecognized device and is attempting to access sensitive data. In this case, the criteria could include conditions such as the user’s location, the type of device being used, and the time of day.

For additional information about triggers, contact us

Related articles

Overview

A scalable event lifecycle engine that handles event collection querying and triggering while giving organizations full control over analytics through API-based infrastructure and webhook functionality at a cost based solely on stored events.

Agent > Send events via the CLI agent

The Manufactory agent facilitates event transmission by accepting base64-encoded actor and event objects with specific attributes for user tracking and monitoring purposes.

Collector > Collecting events via our CLI agent

The Manufactory agent serves as an alternative data transmission solution ideal for IoT devices with limited resources or scenarios requiring API load reduction through direct event sending capabilities.

Manufactory > Collector

A data collection system enables event and actor information transmission through REST API websocket or CLI agent integration while providing a simple interface for viewing the collected data.