Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Excellent Integration Solution as a Service Provider
What do you like best about the product?
Tray.io makes it much easier to create, deploy, and manage multiple different integrations of various complexities. They have a fantastic staff when it comes to support and guidance on maximizing the use of the product.
What do you dislike about the product?
It is important to note that Tray.io is not for the typical integration owner. It does require advanced knowledge and training when it comes to creating integrations, especially highly complex ones.
What problems is the product solving and how is that benefiting you?
We are expediting the delivery of integrations and creating a more comprehensive scope of what data is synced between different environments. If you have a limited staff when it comes to supporting integrations, I highly recommend giving this solution a try. In addition, the number of prebuilt connectors makes choosing the correct solution more apparent.
Recommendations to others considering the product:
Leverage Tray.io's support and account management team for advice and guidance when using the product. They are knowledgeable, helpful, and responsive.
- Leave a Comment |
- Mark review as helpful
Solid, easy-to-use automation tool
What do you like best about the product?
The Tray.io user interface is intuitive. I love the concreteness of the visualization. There's an extensive library of connectors, and within a workflow, it's easy to move connectors around, and it's also easy to connect connectors to each other -- I appreciate the snake connector for JSON paths.
Currently, our organization is using Tray more as an ELT tool than as a way to e.g. automate cross-departmental business workflows. Though this has worked okay for us, it doesn't really seem like the intended use case, and it's too expensive (and a little unwieldy) for that purpose. It's in the other cases -- triggering some business action to happen after some other business action happens -- that Tray really shines.
Currently, our organization is using Tray more as an ELT tool than as a way to e.g. automate cross-departmental business workflows. Though this has worked okay for us, it doesn't really seem like the intended use case, and it's too expensive (and a little unwieldy) for that purpose. It's in the other cases -- triggering some business action to happen after some other business action happens -- that Tray really shines.
What do you dislike about the product?
Rarely there will be a few hours when Tray just isn't working right -- things won't run. Troubleshooting versioning issues has often been bizarrely tricky. Additionally, Tray is a pain for working with workflows that have complicated logic, when the workflow structure branches out too wide and it's hard to navigate.
What problems is the product solving and how is that benefiting you?
ETL -- getting e-commerce data from Shopify and Amazon and putting it into a cloud storage warehouse -- has been our main use case. Tray helped get our Data team up and running without needing help from a developer. (The Data team now also uses it for audits.)
Powerful automation tool
What do you like best about the product?
Tray.io has a drag and drop interface that allows non-engineers (like myself) to do really cool things with APIs. Once I got over the learning curve, it's an intuitive and powerful system. Plus, the support engineers are insanely patient and knowledgable!
What do you dislike about the product?
Occasionally bugs make it hard to know if I'm doing something wrong, or if the system is showing me incorrect information.
What problems is the product solving and how is that benefiting you?
We are trying to help our customers get more out of our API, many of whom do not have development resources themselves. Many more customers are able to send data back and forth now that Tray.io is powering their data flows.
Excellent iPaaS platform
What do you like best about the product?
Easy to use, visual programming platform for intricate, involved integrations. Easy to use, visual programming platform for intricate, involved integrations. Easy to use, visual programming platform for intricate, involved integrations
What do you dislike about the product?
Onboarding process takes time - but overall great experience. Onboarding process takes time - but overall great experience. Onboarding process takes time - but overall great experience
What problems is the product solving and how is that benefiting you?
We are taking data collected by our platform and syncing with other systems of record. Benefits include enterprise-grade platform and security and scalability. Also very agile in terms of connector development and deployment
Recommendations to others considering the product:
Great platform worth a shot
Tray.io review
What do you like best about the product?
It's a suitable tool for simple workflows and easy integrations.
What do you dislike about the product?
- It lacks the creation of separate environments and promotion of changes.
- When idle, it continues to make a lot of network requests, and I think this consumes a lot of resources when working on multiple tabs.
- Sometimes there are conflicts when different users try to edit the same workflow, and the warning is not very informative.
- The interface to check the logs sometimes is very slow. The navigation inside the workflows is ok but not enough with large workflows. The new builder is faster, but there is a lot of unused space between connectors; this is not comfortable working with large workflows.
- I usually have to export the JSON for different versions because It also lacks proper control versioning.
- Some connectors have a manual error handling configuration, but it doesn't work at all, only for a specific connector (HTTP); then why is it available for other connectors (callable, script) where this is not supported?
- The edition of input schemas for callable workflows doesn't work well because the edition of an existing schema is almost always restricted; As a workaround, I have to download the JSON, make the changes manually and upload them again.
- Some connectors struggle to work well depending on the version; this is not desirable for production workflows which are not very open to modifications, I don't really wan't to be checking if a connector have the proper or latest version to be sure it will work ok.
- There is not a way to organize workflow with related purposes, tags are not enough, a folder structure is not available either.
- It's difficult to trace how workflows are linked to other callable workflows. This kind of maps have to be build externally
- When idle, it continues to make a lot of network requests, and I think this consumes a lot of resources when working on multiple tabs.
- Sometimes there are conflicts when different users try to edit the same workflow, and the warning is not very informative.
- The interface to check the logs sometimes is very slow. The navigation inside the workflows is ok but not enough with large workflows. The new builder is faster, but there is a lot of unused space between connectors; this is not comfortable working with large workflows.
- I usually have to export the JSON for different versions because It also lacks proper control versioning.
- Some connectors have a manual error handling configuration, but it doesn't work at all, only for a specific connector (HTTP); then why is it available for other connectors (callable, script) where this is not supported?
- The edition of input schemas for callable workflows doesn't work well because the edition of an existing schema is almost always restricted; As a workaround, I have to download the JSON, make the changes manually and upload them again.
- Some connectors struggle to work well depending on the version; this is not desirable for production workflows which are not very open to modifications, I don't really wan't to be checking if a connector have the proper or latest version to be sure it will work ok.
- There is not a way to organize workflow with related purposes, tags are not enough, a folder structure is not available either.
- It's difficult to trace how workflows are linked to other callable workflows. This kind of maps have to be build externally
What problems is the product solving and how is that benefiting you?
Integrations with different partners and tools. Debugging is easy. There are a lot of connector for multiple purposes.
Flexible integration tool with fantastic support
What do you like best about the product?
The hands-on support walking through integration requirements and supplied documentation is the best I've seen. The tool itself is great and can branch with conditions as needed. Not sure I've seen anything it can't do.
What do you dislike about the product?
It requires some studying up and technical ability to learn. Not as complex as MuleSoft, but as it is more flexible than a tool like Zapier, it is more complicated to learn.
What problems is the product solving and how is that benefiting you?
Data transport from our business to Partners, data conversion, error handling.
Tray Review
What do you like best about the product?
The people we worked with were very helpful
What do you dislike about the product?
Our needs were not quite a match with what tray can do
What problems is the product solving and how is that benefiting you?
We were trying for automation of our POs and order entry. Our POs can be read and downloaded into a spreadsheet to be copy and pasted.
Tray gets the job done
What do you like best about the product?
I love that Tray connects to just about everything. If you have an application with an API, it's likely tray can link to it.
What do you dislike about the product?
Tray does go down relatively often, in comparison to other applications my company uses. And the fixes are not always super fast.
What problems is the product solving and how is that benefiting you?
We are trying to solve the problem of connecting multiple applications across multiple domains. Tray allows us to centralize some workflows
Tray helps us automate tickets!
What do you like best about the product?
I love that tray connects to all of our 60+ zendesk instances to help us automate ticket flow
What do you dislike about the product?
can be a bit slow at times and does go down occationally
What problems is the product solving and how is that benefiting you?
we have WAY more systems than we can manually manage. Tray helps us move and change data in all of our systems with very little custom code
Reveneer
What do you like best about the product?
The people who work at Tray are the best part of the team. The product is great but it has bugs and flaws. Those would 100% be problematic if they lasted more than a few moments. The people at Tray, Karyna Yehorova, and Conor Kogler are the best of the best; make it what it is. Any tool can do ETL, but not every company has the service and dedication Tray does.
What do you dislike about the product?
Not too much about the tool has faults. The product is fantastic and constantly delivers what I need. I would say the only downside is the debugger is kind of slow.
What problems is the product solving and how is that benefiting you?
We needed to connect various sources of data into 1 central record of truth
showing 61 - 70