-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.