Prismatic Changelog

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.

We added some new components to our catalog in April. This past month, we added:

• Facebook Marketing - Interact with ads and ad sets in your Facebook Marketing account
• Google Ads - Manage Google Ad campaigns
• WooCommerce - Easily manage your customers, orders, and products in your WooCommerce platform

Some popular SaaS applications append URL paths to the webhooks that they're configured to use. So, given a webhook endpoint https://hooks.prismatic.io/trigger/EXAMPLE== they might send data to https://hooks.prismatic.io/trigger/EXAMPLE==/order/created.

You can now send data to webhook triggers four ways:

• Request body
• Request headers
• URL parameters
• URL path (added)

Check out our Sending data to webhook triggers article for more information.

Instance-specific endpoints (meaning all flows in an instance share one webhook URL) and shared endpoints (meaning all instances of an integration share one webhook URL) are now easier to configure, test and troubleshoot. Check out our Endpoint Configuration article for details.

Instance webhook triggers can now be invoked using the GET HTTP verb in addition to the POST verb.

Some third-party apps (notably Dropbox among others) verify that a webhook endpoint is ready to receive requests with a GET request. They then send webhook payloads with POST requests. This change was made to support the initial verification GET requests.

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

• Collection Tools - Perform common operations on collections
• Microsoft OneDrive - Interact with files and drives inside Microsoft OneDrive

If you need to add a flow that is similar to another flow you've already built, it's helpful to be able to clone (make a copy of) a flow. You can now clone an existing flow from the flow menu in the integration designer.

For more information, see our Building Integrations article.

You can now filter the integrations that you show in your embedded marketplace by category or label. This gives you the flexibility to show specific types of integrations to specific users or customers.

To get started with filtering your embedded marketplace, update your @prismatic-io/marketplace package to version 1.1.2, and add a filters attribute to your prismatic.showMarketplace() invocation - see docs for details.