If there's one lesson we've learned, it is that B2B SaaS companies don't all look alike when it comes to integration development needs. Some have extensive dev teams for building integrations, and others use non-devs for integrations. Still others have a mix.
Given that, our goal for 2024 was to continue improving Prismatic into a platform powerful and versatile enough to give devs and non-devs alike an exceptional experience for building, deploying, and managing B2B SaaS integrations.
To do this, we focused on creating tools that enable SaaS integration teams to handle any number of integration scenarios with ease.
Here are the most impactful updates to Prismatic for 2024.
Code-native integrations
Video available here.
We introduced code-native integrations to ensure that Prismatic meets devs where they are rather than introducing another tool they need to learn. We've provided a powerful SDK that lets you incorporate coding integrations into your current workflow.
You can use your favorite IDE, bring in any npm packages they want to use, call actions in pre-built connectors, and otherwise take advantage of the Prismatic infrastructure without compromising your ability to deliver customer integrations exactly how they need to.
Build entire integrations in TypeScript from scratch or leverage existing integration functionality to make the most of what others have already written. Either way, the only limits you have are the ones you set.
On-prem agent
Video available here.
While much new software development focuses on SaaS, myriad apps will never be in the cloud. That's why we introduced our on-prem agent.
The on-prem agent enables you to build integrations with non-Internet-connected local apps and other data sources that used to be, if not unreachable, at least difficult to integrate with SaaS apps securely.
Now, if your customers are managing sensitive data locally or have several legacy systems that are still providing value, you can use the on-prem agent to help them integrate those systems with your app using either pre-built or custom connectors.
Org-activated connections
Video available here.
We introduced org-activated connections to make it easier for you and your team to create and manage customer connections when configuring an integration instance.
Org-activated connections let you streamline your customer UX by automatically handling auth with your product, removing the need to re-ask for credentials they've already provided.
You can manage these connections and corresponding configs through the UI or programmatically via our CLI.
Use org-activated connections to bulletproof your integration setup by hiding/removing unnecessary connection steps from customers while ensuring secure authentication.
Polling triggers
While webhook triggers react to an event when it occurs, we added polling triggers to react to events shortly after they happen within systems that don't have webhook capabilities.
These triggers poll an API according to a defined interval and ask if there's anything new. If the API has no new data, the trigger sleeps until the next time it polls. If the API has new data, the trigger runs and starts the integration.
In addition to building polling triggers into several of our connectors, you can also create custom polling triggers for other apps that don't have webhooks.
While you could previously work around the real-time update limitations of systems without webhooks, this new functionality makes the process straightforward.
GitHub actions
Video available here.
We introduced GitHub actions to enable you to incorporate Prismatic and the code you build on it directly into your existing SDLC, keeping to the tools and processes you and your team already know.
You can now automate the process of publishing integrations and components you've tested in your dev tenant to production.
At the same time, you have access to all the source control metadata directly within Prismatic.
And, while we built these actions specifically for GitHub, you can implement this functionality with just about any source control system using our Prism CLI.
Cross-flow calling
It's not uncommon for multi-flow integrations to have complex configurations. But that's where cross-flow calling (and the triggers it enables) can provide value, allowing you to quickly break down and connect flows while maintaining visibility into how they work together.
Cross-flow calling is beneficial in scenarios where you need to:
- Perform parallel processing for large datasets
- Organize large or complex integrations into simpler chunks
- Create reusable logic to be referenced by multiple flows
With cross-flow calling, we took something our customers were already doing and greatly simplified it, saving time and reducing frustration.
What’s next?
In 2025, we will continue to push our platform's evolution by focusing on how we can help you, your team, and your customers build integrations in less time and with fewer resources.
To do this, we’ll keep the simple things simple, make the difficult easy, and abstract the complexity that comes between you and the integrations you need to build.
We wouldn't be here at the end of 2024, looking back at what we've accomplished without the continued feedback and support of our customers. Here's to a fantastic 2025 working side-by-side with you as we develop our market-leading platform to continue delighting devs and non-devs alike!
