From faster activation with our new config wizard update to industry trends driving success, we have some exciting updates and insights to share to keep you ahead of the curve.
Plus, hear how Cofactr boosted revenue by 50%—all without additional engineering resources.
Ready to continue optimizing your integration strategy? Let's dive in.
Spotlight
Try our config wizard update now!
We're excited to share an exciting update to our config wizard that will make your integration activation process smoother.
What's new?
You can now opt-in to remove the first page of the config wizard, making the activation process quicker and more efficient. This means less time setting up and more time building!
How to get started
- Upgrade to version 2.12.0 of our embedded SDK.
- Set configurationWizard.mode to 'streamlined'.
It's that simple! This change is completely optional and won't affect your existing implementations. Ready to give it a try?
Cofactr boosted revenue without adding engineering resources
Thanks to Prismatic, 50% of Cofactr's new revenue now comes from integration-enabled modules.
Cofactr, a leader in workflow automation, faced a significant challenge: scaling integrations without overburdening its engineering team. Each new customer required multiple integrations, which were tying up 25% of its engineering resources.
By partnering with Prismatic, Cofactr transformed its integration process, freeing up its engineering team to work on its core product.
If you want to get even more out of Prismatic, we're here to help every step of the way! Feel free to book some time with our customer success team here.
Integration resources
Integrations are your competitive edge in 2025
As you optimize your integrations with Prismatic, staying ahead of emerging trends can help you unlock even more value. Here's a quick look at key trends shaping the landscape:
- SaaS expansion – The growth of SaaS apps creates new opportunities for efficient integrations.
- Native integrations are critical – Customers expect easy, out-of-the-box integrations.
- Low-code and high-code options – Tools that empower both dev and non-dev teams.
- AI-powered integrations – AI is simplifying and speeding up integration processes.
Explore how these trends can enhance your integration strategy.
Pro tips to keep your integrations on track
Even with a solid integration strategy, unexpected roadblocks can still pop up. Our CEO, Michael Zuercher, recently shared insights in SD Times on how teams can stay proactive and keep integrations running smoothly.
What you need to know:
- Tackle it in phases – Break integrations down to keep them on track.
- Plan ahead – Define requirements early to avoid last-minute pivots.
- Think long-term – Scalability and support are just as important as the launch.
You've already built a strong foundation—what's the next step in optimizing your process? This article explores how a phased approach and proactive planning can help you avoid surprises.
How generative AI is accelerating app development and what it means for you
Generative AI is changing the game for app development, allowing teams to innovate faster and more efficiently. By automating repetitive tasks, AI helps reduce development time, enabling companies to deliver scalable, adaptable solutions.
With AI, decision-making becomes more data-driven, allowing teams to stay ahead of the curve and meet the growing demands of the industry. It's no longer just about building apps—it's about building smarter, faster, and more efficient solutions.
Want to see how this plays out in real-time? Watch the full interview with VP of Engineering Tanner Burson.
Product news
How to get the most out of cross-flow triggers
We previously launched cross-flow triggers, which enable flow-to-flow communication within Prismatic. You can now directly reference and call other flows within the same integration, making it easier to build integrations that need to coordinate across multiple flows.
Here are a few reasons to consider adopting cross-flow triggers in your integration design:
1. Execution traceability
Cross-flows automatically create execution lineage, linking calling and invoked flows within Prismatic. This built-in traceability allows you to quickly see which flow triggered another, view linked executions, and debug failures without extra logging. In contrast, HTTP requests lack this feature and require manual tracking to understand flow dependencies.
2. Synchronous vs asynchronous execution
Cross-flows support both synchronous and asynchronous execution modes, giving you flexibility in how the calling flow behaves. You can choose whether the calling flow waits for a response or continues processing immediately—all from within the component's input window. With standard HTTP requests, handling asynchronous behavior requires additional configuration.
3. Native error handling and retries
Prismatic automatically handles errors, retries failures, and tracks execution status using cross-flows. With HTTP requests, you would need to implement your error handling, retry logic, and logging to achieve the same level of reliability.
4. Simplifying parallel data processing
Cross-flows are perfect for parallel data processing. By breaking large tasks into smaller, independently executed flows, you can:
- Distribute workloads across multiple cross-flow executions.
- Boost performance by running tasks concurrently.
- Maintain traceability while keeping logic modular and reusable.
To learn more about parallel processing strategies, check out our guide to Processing Data in Parallel.
5. Flexibility for both low-code and code-native integrations
Whether you prefer using the drag-and-drop UI or writing TypeScript, Prismatic allows you to invoke flows in the way that best fits your workflow. For code-native integrations, you can use the context.invokeFlow function, which the cross-flow component wraps in your code.
For more details on using cross-flow triggers in code-native integrations, visit our documentation and example code.
When to use HTTP requests instead
You may still prefer to use the HTTP component in the following cases:
- Calling external APIs outside of Prismatic.
- Implementing custom authentication methods that cross-flows don't currently support.
- Sending requests with specific headers or formats that cross-flows can't accommodate.
Continued support for HTTP requests
Invoking sibling flows using the HTTP component remains fully supported. Cross-flow triggers extend this functionality, making it easier to manage flow-to-flow communication natively within Prismatic.
Connector updates
We have updated our built-in Shopify connector to use Shopify's GraphQL API. These changes are in response to Shopify's deprecation of its REST API endpoints. Public apps that rely on their REST API must be updated this month, and custom apps must be updated by April 2025.
We updated most of the actions in a backward-compatible way. For these actions, you'll just need to update the Shopify component's version to the latest, and they'll continue to work as before. No further action will be needed.
But for a couple actions, the GraphQL API was different enough from the REST API that we had to deprecate the old action in favor of a new action that accepts differently formatted inputs and yields a differently formatted result.
If you use either of these actions, please replace them with their updated (same-named) counterparts:
- Get Order
- List Orders
Additionally, if you use the Raw Request action, you must update those steps to use the GraphQL Raw Request action to query for the same information instead.
Want expert assistance on these new connectors or your next integration? Schedule a build session with the Prismatic team. We'd love to help!
What do you love about Prismatic?
Your insights are valuable! Not only do we love to hear your feedback, but we know other SaaS companies do, too.
Ready to share your insights? Just leave a review on G2. You can find directions here.
We appreciate your support!