Patchworks Reviews & Product Details

We use Patchworks as the integration layer connecting Shopify and BigCommerce to HubSpot, keeping product and customer data in sync across all three. The biggest upside is not having to build and maintain those connections ourselves — the pre-built connectors handle the heavy lifting, and data stays consistent between our storefronts and CRM without manual exports. Setup was more straightforward than a custom-built pipeline, and it's held up reliably for our day-to-day data management. Review collected by and hosted on G2.com.

The main limitation we've run into is around custom field mapping — when our data model doesn't line up cleanly with the pre-built connector structure, configuring the exceptions takes more trial and error than expected. Error reporting could also be clearer; when a sync fails it isn't always obvious which record or field caused it, so troubleshooting takes longer than it should. Pricing scales up as volume grows, which is worth factoring in for larger catalogs. Review collected by and hosted on G2.com.

What I like best about Patchworks is the combination of its integrations, user experience, support, and pricing. The platform makes it easy to build and manage integrations, and we've been able to get our connectors into a strong, stable working condition.

The documentation and Patchworks University are excellent resources, making it easy to learn the platform and find answers when needed. The support team has also been fantastic, particularly Jon, who has provided insightful guidance and helped us along the way.

From a UI/UX perspective, the platform is intuitive and easy to navigate. The AI tool is especially useful for finding documentation quickly and understanding workflows. I also appreciate the debugging capabilities, which make troubleshooting and resolving issues straightforward.

Performance has been reliable, and I haven't experienced any significant issues. Finally, Patchworks offers very competitive pricing compared to other integration platforms, and having access to quality support without excessive additional costs provides excellent value for money. Review collected by and hosted on G2.com.

One area I'd like to see improved is the AI implementation agent. In my experience, it hasn't consistently delivered the expected results. I've had several sessions where the AI indicated that implementation changes had been completed, but the changes were not actually applied. This often meant having to spend additional time validating the outcome or finding an alternative solution.

While the AI documentation and workflow navigation features are useful, I would like to see improvements in the reliability and accuracy of the implementation agent so that it can be used with greater confidence for development and configuration tasks. Review collected by and hosted on G2.com.

The user interface is really good. It is easy to identify most of the shapes and what they do just by their naming convention. Although I haven't used the AI assistant as much but so far it has helped me with my process flow. Review collected by and hosted on G2.com.

This might be based on personal preferences really but I don't really enjoy the concept of scripts and code in a user friendly UI. I wish things could be done directly in the flow using shapes and low code logic rather than using scripts. But I also understand the need of using them to cater different scenarios. I also wish there was an undo/redo button on the UI, which currently is a pain if you change something significant and want to quickly revert back. Review collected by and hosted on G2.com.

The ease of setting up integrations is what stands out most for me. It’s fairly straightforward to get started if you have a technical background, and once you understand the basics, you can set up pretty much any integration you need. It’s also worth mentioning that the Support team is especially helpful—I typically hear back on support queries about the integrations I’m building within a few hours. Review collected by and hosted on G2.com.

While using scripts can make it easier to build integrations at times, it can also create an overdependence on scripts. That said, this may be because I’m still a fairly new user of the solution, and I’ll likely learn better alternatives as I gain more experience. Review collected by and hosted on G2.com.

-Expansive library of pre built connectors

-Ease of use

- Flexible integrations triggerable by schedules or webhooks for rapid synchronisation.

- Excellent error logging and run logs

- MCP connector and APIs allow rapid building with any AI model you prefer

- The training courses on Patchworks are clear and well thought out. The videos and text are genuinely useful and it contains the information within the docs itself rather than referring you to its docs. It does provide links to docs, but they are relevant, clean and easy to understand.

- High uptime, never experienced any failures of a task run due to downtime Review collected by and hosted on G2.com.

The built-in AI model wasn’t very useful for me. Using the MCP performed much better in my testing, though that may be because I was using a stronger model.

Some shape settings aren’t clear about what they do. A few times I turned a setting off and it broke my flow without any obvious reason. For example, on a route shape checking whether a field was yes or no, setting “Keep matching?” to off stopped it working, but it works with it on.

