Skip to main content
Version: 6.1.0

Basic Concepts

Interactor Engine is a user-defined automation solution. It is an event processing micro-services infrastructure allowing configuration and execution of user-defined automation integrated with various external services.

Stake Holders

There are the main stakeholders.

  • Platform: Deploy Interactor Engine integrated into their existing product
  • Developer: Create and manage services that can be used in automation
  • User: Create and manage automation

System

Interactor Engine is comprised of the following sub-systems.

  • Service Handling Engine
  • Automation Execution Engine
  • Datastore
  • Logic Execution Engine

Service

Services are developed by users with developer privileges and may be shared among users within a single platform deployment, or across deployments. Services define details of how an external service may be integrated into user automation. Details may include

  • Events produced by the service
  • Actionable triggers
  • Actions toward the service
  • Conditions specific to the service
  • Data types custom to the service

Automation

A user may define an automation with details of what to be done based on an actionable trigger.

Each Automation is comprised of the following sub-components.

  • Trigger
  • Action
  • Condition

Datastore

Configuration and history data are stored for persistence.

Logic Execution

Service developers may use Javascript to create logic for various lifecycle events such as

  • Webhook notification routing
  • Webhook notification response
  • Webhook notification triggered and automation using the service trigger
  • Automation created using the service trigger
  • Automation deleted that was using the service trigger
  • Service action is executed as a step in the automation logic being executed
  • Service condition is checked as a step in the automation logic being executed