External reviews
158 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Overall a mixed bag.
What do you like best about the product?
Allows us to connect our systems beween Shopify and an LMS solution we use.
What do you dislike about the product?
We reached out to the customer support team and never heard back. It isn't easy to reach anyone at Tray.io in my experience. It could be easier to setup failure alerts when a synch encounters issues.
What problems is the product solving and how is that benefiting you?
It acts as a connection layer between our Shopify storefront and a learning management platform that contains courses, so when users purchase on Shopify the item is then populated into their user account in our LMS.
Powerful tool with great UI features to make automation easier
What do you like best about the product?
The UI is great in my opinion! I love being able to clearly follow a diagram that shows how the pieces interact with eachother and being able to drag-drop is fantastic. Tray is one of the few/rare tools that allows for quick start-up and is overall intuitive so that junior technical staff can hop in and field some requests with little training.
What do you dislike about the product?
Overall, we really love the Tray platform. The cost is a consideration, but have not found a tool to do the job better.
What problems is the product solving and how is that benefiting you?
Tray is great for mapping APIs to work efficiently together. We've used it for projects like Gift Card Platform migrations so that numbers from our legacy system could still be checked/validated/redeemed.
Incredibly flexibly
What do you like best about the product?
I like how flexible Tray is.
The implementation of its features are in a way such that things just work as you'd expect it to. Theres not many places where you have to do things a certain why and its not clear why.
The implementation of its features are in a way such that things just work as you'd expect it to. Theres not many places where you have to do things a certain why and its not clear why.
What do you dislike about the product?
Theres a few places where you need to do things a certain why and its not documented why.
Examples are mainly from the solution editor of the embedded platform.
1.) when setting up a data mapping from a ddl. If the operation requires any extra inputs, the inputs are shown as their id's instead of their names. the list is also not searchable so one must scroll. The order in which you click them also matters.
- solution would be to have the number of inputs the connector operation requires appear as individual drop downs, and you select which config goes into each slot individually
2.) when changing auths (as in keeping the same connector, just changing the selected auth) it prompts you to change all similar auths, but when you select yes, it potentially misses auths. Theres also no way to quickly identify which auths didn't get switched
Examples are mainly from the solution editor of the embedded platform.
1.) when setting up a data mapping from a ddl. If the operation requires any extra inputs, the inputs are shown as their id's instead of their names. the list is also not searchable so one must scroll. The order in which you click them also matters.
- solution would be to have the number of inputs the connector operation requires appear as individual drop downs, and you select which config goes into each slot individually
2.) when changing auths (as in keeping the same connector, just changing the selected auth) it prompts you to change all similar auths, but when you select yes, it potentially misses auths. Theres also no way to quickly identify which auths didn't get switched
What problems is the product solving and how is that benefiting you?
integrating different components of tech stack together
It is ease to use and very trustworthy
What do you like best about the product?
The workfllow they have to design the business requirement.
What do you dislike about the product?
Somtimes the flow looks busy. But when you do expand and colaps. It will work.
What problems is the product solving and how is that benefiting you?
We are using to update the payment.
An experience that continues to improve
What do you like best about the product?
I enjoy the interface and how you can use the connector snake to map values. It's also really powerful and is constantly improving. I've used Tray for a few years now and it's constantly improving and becoming more innovative. It's also cut down on a lot of development time.
What do you dislike about the product?
The downside of Tray is if you dont have embedded it's limiting to the capabilities of your workflow.
What problems is the product solving and how is that benefiting you?
automating internal business processes and integrations. It cuts down our development time and dedicated resources to build hardcoded integrations.
Tray.io makes us more dynamic!
What do you like best about the product?
I love that it allows teams to maximize their API's, expanding the dynamacism and relevance of a core product without extensive dev work. In my experience, it's made products more adaptable, and allowed us to focus valuable engineering resources on more frutiful products.
What do you dislike about the product?
You are passing data through a third party, which can create some security issues in certain instances. However, because of the work Tray has done with partnerships, that concern is often mitigated.
What problems is the product solving and how is that benefiting you?
Tray.io is allowing us to easily yet comprehensively connect to integration partners, and to also put our customers in a position to fully utilize our API. This puts our product in a better position within the customer's tech stack while also allowing us to provide better ROI by solving for more use cases.
Tray makes it easy to automate workflows between technologies in a scalable way
What do you like best about the product?
I like using Tray. I've been a user since the beginning! The UI has received many updates and they've all been really helpful. I like that you can create a workflow, easily copy it and repurpose it for other services. It because of the powerful template capabilities and nodes that we were able to scale our data sync service to our own customers!
The success of implementing Tray in our business has enabled us to increase customer satisfaction, rentention, and close deals without the need of high effort and expensive code creation. It's a great low/no-code platform.
Their support has also been instrumental in our success. It's much appreciated!
The success of implementing Tray in our business has enabled us to increase customer satisfaction, rentention, and close deals without the need of high effort and expensive code creation. It's a great low/no-code platform.
Their support has also been instrumental in our success. It's much appreciated!
What do you dislike about the product?
Currently I'm not experiencing any downsides; however, I've only ever used Tray.io, with some minor experience using Zapier, Workato, and MS Logic Apps. With my limited experience of similar platforms, I don't know if I'm missing out on something but Tray suits our needs and is reasonably priced so I haven't had any reason to dive into other platforms so far.
What problems is the product solving and how is that benefiting you?
- Data sync between various CRM platforms and UserVoice
- Scalable, repatable processes no matter the volume
- Integration testing
- R&D
- Scalable, repatable processes no matter the volume
- Integration testing
- R&D
End to end automation and integration solution
What do you like best about the product?
* Intuitive and easy to use (especially as a technical person, it comes naturally)
* Comprehensive logging and log search capabilities
* Flexibility in any situation
* Comprehensive logging and log search capabilities
* Flexibility in any situation
What do you dislike about the product?
I'd like to see more pre-built tools for common business scenarios.
Two specific ones that come to mind: parallel execution which waits for all threads to complete before proceeding further and request trickle for APIs that allow low throughput
Two specific ones that come to mind: parallel execution which waits for all threads to complete before proceeding further and request trickle for APIs that allow low throughput
What problems is the product solving and how is that benefiting you?
Tray.io helps bridge the gap between software applications through automation and integration.
It helps build businesses based on composable enterprise patterns where you choose the best SaaS tools for the job and then orchestrate them together with the use of Tray.io to obtain a unique business advantage.
It helps build businesses based on composable enterprise patterns where you choose the best SaaS tools for the job and then orchestrate them together with the use of Tray.io to obtain a unique business advantage.
Powerflow integration workflows
What do you like best about the product?
We receieved great support from Jash, an architect who helped us build out initial workflows. There are a lot of different connectors that will allow you to integrate with lots of different services.
What do you dislike about the product?
Customer support with the support team via email was not instant and it was some times dragging on for days due to timezone differences sending 1 message per day back and forth. This may have changed now as this was based on experiences a couple of years ago.
What problems is the product solving and how is that benefiting you?
Tray.io allowed us to automate sending messages into Slack off the back of webhook events. It also enabled us to sync employee data from a HR system into our system.
Worst vendor experience
What do you like best about the product?
It did allow us to go to market faster with two integrations. But the cost of maintenance has already severely eaten into that advantage.
What do you dislike about the product?
In the last few months, Tray has managed to delete our users, attempt to recover them, and fail -> certain customers could not access the Tray embedded integrations that are available to them due to Tray errors.
Tray's inability to change the timeout of the embedded layout to more than 5 minutes, meant that we had to add over a month of work to our timeline in order to build the UI ourselves for a very common use case: mapping CRM fields.
Tray's inability to allow us to edit the 'Finish' button for authentication means that our customers STILL see this awkward first step in the integration for authentication saying 'Finish' even though it's only the first step of the integration.
For its Salesforce connector, Tray requires FAR more permissions to the customer's Salesforce instance than we require in the integration itself: we only need read access to the specific objects that the customer maps, but Tray asks the customer for a lot more data access, to the point of 'View All Data' within Salesforce. Tray also asks for permissions to manage flows, which is ridiculous for an integration that only requires read access. Tray has made it a lot harder for us to build and ship integrations for customers, instead of easier. Our engineering team is exhausted at having to deal with Tray, and regret the decision to proceed with them as a vendor. They have changed our CSM several times and recently the only reliable person we've encountered at Tray (he was technical and answered our engineers' questions) has left the company. They keep trying to upsell us professional services in order to help 'guide us' to use the embedded app properly - but we have not learned anything in interacting with them that we did not know before from the documentation.
Further, their documentation has been incorrect, leading us to believe that more customer-side permissions are required than they actually are. Please spend some time ensuring your documentation is up-to-date, instead of trying to sell clients more professional service hours.
Tray's inability to change the timeout of the embedded layout to more than 5 minutes, meant that we had to add over a month of work to our timeline in order to build the UI ourselves for a very common use case: mapping CRM fields.
Tray's inability to allow us to edit the 'Finish' button for authentication means that our customers STILL see this awkward first step in the integration for authentication saying 'Finish' even though it's only the first step of the integration.
For its Salesforce connector, Tray requires FAR more permissions to the customer's Salesforce instance than we require in the integration itself: we only need read access to the specific objects that the customer maps, but Tray asks the customer for a lot more data access, to the point of 'View All Data' within Salesforce. Tray also asks for permissions to manage flows, which is ridiculous for an integration that only requires read access. Tray has made it a lot harder for us to build and ship integrations for customers, instead of easier. Our engineering team is exhausted at having to deal with Tray, and regret the decision to proceed with them as a vendor. They have changed our CSM several times and recently the only reliable person we've encountered at Tray (he was technical and answered our engineers' questions) has left the company. They keep trying to upsell us professional services in order to help 'guide us' to use the embedded app properly - but we have not learned anything in interacting with them that we did not know before from the documentation.
Further, their documentation has been incorrect, leading us to believe that more customer-side permissions are required than they actually are. Please spend some time ensuring your documentation is up-to-date, instead of trying to sell clients more professional service hours.
What problems is the product solving and how is that benefiting you?
Tray embedded's value proposition is to make integrations easier + faster to build and launch, with low code.
showing 11 - 20