Prismatic Changelog

You can now use logical operators like and, or, startsWith, notEqual and more to filter the integrations in your embedded marketplace. For example, if you would like to show all integrations that have a category "ERP" and label "paid", and would also like your Dropbox and Slack integrations to be displayed, a filter could look like:

[
  BooleanOperator.or,
  [
    BooleanOperator.and,
    [TermOperator.equal, "category", "ERP"],
    [TermOperator.in, "labels", "paid"],
  ],
  [TermOperator.equal, "name", "Dropbox"],
  [TermOperator.equal, "name", "Slack"],
];

Read more about advanced filters in the docs.

Our list of built-in components continues to grow. A full catalog is available here. This past month, we added:

• Microsoft Graph API - Interact with the Microsoft Graph API
• OpenAI - Interact with OpenAI models, including Chat GPT and DALL·E

Additionally,

• Microsoft Outlook - Added actions to interact with mailboxes, folders and email messages

We added a few additional components in February:

• Arena PLM - Interact with items and resources in Arena PLM
• Google Analytics - GA4 - Manage Google Analytics GA4 accounts and data
• HTML Utils - Helpful HTML-related functions for building HTML documents and HTML-based emails.

Our list of built-in components continues to grow. A full catalog is available here. This past month, we added:

• HTML Utils - Helpful HTML-related functions for building HTML documents and HTML-based emails
• JSON Forms - Create powerful custom forms for the configuration wizard
• Marketo - Manage Marketo records
• MessagePack - Efficiently serialize or deserialize data into a JSON-like format
• Microsoft Outlook - Read and manage Microsoft Outlook calendars
• NetSuite - Manage NetSuite records

We've integrated JSON Forms into our configuration wizard to give you more control over your users' integration configuration experience. You can build a static JSON form using the built-in JSON Forms component, or create dynamic configuration experiences by adding JSON Forms data sources to your custom components.

Not all of your customers speak English. You can now offer translations for embedded marketplace, so your customers can enable integrations in their native language.

See Embedding Marketplace for information on how to offer i18n support to your customers.

Our component team has been busy! A full catalog is available here. In October and November we added:

• GraphQL - Make GraphQL requests (queries and mutations) to a GraphQL-based API
• Microsoft Bing Ads - Manage Microsoft Bing Ad Customer Services
• Microsoft Bot Framework - Manage conversational interactions across platforms using Microsoft Bot Framework
• Microsoft Outlook - Read and manage Microsoft Outlook calendars
• Odoo - Manage records in an Odoo database
• Zoho - Manage records, users, and more in your Zoho CRM and Books apps

We're proud to introduce a new instance configuration option - User-Level Configuration (ULC).

What is ULC? ULC helps when multiple users of a single customer all need an integration. It allows you to configure a single instance of an integration for a customer, but collect configuration from multiple users and execute using user-specific configuration.

Why use ULC? ULC is handy if your integration requires user-specific config variables and credentials. For example, suppose your app needs to write data to several users' private Dropbox folders. With ULC, you can collect connection information for several users within a customer, and integrate with each of their individual Dropbox accounts.

How does ULC work? At a high level, a single instance of an integration is deployed to a customer, and is configured with some customer-wide config variables. Individual users within the customer, then, go through a ULC config wizard and supply user-specific credentials and config variables. When the instance runs, it pulls in user-specific configuration depending on some rules you set.

Read more about ULC in our docs.

You can now persist data between instances of the same integration. This is handy if your customers need to share some state, or if you need to persist a customer mapping for preprocess flows.

See the Persist Data docs, or write your own component that persists integration data

Source code for the @prismatic-io/prism CLI tool and the embedded marketplace library, @prismatic-io/marketplace, have been added to public repositories on GitHub.

prism wraps the Prismatic API and provides users a way to perform CRUD (create, read, update, delete) operations on a variety of Prismatic resources (components, integrations, instances, customers, etc.) from the command line. Having it publicly available provides a great reference for developers looking to wrap the Prismatic API themselves.

The two projects join the custom component SDK, @prismatic-io/spectral, which was already publicly available:

• @prismatic-io/prism - https://github.com/prismatic-io/prism
• @prismatic-io/marketplace - https://github.com/prismatic-io/marketplace
• @prismatic-io/spectral - https://github.com/prismatic-io/spectral
• @prismatic-io/examples - https://github.com/prismatic-io/examples