Prerequisites
You need access to Tools & Settings in TrackerRMS. If you do not see this option in your user menu, ask your TrackerRMS administrator to grant you the required permissions or to generate the access token for you.
Instructions
Identify your region
Before connecting, determine which region your TrackerRMS account is hosted in. Check the subdomain in your TrackerRMS login URL:
- United States (evous) — your URL contains
evous - Canada (evoca) — your URL contains
evoca - Rest of world (evogl) — your URL contains
evogl
You will need to select the matching region in the Kombo connection flow.
Generate an access token
- Log in to TrackerRMS.
- Click your user name in the top-right corner of the page.
- Click Tools & Settings in the dropdown menu.
- In the left sidebar, expand Security and click Security Settings.
- Scroll down to the API section.
- Under Generate access token, click Generate to create a new token, or copy your existing token if one is already shown.
Note: Generating a new access token invalidates any previously generated token.
- Copy the access token and keep it somewhere safe — you will paste it into the Kombo connection flow in the next section.
Connecting
- Open the Kombo connection link you received (from the Kombo Dashboard or your integration partner).
- Search for TrackerRMS and select it.
- Review the requested permissions and click Continue.
- Select your Region (see Identify your region above).
- Paste your TrackerRMS Access Token into the corresponding field.
- Click Set up integration.
If the setup completes successfully, your TrackerRMS account is now connected.
Troubleshooting
- Invalid access token — Make sure you copied the full token with no extra spaces. If in doubt, generate a new token in TrackerRMS and try again.
- Connection fails after entering credentials — Double-check that you selected the correct region. A token from a US (
evous) account will not work if you select Canada or Rest of world, and vice versa. - Missing permissions during setup — Your TrackerRMS user may lack API access. Ask your TrackerRMS administrator to verify your account can use the API, or have them generate the token on your behalf.