| Integration | A collection of logical flows and steps that move data between your app and other apps your customers use. |
| Customer | A business that purchases your product. Typically, there is a one-to-one relationship between customers in your application and those created in Prismatic. |
| Instance | A configured deployment of an integration for a specific customer, using their credentials and configuration options. |
| Flow | A sequence of steps beginning with a trigger, designed to accomplish a specific task (such as moving records between systems). An integration can contain multiple flows. |
| Execution | A single run of an instance's flow. An instance may have multiple concurrent executions. |
| Component (Connector) | Reusable code that performs specific tasks or connects to third-party services. Components can be utility-focused (e.g., math operations) or connection-focused ("connectors" such as the Salesforce component). Components contain actions (e.g., "Get Record"), triggers, data sources for dynamic UI elements, and connections for third-party authentication. |
| Custom Component | A component you build to connect to your own application or a third-party service you integrate with. |
| Trigger | Determines when a flow should run. Types include scheduled triggers (e.g., "run every 5 minutes on weekdays"), webhook triggers that respond to incoming payloads, and instance lifecycle triggers (e.g., run when an instance is deployed). |
| Action | An individual operation within a component that performs a specific task (such as "Create Record" or "List Accounts"). |
| Raw Request | A mechanism to interact with API endpoints not covered by built-in component actions. While components wrap common endpoints as actions, Raw Request allows you to send HTTP requests to any endpoint. |
| Config Variable | A configuration option presented as an input box, dropdown menu, boolean toggle, or other UI element. Customers set these when configuring integration instances. Config variables can be referenced throughout the integration and drive its logic. |
| Connection | A specialized config variable containing authentication and connection details such as usernames, passwords, API keys, OAuth 2.0 credentials, endpoints, and API versions required for connecting to external services. |
| Data Source | A dynamic config variable that uses a customer's connection to populate UI elements with data from third-party systems. For example, a "List Channels" data source might populate a dropdown menu with the customer's Slack channels. |
| Configuration Wizard | The interface where customers enter credentials and select config variable values when enabling an integration instance. |
| OAuth 2.0 | An authorization protocol commonly used in integrations. Customers authorize access to their third-party application data by clicking a "connect" button in your configuration wizard. |
| Webhook | A real-time notification sent between applications when events occur. Webhooks enable systems to notify each other of changes and can trigger integration flows to sync those changes. |
| Marketplace | A collection of your integrations that customers can browse, configure, and enable in a self-service manner. |
| Embedded Marketplace | A marketplace integrated into your application, allowing customers to configure and enable integrations without leaving your app. |
| Embedded Workflow Builder | A tool that enables customers to build their own integrations directly within your application. |
| Alert Monitor | A system for notifying your team via SMS, email, or webhook when integrations behave unexpectedly (e.g., errors occur or performance degrades). |
| Prism CLI Tool | A command-line interface for managing customers, integrations, instances, and custom components. |
| Prismatic API | A GraphQL-based API used by Prismatic's frontend and CLI tools. You can use it to create scripts for programmatically managing customers, deploying instances, and more. |