Prismatic Reviews & Product Details

The support has been the standout for us. During our POC, the sandbox let us actually verify Prismatic would work for our use cases before committing — which made the decision easy. Onboarding was smooth thanks to dedicated weekly check-ins where their team answered questions and helped us clear roadblocks. Even now that we're past onboarding, we still have monthly check-ins with our account manager to stay on top of new features and make sure we're getting the most out of the platform.

Day-to-day, their Slack support is genuinely impressive. We always get timely responses, and they don't just answer the question — they share resources and ideas for how to use the system better. It feels like a partnership rather than a vendor relationship. Review collected by and hosted on G2.com.

The JSON forms are limiting for our use case where we need to transform data on a per-event basis a layer below the customer. Review collected by and hosted on G2.com.

I am a huge fan of Prismatic's skills and CLI. The code native integrations are great. I think one of the best parts about it is that I can use my cloud code to develop integrations at scale and go fast. They also have low code options, which I'm a big fan of for nontechnical people. Using cloud code and version control really speeds up the rate of integration development exponentially. The CLI is great because it allows me to iterate quickly and put things into motion very fast without spending a lot of time in iterative cycles. Setting up Prismatic was quite simple, especially compared to past experiences, as it only took us a month instead of the ten months other implementations have required. So far, my experience has been stellar. Review collected by and hosted on G2.com.

There's a little bit of a learning curve, obviously. You have to get into it. Getting everything set up, getting, Prismatic embedded was quite simple. I don't have a ton of criticism. Just having to learn a new system like that takes time as this is for any iPass system, though. Review collected by and hosted on G2.com.

The code-native SDK is the biggest win for me. Integrations are TypeScript projects I can version-control, review in PRs, test locally, and deploy through the same engineering workflows as the rest of our stack — not drag-and-drop flowcharts that drift out of sync with the code that owns the data model. That alone puts Prismatic in a different category from the low-code competitors.

A few more things I lean on heavily:

- Responsive engineering partnership. Getting direct help from their team on shared-instance endpoint derivation and ULC (user-level config) deployment patterns made a real difference. They engage like engineers, not like a support tier.

- The component/integration split. Building shared components (our router, webhook forwarders) that every integration composes onto is what made our shared-instance architecture tractable. Without that layered model we'd be copy-pasting logic across every vendor.

- The prism CLI. Being able to query execution logs from the terminal and wire it into my own tooling — I've built staging-reset and e2e-validation workflows on top of it — turns Prismatic from a black-box hosted service into something I can actually operate. Review collected by and hosted on G2.com.

Docs for multi-tenant / shared-instance patterns were relatively thin. Review collected by and hosted on G2.com.

I like Prismatic's fully embedded nature which makes it look like a seamless part of our product for our clients. Also, its extensibility from a visual builder to a code native builder is impressive. The visual builder streamlines and makes it easier for less technical users to understand and develop workflows, ensuring you don't have to code everything from scratch while still allowing for custom solutions with the code native builder. I also appreciate the new capability around the embedded workflow builder that can be extended to end users, offering tooling similar to what Prismatic provides for backend integrations, which is equally helpful for embedded workflow designing for end users and clients. Review collected by and hosted on G2.com.

It's a bit challenging to get integrations from one deployment to another. To create an integration inside one region or deployment, and get it into another region without multiple series of manual steps is a more manual than desirable effort. It's got a learning curve, and it's certainly a product you need to make sure you've got the engineering capacity to dig into and build some internal knowledge around. Review collected by and hosted on G2.com.

From a UI/UX perspective, the integration workflow builder is pretty clean. I also like the plethora of integrations offered. So far, performance on our file loads has been very acceptable.

On pricing, what works best for us is that it’s priced per instance and not per file, since we have heavy workloads. Support has been exceptional as well—they’re very responsive and we have weekly check-in calls to debug, help, and also explore.

I haven’t used their AI offerings much yet, but prismatic skill in claude seems to be helpful. Review collected by and hosted on G2.com.

I think the documentation is comprehensive overall, but it can be a little hard to find the right document when I need it.

Additionally, some parts of the UI could be improved, especially the logs dashboard. Review collected by and hosted on G2.com.

I like that Prismatic has a very intuitive interface, which makes it easy to use. The availability of plenty of built-in connectors along with the option to create custom connectors is a significant advantage. I appreciate the powerful documentation that aids in the ease of setup and use. Prismatic offers two options for building, whether you prefer a low-code or code-native approach, which is great for flexibility. The onboarding team is reactive and great to work with, which has made my experience with Prismatic even better. These features have helped us transition from customized integrations per customer to a fully scalable product. Review collected by and hosted on G2.com.

Nothing for now. Review collected by and hosted on G2.com.

- Integrations with Prismatic has been quite seamless and straight forward. The low-code/no-code ability is a life saver.

- Support from the Prismatic team as part of the onboarding and the initial journey has been quite amazing.

- The Prismatic Claude skills is a life saver. It has been one hell of a help. Review collected by and hosted on G2.com.

- Journey in finding the Secrets/Keys could probably be better. Review collected by and hosted on G2.com.

Prismatic's workflow builder is easy to use and hugely extensible. Their out of the box integrations cover a lot of use cases needed for general data transfer, and several with specific third-party solutions our clients use. But it also supports our own custom-built components, there is a way to expand the foundation and re-use integration logic with our future workflows as well. We will only see our integration velocity, and the capabilities of our integrations, improve as time goes on.

Prismatic has been available from day one to handhold us through implementation and readily answers questions every time we have them, providing links and examples to help us get our jobs done as soon as possible. Review collected by and hosted on G2.com.

Using any middleware introduces constraints that we might be able to avoid if we built in-house. With high-volume workloads, we often have to split work in ways that add overhead that might not otherwise be necessary. Synchronous workflows also come with additional volume constraints that likely wouldn’t apply if we were calling our APIs directly. To Prismatic’s credit, they make these constraints very clear and they’re making strong improvements in these areas, but some level of constraint will always be present. Review collected by and hosted on G2.com.

I love how Prismatic makes it super easy to build integrations connecting our customers' platforms with Limble CMMS. I also appreciate the AI workflows and tooling, including using Claude Code, Prismatic Claude Skills, and MCP server, which make it very easy and efficient to build out Code Native Integrations. I'm pretty happy all around with Prismatic as they are always evaluating and improving the product. Review collected by and hosted on G2.com.

CI/CD pipeline gets pretty complicated when deploying new integrations to multiple environments Review collected by and hosted on G2.com.

I like Prismatic's flexibility and the wide range of different apps it connects to. I appreciate that you can write your own connectors and integrate those with Prismatic too, which has saved us a lot of time. The support line has also been very helpful. Review collected by and hosted on G2.com.

The ease of use for the workflows could be improved. Some of our clients are resellers for our app, meaning they need to be well trained on how to build workflow automations. They are having trouble getting the hang of things. I think having more generalized actions may be a good idea. Also, the filtering on the integrations marketplace could be improved. Right now we aren't able to filter it to show specifically which integrations we need it to. Review collected by and hosted on G2.com.