Prismatic Reviews & Product Details

The pre-built connectors were the biggest advantage for us. We didn't have to treat the integration like a completely custom development project, and the team could take care of much of the implementation work. Review collected by and hosted on G2.com.

At a few points I had to follow up to find out where things stood. The work itself moved forward, but having more proactive updates during those gaps would have made the project easier to track. Review collected by and hosted on G2.com.

The useful part was being able to focus on the actual workflow rather than trying to make our team work around disconnected systems. The completed automation gives us a clearer path for operational information to reach the accounting side. Review collected by and hosted on G2.com.

There was some back-and-forth early in the project while we clarified exactly how certain requirements should work. It wasn't a major issue, but we did have to revisit some details before everything was settled. Review collected by and hosted on G2.com.

The useful part was being able to work through the actual integration requirements rather than getting a generic solution. The team also helped address the API details that mattered to our particular workflow. Review collected by and hosted on G2.com.

We had some requirement clarification to work through at the beginning. A few things needed extra discussion before everyone was working from the same understanding, although that became less of an issue as the project progressed. Review collected by and hosted on G2.com.

The connector approach is the part I find most useful. Instead of treating every integration as a completely new development project, we have a starting point for connecting the systems involved in a marketing workflow. Review collected by and hosted on G2.com.

Some of the requirements needed extra clarification before we could settle on the right implementation. I would have liked a little less back-and-forth at that stage, particularly when the integration requirements were changing between systems. Review collected by and hosted on G2.com.

The flexibility around the integration was the useful part for us. We could focus on how our accounting workflow actually works instead of trying to force the process into a fixed connector. Review collected by and hosted on G2.com.

We had some back-and-forth at the beginning while we clarified exactly what we wanted the integration to do. A few requirements needed additional follow-up before everything was completely clear. Review collected by and hosted on G2.com.

The pre-built connector approach was the biggest benefit for us. We could focus on what information our marketing workflow needed rather than starting an integration completely from scratch. Review collected by and hosted on G2.com.

We had to go back and forth a few times at the beginning to clarify exactly which data points and fields we wanted. It wasn't a major problem, but getting those requirements settled took some extra follow-up. Review collected by and hosted on G2.com.

The biggest benefit was having the integration work organized in one place rather than stitching together separate pieces of infrastructure for every connection. It was useful for a project where data needs to move between transportation systems, APIs, and Microsoft Azure. Review collected by and hosted on G2.com.

We had some requirement clarification to work through early in the project. A few integration details needed extra follow-up before everyone was working from the same interpretation. Review collected by and hosted on G2.com.

The useful part is being able to treat synchronization as an integration workflow rather than a collection of manual data tasks. The Marketo capabilities also cover practical operations such as creating, updating, and upserting records. Review collected by and hosted on G2.com.

Some requirements needed additional follow-up before they were completely clear. With integrations, the details around fields, matching, and how records should behave can take a little back-and-forth to nail down. Review collected by and hosted on G2.com.

Prismatic gives us a more organized way to handle application integrations as our retail operations grow. I like having the integration work in one environment instead of managing separate processes for every connection. Review collected by and hosted on G2.com.

There is a bit of a learning curve when first getting familiar with the platform. Some of the setup can take a little time to understand, especially when you're working through a new integration for the first time. Review collected by and hosted on G2.com.

I like how Prismatic lets us handle several integration needs through one platform, connecting with different applications without relying on a collection of separate tools. I value the flexibility around APIs and the ability to work with data as part of the integration process. This flexibility gives our team more options when direct connections aren't enough, allowing us to manage how information is transferred and processed. Having everything organized within the same integration environment makes our day-to-day work much simpler. Additionally, the initial setup of Prismatic was very easy. Review collected by and hosted on G2.com.

I find it challenging to set up and manage advanced integration tasks. When it involves several systems or more complex data handling, it can take extra time to get everything configured the way we want. A more streamlined setup and guidance for those situations would be appreciated. Review collected by and hosted on G2.com.