| Integration | A collection of logical flows and steps that move data between your app and another app that your customers use. |
| Customer | This represents a business who purchases your product. There is usually a 1-to-1 correlation between customers in your app, and customers you create in Prismatic. |
| Instance | A copy of an integration that has been configured for a specific customer using customer-specific credentials and configuration options. |
| Flow | A set of steps that begin with a trigger and together accomplish a specific task (like moving a type of record from one app to another). Multiple flows can exist in one integration. |
| Component | Reusable code that accomplishes a specific set of tasks or connects to a third-party service. Some components are utility components (like the math component), while others like the Salesforce component are considered “connectors.” Components contain actions like “Get Record” or “Create Record”, triggers which determine when a flow should run, data sources which are dynamically-populated UI elements for the configuration wizard, and connections which dictate how a connector authenticates with a third-party app. |
| Custom Component | A component that you build to connect to your own or a third-party app that you integrate with . |
| Trigger | A trigger determines when a flow should run. It can be a scheduled trigger (e.g. "run every 5 minutes on weekdays"), a webhook trigger that runs when a payload is received, or an instance lifecycle trigger (e.g. run when an instance is deployed). |
| Action | Components are comprised of multiple actions that each accomplish a specific task (like "Create Record" or "List Accounts"). |
| Raw Request | APIs are vast, often comprised of hundreds of endpoints. Built-in components wrap the most commonly used endpoints as actions. If an endpoint you need to interact with is not represented as an action, a Raw Request action can be used to send HTTP requests to that endpoint. |
| Config Variable | A configuration option, presented as an input box, dropdown menu, boolean toggle, etc., that is set by a customer user when they configure and deploy an instance of your integration. Config variables are referenced throughout your integration and can be used to drive logic in your integration. |
| Connection | A connection is a special type of config variable that is made up of fields for things like usernames, passwords, API keys, OAuth 2.0 secrets, host endpoints, API versions, and more - whatever a component needs to know to connect to an outside service. |
| Data Source | A special type of config variable that uses a customer's established connection to dynamically populate a UI element with data from a third-party app. For example, a data source "List Channels" might populate a dropdown menu with list of a customer's Slack channels. |
| Configuration Wizard | When a customer user enables an instance of an integration, they walk through a configuration wizard where they enter credentials for connections and select values for config variables. |
| OAuth 2.0 | Open Authorization 2.0 is an authorization mechanism commonly used in integrations. Customers click a "connect" button within your configuration wizard and consent to allowing your app to access their data in a third-party app. |
| Webhook | An automated message that is sent from one application to another application when certain events occur. Webhooks let applications notify one another in real-time when something has changed in one system and can be used to trigger an instance's flow so the change is reflected in the other system. |
| Marketplace | You can add integrations that you build to your marketplace, which allows your customers to configure and enable instances of those integrations for themselves in a self-serve manner. |
| Embedded Marketplace | The marketplace can be embedded into your application, which allows your customers to configure and enable instances without leaving your app. |
| Embedded Designer | This empowers your customers to build integrations for themselves from within your app. |
| Alert Monitor | You can alert your team via SMS, email or webhook if integrations behave in a way that you don't expect (i.e. errors occur, an integration starts taking 5 minutes when you expect it to take 5 seconds, etc). |
| Prism CLI Tool | The prism command-line tool allows you to manage customers, integrations, instances and custom components from the command line. |
| Prismatic API | The Prismatic API is GraphQL-based, and is the same API that the Prismatic frontend and CLI tools use. You can wrap the Prismatic API in your own scripts to programmatically manage customers, deploy instances and more. |