Enterprise customers can use their own SSO implementation, so access to the new platform follows your identity rules from the first day.
Source: make.com/security
From Tray.ai to MakeMigrate from Tray.ai (Tray.io) to Make
Tray.ai (formerly Tray.io) workflows map cleanly to Make scenarios: connectors become app modules, branches become routers and loops become iterators. We plan the move so nothing stops while it happens.
Why teams move from Tray.ai to Make
One platform: teams that run Tray alongside other automation tools consolidate on Make.
Visual and readable: Make's canvas shows every module and route, and each run shows the data in every step.
Contract cost: the inventory shows which workflows are worth moving and which can be retired.
Enterprise controls: your own single sign-on, teams and roles, longer log storage and support terms on Make Enterprise, as Make lists them.
Tray.ai concepts in Make
What each part of a Tray.ai workflow becomes when it is rebuilt as a Make scenario.
| In Tray.ai | In Make |
|---|---|
| Workflow | Scenario |
| Connector and operation | App and module |
| Trigger (webhook, scheduled or service trigger) | Trigger module, custom webhook, or the scenario's schedule |
| Boolean condition | Filter |
| Branch | Router |
| Loop collection | Iterator, then an aggregator |
| Data mapper, JSON transformer and script connector | Mapping panel functions, JSON modules, and custom functions on Enterprise |
| Callable workflow | A separate scenario called through a webhook |
| Connector Builder and HTTP client | A custom app, or the HTTP module |
| Data storage connector | Data stores |
| Authentications | Connections |
| Projects and workspaces | Teams and folders |
How the move runs
The same stages, in this order. We give a written plan and scope after the inventory.
- 1Inventory what runs today
Every workflow, its owner, its trigger, the apps it touches, how often it runs and when it last ran. Anything that has not run in months is a candidate to retire, not migrate.
- 2Map concepts and connections
Each step is matched to a Make module. Apps without a Make module get an HTTP call or a custom app. Credentials are re-created as Make connections owned by service accounts, not people.
- 3Set up Make Enterprise
Organization, teams and roles, single sign-on, folders and naming, error-handling standards, data stores and data structures, decided before the first scenario is built.
- 4Rebuild and test side by side
Scenarios are rebuilt in priority order and run against test data. Outputs are compared with the old platform's for the same inputs until they match.
- 5Cut over in waves
Triggers move a group at a time: webhook senders are pointed at Make, polling triggers start from the right record, and the old workflow is switched off, not deleted, until the Make scenario has run cleanly.
- 6Retire and hand over
The old workflows are archived and the source account closed. Each scenario is documented in plain language, and your builders are trained on Make.
What to watch when leaving Tray.ai
- Webhook URLs change: every system that calls the old platform has to be pointed at the new Make webhook.
- Polling triggers need a starting point, or the first Make run can pick up records the old platform already handled.
- OAuth connections are re-authorised in Make by someone who owns each account; passwords and tokens are never copied across.
- Usage is counted differently: estimate the operations each scenario will use (loops and iterators multiply them) before cutover.
- Script connector logic needs a decision for each step: a Make function, a custom function, or your own endpoint.
- Embedded integrations you offer your own customers need their own plan: tell us early, before assuming Make covers that case.
Make Enterprise features that help this move
As Make publishes them; the source is named on each card.
Roles and teams are managed inside the organization, so each migrated scenario has an owning team and only that team can change it.
Source: make.com/securityLog data is kept for 30 days by default, and the Enterprise Plan offers longer storage: useful when an audit asks what a scenario did.
Source: make.com/securityEnterprise Plan customers get 99.5% cloud service uptime and Enterprise support with defined SLAs.
Source: make.com/securityFrequently asked questions
Is it Tray.io or Tray.ai?
The same company. Tray.io now calls itself Tray.ai; this guide covers workflows built under either name.
Can Tray workflows be imported into Make?
Not directly. The formats differ, so we rebuild each workflow as a scenario, using the Tray workflow as the specification.
What about connectors Make does not have?
We check every connector and operation in the inventory. Anything without a Make module becomes an HTTP call, or a custom app when it is reused across many scenarios.
Consultants in a Box is a Make partner and an independent consultancy; this page is ours, not published by Make or by Tray.ai, Inc. (formerly Tray.io). Make and the Make logo belong to Make; Tray.ai is a trademark of its owner. Facts about Tray.ai are kept general; check Tray.ai's own site for current details. Last reviewed November 6, 2026.
Ready to plan your move from Tray.ai?
Book a call. We inventory what runs today, map it to Make and give you a written migration plan and scope.