You can now reference existing components' actions in a code-native integration's flow. This allows you to leverage Prismatic's existing component library while working in your favorite IDE with TypeScript and other tools you love.

Read more about invoking actions in code-native in our docs.

You can now reference triggers, connections, and data sources of existing components when building code-native integrations. Both public and private components can be used in your code-native integrations. By leveraging an existing component, you can save time and effort by reusing existing functionality.

To reference existing components you will need to upgrade to Prism 6.0.0 and Spectral 8.1.0. Prism 6.0.0 requires Node 18 or higher. For those of you that have already started building code-native integrations, note that type definitions now use strings rather than enums to minimize the number of imports required.

Check out the code-native documentation and the video below to learn more.

We've introduced a new option for building integrations called code-native! This is the perfect building experience for integration builders who prefer to write code rather than use a low-code designer.

Code-native highlights:

• Build integrations completely within your IDE rather than in the low-code designer.
• Define triggers, connections, integration logic, and the customer-facing configuration experience all in code.
• Define integration logic however you see fit rather than leveraging predefined logic steps.
• More easily incorporate integrations into your existing CI/CD process and code repositories.

Check out this blog post as well as the video below for more information about the benefits of code-native integrations. Our code-native documentation is an excellent place to start when you're ready to start building your first code-native integration.