External reviews
158 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Tray is a powerful tool that makes building and maintaining integrations much more accessible.
What do you like best about the product?
The awesome thing about Tray is its great drag and drop interface; it makes it very easy to visualize and build logic for integrations using their prebuilt connectors: all relying on the infrastructure they've built out. It's very powerful as it also has the ability to create custom HTTP calls to API's and when you want to more complex data manipulation the ability to interject JavaScript/Python is nice. The prebuilt connectors provide a strong base while the ability to customize makes it very flexible and robust. The UI is also beautiful which makes it enjoyable to work in. Their embedded solution is also invaluable with being able to scale and have customers use solutions we build.
What do you dislike about the product?
It would be nice if you could comment out/skip specific steps when working on a workflow; the ability to import JS libraries would also be nice.
What problems is the product solving and how is that benefiting you?
We're able to build integrations with a lean team: both custom integrations for individual clients and solutions that can be used by many clients.
Tray is extremely well positioned and suitable for simple connections.
What do you like best about the product?
Oauth is extremely easy to setup and that's half the battle. In addition, there are so many connectors to pick up from.
What do you dislike about the product?
1. Debugging in lower environments is difficult, if not impossible.
2. Integration with source code management tools (for custom JS)
3. reusability of the custom JS across different integrations via library
2. Integration with source code management tools (for custom JS)
3. reusability of the custom JS across different integrations via library
What problems is the product solving and how is that benefiting you?
We are integrating our services with other third party services to allow our customers to automate their workflows. We have connected many different verticals using Tray connectors.
Great experience but not for every use case.
What do you like best about the product?
- Easily graphically integrate third-party APIs.
- Quick and easy to use tools to create the workflows, easy copy pasting.
- The logging is really helpful and easy to use.
- Connectors for doing notifications, quick to setup.
- You have connectors for almost anything you'll need.
- Quick and easy to use tools to create the workflows, easy copy pasting.
- The logging is really helpful and easy to use.
- Connectors for doing notifications, quick to setup.
- You have connectors for almost anything you'll need.
What do you dislike about the product?
- Logging: As I mention I really like the logging, but the interface is slow sometimes, the filters in place aren't always helpful, take ages to scroll to reach a top connector. Also the only storing the last 30 days it's a problem too.
- Viewing the workflow gets cumbersome when you have many connectors.
- Random "Something went wrong errors" appearing that aren't clear and you could still use the system without problems.
- Same with losing changes when a colleague opens the same workflow and getting wrong ownership/current editor conflicts.
- Not having a easy way to see if a workflow is called by another one, so having many members in the team is hard to do some cleanup, refactors without risks of breaking something.
- Weird random errors when importing a new workflow from a Json. It works randomly.
- If you want to edit the case of the name of a workflow you have to rename it and then go back to the right name.
- Weird issues with versions of the connectors but hard to debug why that is the problem.
- The Dropbox connector only works with the old Dropbox API version that's is deprecated, took me ages to debug that.
- Viewing the workflow gets cumbersome when you have many connectors.
- Random "Something went wrong errors" appearing that aren't clear and you could still use the system without problems.
- Same with losing changes when a colleague opens the same workflow and getting wrong ownership/current editor conflicts.
- Not having a easy way to see if a workflow is called by another one, so having many members in the team is hard to do some cleanup, refactors without risks of breaking something.
- Weird random errors when importing a new workflow from a Json. It works randomly.
- If you want to edit the case of the name of a workflow you have to rename it and then go back to the right name.
- Weird issues with versions of the connectors but hard to debug why that is the problem.
- The Dropbox connector only works with the old Dropbox API version that's is deprecated, took me ages to debug that.
What problems is the product solving and how is that benefiting you?
Integrations with 3rd party tools and apps from clients mostly. Quickness in integrations thanks to the variety of ready to use connectors.
Recommendations to others considering the product:
It's a great tool that could get a bit better in some spots.
Great tool! Very easy to use and has integrations with many other tools
What do you like best about the product?
Integration with Salesforce and BigQuery
What do you dislike about the product?
The tool is a bit slow, and for the first use it's not so clear
What problems is the product solving and how is that benefiting you?
The connection between Salesforce and BigQuery via Tray.io
Great product, helped me a lot in my automation projects. Cut my time to less than half.
What do you like best about the product?
Customer support is excellent. They are very supportive and schedule a time to pair with you when you need them.
What do you dislike about the product?
Sometimes I have to push the run workflow button more than once to get it running.
What problems is the product solving and how is that benefiting you?
Automating workflows, reducing errors, Integrations
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.
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.
showing 61 - 70