Automation has streamlined credit workflows and highlighted where testing and complexity can improve
What is our primary use case?
We run automation workflows with Tray.io to take data from our internal databases and update a third-party software that we use. Specifically, my company offers digital trade credit, and we use that software to support our collections processes.
At a high level, our systems call a webhook in Tray.io. The workflows in Tray.io then triage and process the incoming data, and finally makes API calls to the third-party service to modify objects.
What is most valuable?
I appreciate the logging features that Tray.io offers, as it is fairly intuitive to use. It is also fairly straightforward to customize debugging messages if needed.
The logging and debugging features in Tray.io have helped us considerably, especially when dealing with APIs that return errors sometimes. Errors could be a configuration issue on our side or 500 errors, and being able to go through each of the workflow steps and see what the outputs were at that particular point has been quite useful for us in terms of making our workflows more resilient and understanding what has gone wrong.
Tray.io has positively impacted my organization by helping us automate both the development and maintenance work that is needed to keep our internal database and this third-party service in sync.
What needs improvement?
It was not always easy to test our changes in Tray.io. In a software engineering context, you might imagine there being different branches and different environments to make changes where you can make changes and test them, but in Tray.io it does not quite work the same way. I understand there have been improvements in this regard.
For how long have I used the solution?
I have been using Tray.io for about two years.
What do I think about the stability of the solution?
Tray.io is stable in my experience.
What do I think about the scalability of the solution?
As our product got more complex, we needed to adapt our Tray.io setup to match that, and that was when the benefits of it being no-code or low-code started to pale in comparison to the cost of making everything slightly more complicated. Given the limited time we have invested in it, I would say Tray.io was fine for us in terms of processing larger volumes, but it was less smooth-sailing when it came to increasing complexity.
How are customer service and support?
The customer support from Tray.io is adequate. It is not great, but not terrible in my memory.
How would you rate customer service and support?
What was our ROI?
I am not in a position to comment on seeing a return on investment, but instead of paying Tray.io, we could have spent more of our engineers' time.
What other advice do I have?
I think in general it has been a positive experience with Tray.io, and while there are areas where it can be improved, overall it is a good product. I rate Tray.io a seven out of ten.
An Integration tool
What do you like best about the product?
Can integrate the workflow easily without any prior knowledge of the platform.
Easy to maintain the workflow once created, has got this feature that sends the email if any error occurred into your platform.
Can use AI (Merlin) to build the workflows and get the help from AI to integrate the steps into the workflows.
Ease of implementing the workflow is quite good.
Customer support is also good, getting the response from the support team is quick too.
Frequency of usage is good because of lot of features.
What do you dislike about the product?
The AI should be more smooth although the AI is pretty good, but it needs more finement.
Also the documents should be more descreptive.
What problems is the product solving and how is that benefiting you?
Building the workflows to integrate the data from one platfrom to another seems easy with using this platfrom. Using this platfrom is quite understandable. No need to go through the documentation.
Sending data from one to another is good.
Tray for amanging worflows and integration with Salesforce
What do you like best about the product?
We use tray for lead routing across all regions by setting up customised rules. Loved the new AI integration features
What do you dislike about the product?
It's a little complex rule to be used if you are new to it. Also it can't be used if the lead routing rules are complex
What problems is the product solving and how is that benefiting you?
We are using Tray at Docusign for managing the lead routing
Tray review
What do you like best about the product?
It's a reverse ETL tool with drag and drop features so it can accommodate a lot
What do you dislike about the product?
There's definitely a learning curve while figuring out some functionality
What problems is the product solving and how is that benefiting you?
Tray was helping to orchestrate data pipelines that couldn't be solved with an ETL tool alone
Depends on Skill Level
What do you like best about the product?
Incredibly flexible way to customize flows. Interface that helped me to visualize the process
What do you dislike about the product?
Difficult to get other people to understand and use it too.
What problems is the product solving and how is that benefiting you?
Integrating other platforms into salesforce. AI assisted workflow increases accuracy and decreases time. Also, less frequent switching between apps seems to decrease user fatigue.
Best Automation for Enterprise Clients
What do you like best about the product?
The best thing about tray.io is Merlin AI chatbot
What do you dislike about the product?
Pricing is pretty heavy for a SME and single users
What problems is the product solving and how is that benefiting you?
Automating my business and well as managing API has been very easy after we started using tray.io
Simple and easy setup for automation tasks.
What do you like best about the product?
Simple and easy setup for automation tasks.
What do you dislike about the product?
Limited supported software compatibility.
What problems is the product solving and how is that benefiting you?
Automation of manual processes.
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.
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
What problems is the product solving and how is that benefiting you?
integrating different components of tech stack together
