Instances Overview

An instance of an integration is a copy of an integration that has been configured for a specific customer. When the instance is configured for a customer or by a customer, connections to third-party apps and services and config variables specific to that customer are set by walking through a configuration wizard.

You can deploy instances of the integrations you create on behalf of your customers or your customers can enable instances themselves through the integration marketplace. For your customers, instance doesn't have any meaning - they either have an integration or they don't. So, when customers log in to Prismatic they're presented phrases like "activate this integration", or "configure this integration". A customer "activates" an "integration" - which is the same as deploying an "instance" in your lingo as an organization user.

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

What happens when an instance is deployed

Once an instance is deployed, any triggers that are marked as deploy triggers are invoked. We recommend adding an alert monitor to instances you deploy, so you can be alerted if an execution (a deploy flow included) fails to run to completion.

Webhooks are generated for each flow and can be invoked after the instance is deployed. Schedule triggers are registered with the Prismatic scheduler and will run at the interval you specify.

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