You can now create and assign instance profiles to customize resource allocations and execution constraints for specific integrations and instances. This allows you to increase memory limits for memory-intensive integrations, control step result and log retention, and enable quickstart to reduce cold start times for synchronous invocations.

You can now configure your JSON Forms config variables to reset data to defaults if inputs to the config variable change. This is useful if your JSON Form generates default data that is derived from other config variables on previous pages, and the defaults should change if the user selects different values on previous config pages. Learn about resetting JSON Forms data when inputs change.

You can now opt-in to remove the first page of the config wizard, creating a smoother activation process for your customers.

Opt-in by upgrading the embedded SDK to version 2.12.0 and setting the configurationWizard.mode to "streamlined". Read docs for more details.

This is completely optional and won't affect your existing implementations.

Your customers can now enable multiple instances of an integration through embedded marketplace. This allows your customers to set up several copies of an integration of themselves, each with different configurations.

Check out our docs for more information.

Granular config variable and connection input settings allow your org to better control who can see and set integration configurations values. Read more in docs.

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.

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.

We've overhauled the way deploy-time configuration management works, making it much more flexible and dynamic.

It's a wizard now, so you can split complex configuration pages in a way that's intuitive to your customers. Any existing configuration pages will simply become part of a one page wizard, so everything will continue to work as-is.

Read more about the configuration wizard designer on the Config Wizard docs page.

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.