The strongest part for us is the ability to treat integrations as an actual product capability rather than an assortment of one-off engineering projects. I like having a consistent framework for authentication, workflow logic, data movement, and monitoring. That gives the engineering team a clearer pattern to work from when a new integration or workflow comes along. Review collected by and hosted on G2.com.

The platform is powerful, but that also means there is some complexity to work through before a team develops a comfortable operating rhythm with it. The first few workflows require more attention to architecture and configuration than a simple point-to-point integration would. I see that more as a tradeoff for having the additional control, but it is still part of the learning curve. Review collected by and hosted on G2.com.

What I like most about Prismatic is the visual approach to building integrations. I can map out a workflow and make the logic easier to understand without having everything buried in code. For example, I’ve been working with a Salesforce-to-external-system workflow where a webhook triggers the process and branching handles different lookup conditions such as Customer ID or Customer Email. The flow is easy to follow, which makes troubleshooting and making changes much more manageable. For us, the biggest value is having a structured way to build and manage integrations. The visual workflow makes complex logic easier to understand, while branching and webhook-based triggers give us flexibility for different integration scenarios. There is some initial learning involved, but once the workflow structure becomes familiar, it is much easier to maintain and adjust. Review collected by and hosted on G2.com.

There is a little bit of a learning curve when first getting familiar with the different workflow components and configuration options. When a workflow becomes more detailed, it can also take some time to trace exactly where a particular condition or step is being handled. More guided examples for common integration scenarios would make the initial setup easier. Review collected by and hosted on G2.com.

The biggest thing for me is the ability to get into the actual integration logic instead of treating the connection as a black box. We could work through data mappings and workflow behavior in enough detail to make the integration fit our existing product and processes. Review collected by and hosted on G2.com.

We had to circle back on a few requirements during the project. Some of the details around what we wanted the integration to do needed additional clarification before everything was settled, so I would make sure the requirements and data flows are very explicit at the beginning. Review collected by and hosted on G2.com.

The biggest benefit was being able to build around our actual workflow rather than forcing our process into a generic connector. Prismatic gave us flexibility around how the systems needed to communicate and how the integration was structured. Review collected by and hosted on G2.com.

There were a few points where we had to follow up to get clarification, so communication wasn't always as quick as I would have liked. It was a relatively small issue, but when you're moving a systems project forward, waiting on an answer can slow down the next decision. Review collected by and hosted on G2.com.

The biggest benefit was being able to build around our existing systems rather than asking us to redesign the way we work. We could get specific about the data we needed and how it should move through the workflow. Review collected by and hosted on G2.com.

There was some back-and-forth at the beginning because we did not have every integration requirement defined precisely from the outset. That meant revisiting a few details before the implementation was fully clear. Review collected by and hosted on G2.com.

The main thing for me is having a purpose-built layer for the integration work instead of treating every API connection as a separate development project. That is particularly useful when you're working across marketing and advertising systems and the requirements can change. Review collected by and hosted on G2.com.

The initial requirements took a little more clarification than I expected. We had to go back over exactly what the integration needed to do before everything was clear, so I'd spend a bit more time defining the workflow upfront. Review collected by and hosted on G2.com.

The flexibility around integrations is what stands out. We could work with our existing AWS environment and focus our engineering effort on the actual integration requirements instead of repeatedly creating custom infrastructure for each connection. Review collected by and hosted on G2.com.

There was some back-and-forth at the beginning while we worked through requirements and the integration approach. We needed a few extra follow-ups before everything was clearly defined, but that became less of an issue once the project direction was established. Review collected by and hosted on G2.com.

The flexibility around APIs and data mapping was the biggest benefit for us. We could work through the actual integration requirements rather than forcing our banking data into a rigid workflow. Review collected by and hosted on G2.com.

We had some requirements that weren't completely understood at the beginning, so there was a bit of back-and-forth before the implementation matched what we actually needed. It wasn't a major issue, but getting those details nailed down earlier would have made the first part of the project easier. Review collected by and hosted on G2.com.

I liked having the integration logic organized in one place rather than scattering API-handling work throughout our application. That made it easier for us to think about the integration as its own system and make changes without unnecessarily touching unrelated product code. Review collected by and hosted on G2.com.

We had some requirements that needed clarification during the project, so there were a few extra follow-ups before everyone was working from the same interpretation. It wasn't a blocker, but I would have preferred to resolve those details earlier. Review collected by and hosted on G2.com.

I like that the integration work can be built around the actual workflow instead of treating every business like the same use case. The Salesforce connectivity gave us a practical foundation without requiring us to build every piece of the integration ourselves. Review collected by and hosted on G2.com.

We had to go back over some requirements early in the project because a few things weren't completely defined at the beginning. It wasn't a major problem, but it did create some extra back-and-forth before the implementation was fully aligned with what we wanted. Review collected by and hosted on G2.com.