Skip to main content

Environments

Actions in the Interval dashboard exist within an environment. When you're using the Interval dashboard, you're always in a particular environment, and you'll only be able to view and run actions within that environment. You can change environments using the switcher in the navigation bar.

Interval comes with two environments by default, Production and Development.

Production is for live actions to be shared with your whole organization, while Development is designed for engineers to rapidly develop actions in a local environment. Each user account with a developer or admin role is assigned its own Development environment and an API key for connecting to this environment, which is referred to as your Personal Development Key.

The environment that your Interval actions run within is determined by the API key that you provide when you create an instance of the Interval class. Your keys can be found on the API keys page in the dashboard.

info

Support for running multiple environments in a single organization (like staging, test, etc.) is currently in private beta.

Please contact us if you would like us to enable it for your organization.

Choosing an environment‚Äč

To run your app in Development, use your Personal Development Key when creating your instance of the Interval class. In Development:

  • Only you can access and run the Interval app instance that is connected using your Personal Development Key.
  • Your history of runs for that action are not stored.
  • Notifications are not sent, but are instead logged to the action's toolbar at the bottom of the screen.

To run your app in Production, use a Live mode Interval API key when creating your instance of the Interval class. With Live mode keys:

  • Actions appear in the Actions tab.
  • Actions can be viewed and run by you and your team.
  • The log of previously run actions and their results is available on the History page.
Was this section useful?