Skip to main content
Version: console

Interactor Engine Basic Concepts

Workspace Hierarchy​

Each deployment provides an isolated environment for development, testing, and production.

Account

Workspace associated with your personal account

Organization

Workspace associated with your organization account. For example, your company name

Deployment

Your application where the integration is being implemented. In most cases, it would be the name of your SaaS platform such as myapp.com. By default, each account or organization includes one deployment named Default

Workspace Hierarchy

Environment​

The Interactor Engine provides a framework for managing data sets across different environments, such as Development, Testing, and Production. By default, each deployment includes three environment named Development, Testing, and Production. . This setup allows for isolated testing and deployment processes. You can create as many environments as needed, and each environment is identified and managed using a unique API key. This key is essential for controlling access from SDKs or API calls

Stakeholders: Who uses Interactor Engine?​

There are four groups of engineers that use the Interactor engine.

Developers from SaaS or AI companies looking to:

App Integration Developer​

  • Provide native third-party app integration for users

Connector Developer​

  • Create custom connectors for their unique integration needs
  • Create connectors for their own product to publish in the Interactor app marketplace

Automation Developer​

  • Utilize no-code workflow automation for their own use

Hosted Automation Developer​

  • Provide a user-defined automation feature native to their product