Overview
MCP Connector Tools
MCP Connector Tools
Tray Agent Hub
Inside the Tray ITSM Agent

Product video
Tray.ai is an AI orchestration platform that connects AI to the enterprise systems, data, and workflows that run your business.
Most organizations can build an AI proof of concept. The harder problem is running AI reliably across real business processes, where AI needs to reach the right data, trigger actions across systems, and operate within clear governance boundaries. Tray sits between your AI models and your enterprise operations to solve that problem.
Companies like Zuora, Apollo.io, HackerOne, NetApp, and Cisco run Tray to build AI-powered workflows, deploy agents across their operations, and connect hundreds of enterprise systems, all on a single platform with the observability and controls that production AI requires. Access Amazon Bedrock foundation models inside Tray, with the integration infrastructure and data connectivity to make those models useful in real business environments.
For Private Offers/Custom Scoping: Please contact aws_sales@tray.ai
Highlights
- Build and deploy AI agents and AI-powered workflows connected to 700+ enterprise systems, with full control over data access and actions
- Deploy and govern MCP servers centrally through Agent Gateway. Extend any AI model or agent with workflow-backed tools that connect to any app or data source
- Run agents, integrations, and AI-infused automations on a single platform with unified observability, audit trails, PII tokenization, and access controls
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months |
|---|---|---|
Tray Enterprise Edition | Enterprise License with task consumption (includes Enterprise Support) | $150,000.00 |
Vendor refund policy
Tray.io sells an annual subscription service that is payable in advance. Unfortunately, refunds are not available during the term. Customers can elect not to renew at the end of their subscription.
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Support
Vendor support
Get help with Frequently Asked Questions and common troubleshooting topics at our support center: https://tray.ai/documentation/help/frequently-asked-questions/account-management-faqs or contact support@tray.ai for assistance.
Learn to automate your apps with online learning at Tray Academy:
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Automated student enrollments have reduced manual work and now free our team for higher-value support
What is our primary use case?
We used and evaluated Tray.io for approximately three to six months during a proof of concept evaluation phase. During this period, our engineering and operation teams utilized the platform to build high-volume data integration pipelines, specifically syncing student enrollment data between our student information system and the LMS system that we have. While we ultimately decided to consolidate our day-to-day automation needs on Make due to its lower barrier to entry and visual ease for non-developers, our time with Tray.io gave us a solid understanding of its enterprise-grade capabilities and structure.
Our primary use case during our evaluation of Tray.io was automated student roster management and enrollment synchronization. Specifically, we needed to ensure that when a student registers for a course on our platform, their profile gets updated, and course access to the particular subject is also done across our internal database as well as our LMS systems. A specific example would be that we set up a workflow which would handle batch updates between our core student database that was running on Supabase in Postgres and our LMS system, which was using a version of Canvas during that time. The workflow operated as follows: when a dual trigger is queried, our database is queried at a specific time at night, maybe around 12:00 a.m. or 1:00 a.m., to fetch all the new student registrations and course changes that were done in the last 24 hours. Then, Tray.io received the data as a nested JSON payload. Using the Tray loop helper, the workflow iterated through each student record to map a field in each specific column for student ID, email, course name, and role based on the format required in the LMS API. The logic that was built handled different user roles; if a record indicated a teaching assistant, the workflow sent them specific permission in the LMS, and if it was a standard student, they would be assigned the standard access.
The workflow sent formatted data to the LMS API so that we could create or update enrollments. If an API call failed due to any issues such as invalid email format, Tray.io's error handling branch caught the failure, isolated this specific record, and sent us a notification in our Slack channels with the error details, allowing us to manually fix it while the rest of the batch could sync without any interruption.
What is most valuable?
In our specific use case, several features stood out particularly strong from Tray.io. There is a robust loop and data helpers when dealing with large datasets of student data. The payload structures are rarely flat; we would have nested objects throughout. Tray.io offers highly capable helpers that allow for detailed data manipulation, making the passing of nested JSON data much simpler and easier. There is comprehensive error handling and branching for business-critical workflows such as student enrollments; an important feature is that Tray.io allows us to configure advanced error handling paths for individual steps within a workflow. We can easily set up a try-catch block to define exactly what should happen when API calls fail, and based on that, we can set up the route to alert the team via Slack, which is what we are currently doing. The connector SDK is also very nice; it has a large library of pre-built connectors that can connect a lot of proprietary internal tools directly into Tray.io, allowing the developer to build, test, and deploy custom connectors using Node.js and integrate the data directly into Tray.io.
During our three to six-month evaluation pilot, automating our student enrollment sync with Tray.io delivered proper operational improvements. We reduced our manual data entry and verification work for the operations team by approximately 10 to 15 hours per week during peak registration periods. There were fewer system errors because the system-to-system data mismatch errors were reduced to near zero during our test runs. There were still issues where the student entered the wrong input; these cases were being tracked using error handlers. The pilot proved that automated near-real-time sync was feasible for our infrastructure, helping shape our long-term automation and data integration strategy.
What needs improvement?
Tray.io is definitely a highly powerful tool, but there are three main areas that I feel could be improved. There is a steep learning curve in user accessibility; the builder is highly developer-centric, making it difficult for a non-technical team member to modify or troubleshoot workflows. Introducing a more intuitive visual interface similar to what we have in make.com right now would make the platform much more collaborative and easier to work with for any non-technical folks or newly onboarded engineers, allowing them to be briefed faster.
Visual debugging is another area where troubleshooting complex nested loops can feel very abstract. Having clearer, more visual step-by-step data tracking during test runs would speed up the development and testing process. The pricing model is geared heavily towards enterprise budgets; offering more flexible mid-market pricing tiers would make it more accessible for a growing organization that wants a small start and scale up gradually.
The core platform security is highly robust and easily meets our requirements for SOC 2 and GDPR compliance. However, when utilizing their AI features such as Merlin AI with sensitive student data, we maintain a very cautious approach. While Tray.io provides enterprise-grade governance guardrails and data masking capabilities, our internal compliance policies prevent us from passing any personally identifiable student information directly through AI-driven processors. We trust Tray.io's underlying infrastructure security, but we believe organizations must still enforce strict data filtering protocols on their end to ensure student privacy is maintained.
During our evaluation, we tested the AI capabilities in a sandbox environment, primarily using it to generate workflow drafts and natural language prompts from web data schemas. Strength-wise, it is highly capable when it comes to translating simple text descriptions into functional workflow templates. It serves as a great accelerator, helping to map standard files quickly and reducing the initial setup time for basic integrations. For issues, in the case of highly custom APIs or deeply nested data structures, accuracy declines. We noticed occasional misinterpretation of complex schemas, meaning our developers still had to manually review and correct the outputs. It is a highly helpful productivity booster but still requires human oversight for enterprise-grade reliability.
For how long have I used the solution?
I have been working in my current field for almost four and a half to five years.
What do I think about the stability of the solution?
Tray.io is pretty stable.
What do I think about the scalability of the solution?
It is quite easy to scale.
How are customer service and support?
We never had a chance to interact with customer support directly.
Which solution did I use previously and why did I switch?
We did not use a solution previously; we started using a different solution after using Tray.io.
Which other solutions did I evaluate?
We evaluated Integromat and other apps as well, but Tray.io did stand out.
What other advice do I have?
I give Tray.io an eight out of ten rating mostly because of how it is developer-centric and lacks a low-code platform and the pricing. The reduction in manual data tasks had a direct positive impact on our team's daily focus. Instead of spending hours manually cross-referencing registration spreadsheets and troubleshooting discrepancies between our student databases and the LMS, our operation team directed their time towards high-priority student support. Specifically, during busy intake periods, they were able to focus on resolving complex student billing inquiries, improving onboarding material, and handling edge cases for registration requests much faster. The platform is definitely a value and worth considering for implementation.
Webhook workflows have streamlined data routing and improve daily debugging and logic building
What is our primary use case?
What is most valuable?
The best features Tray.io offers are debugging, detailed instruction, multiple webhook configuration, workflow items, and flexibility to add logics.
Out of those features, I find myself using logic and debug the most, and they have been the most valuable in my day-to-day work.
Tray.io has positively impacted my organization by helping to manage webhooks easily and workflows easily, and it has improved collaboration so that other clients can use webhooks.
What needs improvement?
There is not much that can be improved in Tray.io. It is a good tool, but debug can be improved further and the solutions can be improved further.
For how long have I used the solution?
I have been using Tray.io for 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?
Tray.io's scalability is very good. It can be scaled very fast.
How are customer service and support?
I have never had the opportunity to interact with customer support, but it should be good.
Which solution did I use previously and why did I switch?
I have not used a different solution before Tray.io.
How was the initial setup?
Tray.io is deployed in my organization on a public cloud. We use Tray.io itself, so there is no specific deployment. I did not purchase it myself. I think it was purchased directly from Tray.io.
Which other solutions did I evaluate?
I have not evaluated other options before choosing Tray.io.
What other advice do I have?
I rate Tray.io an eight out of ten overall.
I gave Tray.io an eight out of ten because of minor improvements needed, some feasibility to manage and configure solutions, and a need for more flexibility to make it a ten.
Regarding Tray.io's AI capabilities, I have not used them.
I have not used Tray.io's AI capabilities regarding accuracy and reliability of output, but when I did use it, it gave me the results.
My advice to others looking into using Tray.io is to consider it, as it is a good tool that people can use. I gave this review a rating of eight out of ten.
Easy-to-Identify Logs and Audit Trails
Marketing A/B tests have gained deeper insights from user behavior and unified global reporting
What is our primary use case?
My main use case for Tray.io is to conduct A/B testing for marketing initiatives that the company has undertaken. We test the deployment of different campaigns across similar cohorts and evaluate which one performs better.
Tray.io fits into my A/B testing process by analyzing the number of words used by consumers in comments and the number of times they stopped campaign videos at specific points. Through this analysis, we can investigate the attention levels of users and determine what thoughts are elicited by the campaign.
I have found that the error management in my main use case with Tray.io is not as effective as we would prefer. We would appreciate having a way to recycle cases that do not carry much value. Every user is precious in their own way, and even if a user does not provide much information, we would still value the ability to extract some information from those boundary cases.
What is most valuable?
The best features Tray.io offers include excellent visualization capabilities and a dashboard, which stand out to me the most.
I appreciate that it is very easy to convert the data we receive from Tray.io into dashboards from Power BI, which is extremely useful. I would also appreciate if in the future Tray.io provides a way to natively convert the data to Tableau.
Tray.io has positively impacted my organization as it provides a trusted way to organize data results and share them throughout the company at once. As a multinational and very large company, it is definitely beneficial that those of us in the UK can use the same format that colleagues use in India, and the entire data architecture is framed within a trusted system from an established organization. As far as I know, Tray.io has been operating for the last 12 years, making it a very reliable system.
What needs improvement?
I believe Tray.io can be improved by offering integration with Tableau, which is still not available.
I rated it an eight because there are still some things that can be improved, as I mentioned before.
For how long have I used the solution?
I started using Tray.io approximately one year ago.
What do I think about the stability of the solution?
In my experience, Tray.io is stable, as we have never experienced issues with it failing or being unavailable. We did not experience any downtime, compatibility issues, or system issues at all.
What do I think about the scalability of the solution?
The scalability of Tray.io is quite good. We were able to deploy it from a small company within Tata with 200 people to what is now a multinational company with 92,000 people globally, and the people involved in using Tray.io number in the hundreds. I believe the scalability is quite good.
How are customer service and support?
I have never used the customer support for Tray.io because the software is very easy to use and we never needed to contact support. However, I can tell you that the support provided through newsletters and update bulletins is quite good.
Which solution did I use previously and why did I switch?
Previously, we attempted to develop an in-house solution as a company proprietary system, but we failed to achieve a good standard and quality level with that approach. We therefore looked for an established solution.
What was our ROI?
I have seen a return on investment as the company has been renewing the product for the entire 19 months we have been using it, which indicates that trust is high and they likely see value and advantage in using the system. There are no complaints in this regard.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for Tray.io is that I did not personally follow the pricing negotiation, but I understand that the company pays a monthly fee which is very competitive. No one has complained in the finance department, and it is very rare for Tata Motors to refrain from complaining about pricing.
Which other solutions did I evaluate?
A few options were evaluated before choosing Tray.io, but I cannot recall which ones were proposed to me because Tray.io was identified as the most valid option since the very beginning.
What other advice do I have?
My advice to others considering Tray.io is to trust the process because once the installation is complete, it is extremely easy to deploy and set up.
I have rated this product an eight out of ten.
Automation has transformed onboarding workflows and still needs clearer error guidance
What is our primary use case?
Tray.io 's main use case for my organization is workflow automations related to user onboardings, license reconciliation, and a myriad of other tasks to improve redundant processes.
An example of a workflow that I automated with Tray.io was during a user email migration where this specific workflow would place individuals being migrated from an offshore email address to our corporate email address into a Slack message saying, 'Hey, we're getting you onboarded with a new email address', and putting them in a specific Slack channel, involving a lot of webhooks and communications.
How has it helped my organization?
Tray.io has positively impacted my organization by reducing the amount of redundant tasks that our team performs by approximately 80%, and the numbers are quite significant with the workflows alone, as we are working towards creating and utilizing AI within these workflows as well.
The 80% reduction in redundant tasks was measured based on the time saved, primarily for onboarding processes. We use a lot of offshore work, and Tray.io helps keep us organized in that sense.
What is most valuable?
I appreciate that Tray.io is low-code automation, meaning you do not have to be an expert in JSON to understand the components and create automations.
The best features that Tray.io offers include a lot of API connections, and we use it for Slack, with Airtable being our data and low-code database that also handles automations, where we store information. You can also connect to G Suite and many different types of environments that can be automated.
What needs improvement?
One way Tray.io could be improved, especially for people coming in with no real coding experience, is with more comprehensive error messages. When an automation fails, it usually provides the JSON format, and if Tray.io could include a summary of what the actual error entails, that would be quite beneficial.
For how long have I used the solution?
I have been using Tray.io for approximately eight months.
What do I think about the stability of the solution?
In my experience, Tray.io is stable, considering the number of workflows we automate. I would say it is quite stable.
What do I think about the scalability of the solution?
Tray.io's scalability is highly effective, given the amount of workflows we generate.
What was our ROI?
As for return on investment with Tray.io, I have reduced approximately 80% of our redundant tasks through Tray.io alone.
Which other solutions did I evaluate?
What other advice do I have?
I would rate Tray.io overall about a seven, give or take, with a consideration of seven and a half. I chose seven for my rating mostly for cost-related reasons as I would not really recommend it for smaller companies or startups. Zapier would be a more beneficial solution for those, but if you are looking to scale up, I think it is worth the price, which is the only reason I would give it a seven rating. My overall review rating is seven.
The learning curve for new users on Tray.io is somewhat noticeable, as when you first log on having never used a low-code platform, you need to take the time to really learn how the workflows are deployed and how to connect everything. However, once you are using it every single day, it is quite easy to catch up, though there is still a bit of a learning curve.
Tray.io integrates fairly well with our existing tech stack, as we utilize Okta, Slack, Google Cloud platforms, AWS , and a multitude of software-as-a-service applications, and Tray.io automates many of these. From my experience alone, it helps with onboardings, offboardings, and title changes.