Tray.io Reviews

* Intuitive and easy to use (especially as a technical person, it comes naturally)

* Comprehensive logging and log search capabilities

* Flexibility in any situation

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

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.

I like being able to perform complex functions with data by connecting platforms in an effortless environment. I also love how open the tray community in slack is. How many companies have a slack community that's public AND have a product feedback channel?

There isn't much to dislike. Sometimes something doesn't work out in a solution but there's almost always a workaround and there's always someone around to help you find that answer/solution you're looking for. The things i dislike are mostly due to how APIs are architected with the platforms you're using when building out tray workflows and solutions.

Tray is reducing the effort needed to build integrations and in turn reducing barriers for our customers.

Tray allowed us to move quickly to test out different integration approaches and partnerships. Without it, learning and Develpoment on new platforms created roadblocks.

A few things were challenges. On our side as it was not globally available yet when we started using it we had to limit na until other centers were added. That's resolved now.

The ability to enable our customers to flow data from their systems to our platfrom.

The tool is simple and easy to learn. The customer service team is very responsive. Jacob Fuller is THE BEST!

The documentation is not always current.

While the product is very easy to learn and implement, I would still recommend establishing a standard for the design and deployment with your organization.

Moving data between SimpleLegal to Coupa/Workday. Workspaces are the BOMB! It makes moving between development and production much easier than moving between environments.

Tray strikes an excellent balance between ease of use and technical prowess. If you have some basic understanding of coding principles and can work with APIs, you can quickly build and iterate automations. The UI makes it really easy to fix issues, and once you understand how the individual pieces take and distribute data you can build some very intelligent tools. Most of the connectors have options to make direct calls to a service's API, so if there are endpoints that need special attention you can build a nuanced request. For other services the ability to use HTTPS or GraphQL with a user-provided auth gives us options that would have been very difficult to achieve.

We have also found that we can rely on the Tray service. We've been running regular automations for years without interruption. Even with event-driven automations processing thousands of requests daily, we haven't had failures in the Tray service (which is way better than most of the APIs we deal with). We have a automation for automatically swapping SSL certificates on client sites that we've been running on Tray for almost two years. It has never failed to handle it, and that's critical for our clients who need their sites 24/7.

I wouldn't say anything missing is deal-breaking, but there are a couple of features I'd like to have. The way that individual nodes handle errors can be a bit irksome. Generally, the simple pass/fail scenario is fine, but there are times when I would love to build conditional states into the nodes directly. For example, you might have a connector node with one API that then passes data to another API. Sometimes the first request will differ slightly, and cause the second one to fail. We ran into this with Dropbox. If you requested folder contents you would get slightly different responses depending on if you were on the first page or anything after the first page. The only way to deal with that was to build a separate branch to handle it. I'd love to handle that kind of conditional difference in the node, instead of having all sorts of conditional branches with their own nodes.

We've fully integrated Tray into our own app for our clients, effectively whitelabeling the solutions we build in Tray. One of the key pillars of our strategy is a connected ecosystem in the marketing tech space, and Tray is playing a pivotal role. For the most complex integrations, we bring in partners who are experts to build. That is quite expensive, and we had a wide array of technologies that wouldn't be worth integrating at that cost. We had the option of bringing in engineers to build individual connections between our app and others, but the risks didn't seem worth it. We would have needed to foster knowledge of those APIs, keep them up to date, and manage all the devops around that. That's a viable strategy, but it didn't really make sense when we had the option of just bringing in Tray and using it as infrastructure.

Tray has been great for filling in the integrations within that realm. We've been able to build out a healthy library within a few months. We didn't need engineers to do it, just a couple people with good knowledge of data structures and APIs. We can do it at a cost that makes sense for our clients, and we're seeing quick adoption of our solutions with immediate ROI. The true value we've found is the ability to find and remedy issues or add features. The infrastructure of Tray lets us make updates and push them in real time. This has been critical for us to adapt to the nuanced needs of our clients. It's also opened up a whole new business for developing custom solutions for clients. We can offer it at a cost that makes it reasonable for them, but gives us a healthy margin. Over the long term we expect the custom solutions to contribute equally with our general ones.

Tray.io is extremely easy to use and very stable. It simplifies complex data integration / ETL tasks by providing a transparent, reliable glue layer between systems. The confidence and increased speed of development this provides will quite literally 10x your productivity.

Log and error management still needs some work. Currently, we use the Slack integration to broadcast error notifications in realtime; otherwise, it's too easy for workflows to fail silently.

We use Tray for ETL and integration between many internal and 3rd party systems. In the modern era of Open APIs, interoperability is paramount. Tray makes this extremely easy.

The breathe of tools available, the documentation, the templates that if don't exactly fit will give you ideas for how to implement problem solving solutions.

Whilst the step logging is great and alerting workflows useful sometimes I just want to see a text log of everything firing , or not, and access it from outside the platform.

* Real time ochestration of team collaboration between disparate business groups who want to stay in their own tools, for instance Asana (PM) and Jira (Dev).

* Optimising and standardising working practices of e-Commerce business (Store, Inventory, Freight, CRM)

The fact that the platform allows you to easily and quickly implement a solution that would much longer through coding.

There are still some limitations on some of the connectors, but you can still set up your custom http query.

We need to quickly ramp up and proof certain solutions and Tray.io is perfect for this scenario. It also allows us to easily implement new Production solutions.

Tray.io and the best support team. They are constantly improving customer experience

The tray is a very good and powerful tool

I can do a system integration in a quick way to solve my business problem

Tray.io supports various use cases to interconnect data across various tools. Due to its ease of use and multiple integration connectors, we have successfully implemented Tray as the critical connector tool to automate the data flow across Intercom, Salesforce and other key tools in our Tech stack.

It can be difficult to interpret failed steps in a workflow and identify the most optimal fix, especially when it comes to hitting rate limits in a bulk update job. It would be great if Tray.io could provide recommended fixes to failed steps/executions to apply to the workflow.

Tray.io helps us sync critical fields from multiple Salesforce custom objects every time a field change occurs to enrich the user profiles of our customers in Intercom. These fields are vital to our real-time campaign targeting criteria and personalization in Intercom. Tray.io also helps us sync campaign interactions from Intercom back into Salesforce as activity tasks. This helps inform sales reps and CSMs which nurture touches our users and accounts are receiving and engaging with.