The tracker runs on your real accounts, so Salesforce comes first. You connect it through an auth alias: a name in your config that points at an authentication in your Tray workspace. Your code uses the name. The credential stays on the platform, and you, your assistant and your code never hold it.
How the app reaches your systems
- Your appCalls the salesforce alias
- Tray auth aliasResolves to the real credential, held centrally in the Tray platform
- SalesforceOr any system connected in Tray
Connect it
Connect Salesforce to this app. Show me the Salesforce authentications in my Tray workspace, let me pick one, and add it as "salesforce".Pick one and the assistant adds the alias to the app’s config. If there isn’t one yet, it gives you a link to create it in Tray. Create it, say you’re done, and it carries on.
Why an alias
- Nothing to leak. No token in the code, the config or the prompt history.
- Rotate once. When the credential behind the alias changes, the app follows, with no code change and no redeploy.
- On record. The alias list says which authentications the app uses, and the dashboard shows which one each call used.