Instances Overview

An instance of an integration is a copy of an integration that has been configured for a specific customer. When configuring an instance, you or your customers set up connections to third-party applications and services, along with customer-specific configuration variables, by walking through a configuration wizard.

You can deploy instances of your integrations on behalf of your customers, or your customers can enable instances themselves through the integration marketplace. For your customers, the term instance doesn't have any specific meaning - they either have an integration or they don't. When customers log in to Prismatic, they see phrases such as "activate this integration" or "configure this integration." A customer "activates" an "integration" - which is equivalent to deploying an "instance" in organization user terminology.

When a flow within an instance is triggered, an execution of that instance's flow runs.

What happens when an instance is deployed

When an instance is deployed, any triggers marked as deploy triggers are invoked. We recommend adding an alert monitor to instances you deploy so you can be notified if an execution (including a deploy flow) fails to complete.

Webhooks are generated for each flow and become available for invocation after the instance is deployed. Schedule triggers are registered with the Prismatic scheduler and will run at your specified intervals.

Instances are billed based on how long the instance is enabled. You are not billed when an instance is paused.