Debugging failed map shapes is difficult. When one failed, I couldn’t easily tell which transform was responsible, so I had to duplicate the shape and test each transform individually. It turned out to be a cache lookup failing, but that wasn’t obvious at first.

I love being able to test a payload on scripts and wish shapes had something similar, specifically for testing syntax like [[payload.*.0.test]]. Even better would be a pasted sample payload that highlights which fields are affected as you type syntax like *.0. This would have helped a lot with a connector that had no mapping documentation.

I’m also not a fan of how API requests aren’t visible in the run logs for past runs unless the step fails and you’ve explicitly logged it. You can see request headers and responses during a manual run, but not afterwards.

Finally, I wish connectors had a built-in way to handle APIs that return a successful response but include errors in the body. At the moment I have to write a script or add extra shapes to catch this. It would be useful to set an errors path and expect it to be empty, for example checking that Shopify’s errors array is empty. Review collected by and hosted on G2.com.

I like how easy it is to connect different platforms using the pre-built connectors. The visual workflows make it easier to see how data moves between systems, and I like that you can make changes to integrations without having to build everything from scratch. The support team is also helpful whenever you run into an issue Review collected by and hosted on G2.com.

Some parts of the platform can take time to understand, especially when setting up more complex integrations. The error logs could also provide more details to make troubleshooting easier. It would be helpful to have more configuration options available directly in the interface without needing developer support Review collected by and hosted on G2.com.

I love the service and the relationship we have with our partner manager, Dave, who is fantastic. Patchworks gives my clients a solution that keeps them happy and is more cost-effective than custom integrations, with the cost spread monthly. I appreciate the number of pre-built integrations and how easy Patchworks is to use with Shopify. My customers really love how easy it is to use once it’s integrated. Our custom builds can also connect with Patchworks, which helps us provide excellent service to customers. It lets us connect our own solution to Patchworks rather than build four or five separate integrations for a client. The documentation and support from the Patchworks team were good, and they helped us build our first client integration smoothly and supported us when the client added scope. Review collected by and hosted on G2.com.

Honestly, everything works really well. The more integrations you have, the better. I’d welcome further integrations with ERPs, product information systems, and finance systems like Sage Zero. There are probably a few exceptions where a custom integration might do things better, but they’ll be slim. Review collected by and hosted on G2.com.

I like its block building style and the ease of building integrations - the interface is really nice and helps me to clearly see each stage of the flow. Whenever I have had issues or questions they have always been dealt with quickly and respectfully. The performance of the service seems solid and rarely breaks. Review collected by and hosted on G2.com.

Sometimes there is a lot of clicking around to lots of different pages and usually I have to have several tabs open when building the various parts of the flow. When I want to select multiple shapes at once in a flow it can be painful when there are a lot to select - would be useful to have a 'select from here' option similar to the 'copy from here' option. Due to some of the rapid growth of the service and new features some of the documentation doesn't have up to date information. Review collected by and hosted on G2.com.

I use Patchworks as an integration layer to connect clients’ e-commerce platforms with their ERP, CRM, and other systems, which removes manual data wrangling and brittle point-to-point connections. I like the visibility: when a sync fails, I can see exactly where it stopped and replay it instead of guessing where or what went wrong. The dashboard and sync logs stand out, the pre-built connectors are lifesavers, and the field mapping and data transformation tools are useful in a lot of use cases. After the learning phase, adapting to Patchworks was smooth, and it was a good fit for my team. Review collected by and hosted on G2.com.

The learning curve is real at the start, and getting comfortable with the flows and tools takes some time and effort. Pricing can also be a consideration when scoping small-scope and small-client projects, especially when pitching Patchworks as part of the overall solution. Review collected by and hosted on G2.com.

I find Patchworks easy to use and flexible. The visual process flows make it easy to see the journey the data takes, set things up, and duplicate flows across brands. I can connect platforms through APIs, add endpoints, and customize flows to fit my business logic and rules without needing to know much code or be a developer. I can also make and deploy changes myself, quickly. I appreciate the support, account managers, and constant updates. It works, has very low downtime, and keeps getting better over time. Setup was straightforward, and the academy explaining how to use each part was very helpful. Review collected by and hosted on G2.com.

The logs for historic flow runs could be more detailed. Review collected by and hosted on G2.com.