Prismatic Changelog

This month we added a new utility component for zipping and unzipping files:

• Zip - Provides utility methods for working with zip files

You can now access additional information about the currently running execution from your custom component including:

• The name and ID of the running instance
• The name, ID and external ID of the customer the instance is deployed to
• Webhook URLs for all flows of the running instance

This is handy if you need to know information about the current run context, or if you're building actions that configure or delete webhooks in a third-party app. To access new context properties, update your custom component's @prismatic-io/spectral version 6.6.0.

Read more about the expanded context parameter.

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

• GitHub - Manage users, repositories, licenses, and more on GitHub
• Hash - Compute hashes of strings using common hash functions
• Pipedrive - Manage leads, companies, activities, and more on the Pipedrive platform
• Rippling - Rippling makes it easy to manage your company's Payroll, Benefits, HR, and IT - all in one, modern platform

You now have more control over the UI elements that appear to your customers in your embedded marketplace. If you would like to hide the Back to Marketplace link, or the Test, Executions, Logs, or Monitors tabs on an instance configuration screen you can!

Bump your @prismatic-io/marketplace version to 3.1.0, and add a screenConfiguration code block to your marketplace.

We have five new components this month (including a component to Prismatic itself - how meta!).

• IMAP - Fetch and manage email via IMAP
• Intercom - Manage companies, contacts and tags on the Intercom platform
• Microsoft Sharepoint - Interact with sites, drives, and items within Microsoft Sharepoint
• Pretty Good Privacy (PGP) - Create and translate encrypted messages
• Prismatic - Interact with the Prismatic API to manage customers, integrations, instances, etc.

A full catalog is available here.

We've made several improvements to the custom component development experience. To highlight a few:

• You can now clean your reusable inputs, which helps ensure type safety and catches problems with inputs before they reach the perform function.
• You can now add a global error handler to your component, which helps you capture and display more informative errors if they're thrown.
• The improved testing harness gives you more flexibility when unit testing your actions and triggers.
• The prism CLI tool can now fetch existing integration connections (including OAuth 2.0 access tokens) and store them in environment variables, so you can use them for unit testing.

Update to the latest @prismatic-io/spectral 6.x version to take advantage of these new features!

You can now store and load across flows of an instance. One flow can save state, and another flow can load that saved state.

Check out our Persist Data for documentation on the new "Cross Flow" actions, and see our docs to build state storage into your custom components.

Sometimes a step in an integration throws an error. This can be caused by a variety of external factors - temporary network connectivity issues, brief third-party API outages, etc.

You can now configure how the integration runner handles errors on each step. You can choose to stop the instance execution (that's the current default behavior), you can ignore the error and continue the run, or you can choose to wait and retry the step at a later time.

Read more in our docs.

A new management trigger - Instance Remove has been added to the Management Triggers component. Flows that use the instance remove trigger are run when an instance is deleted.

This new trigger is handy for cleaning up configuration created by the integration. For example, you can remove webhook configuration in third-party apps, or update our own API so your team knows that a customer removed an integration.

You can now set values for configuration variables from your app within your embedded marketplace. This is helpful if you know some information about your customer (their API key, a special endpoint they use, data mapping configuration, etc), and would like to set a config variable value so they don't need to.

Read more about Dynamically Setting Config Variables in Marketplace in our docs.