Connection Overview

The SysTrack integration connects iPaaS.com to a SysTrack tenant hosted by Lakeside Software. All API requests are sent to the subscriber's regional SysTrack Cloud host and are authenticated with an OAuth 2.0 access token obtained from Microsoft Azure AD B2C using the Resource Owner Password Credentials (ROPC) flow. The credentials used are those of a SysTrack service account that SysTrack Support creates and links to the tenant — not an interactive user login.

The integration synchronizes two entities:

Customer: SysTrack users, including their linked systems and associated sensor actions. This entity flows inbound only, from SysTrack into iPaaS.com.
Message: SysTrack sensor alerts. This entity flows inbound from SysTrack into iPaaS.com, and supports one outbound action — dispatching a SysTrack automation (autofix) run for a message and recording the resulting batch identifier back on the iPaaS.com record.

There is no SysTrack sandbox or test environment available to subscribers. All configuration and validation is performed against the subscriber's live SysTrack tenant, so changes should be made deliberately and during a low-activity window.

How to Connect

Prerequisites

Before configuring the subscription in iPaaS.com, subscribers or their MiSP must have the following in place:

An active SysTrack Cloud tenant with tenant administrator access.
A SysTrack service account. The first time the API is to be used, contact SysTrack Support and request a service account. SysTrack Support creates the account and links it to the tenant. This is the only supported way to obtain API credentials — service accounts cannot be self-provisioned.
The tenant's Azure AD B2C tenant name and ROPC policy name. Both values must be supplied by SysTrack Support. They are not displayed anywhere in the SysTrack tenant administration pages.
Azure Active Directory configuration that meets SysTrack requirements. Subscribers or their MiSP should confirm the tenant's Active Directory configuration with SysTrack Support before attempting the first connection.
An iPaaS.com company with permission to create subscriptions, and the SysTrack integration available to that company.

Configuration Details

The integration requires six credential and endpoint values. Every one of them is required — the connection will not establish if any is blank. The values are entered on the iPaaS.com Subscription Settings page and applied together.

API URL: The base address of the SysTrack Cloud API for the subscriber's region. For the United States region the value is https://cloud.lakesidesoftware.com/api. Regional hosts exist for the EU/UK (https://cloud-uk.lakesidesoftware.com/api) and Australia (https://cloud-au.lakesidesoftware.com/api). The correct host is the one matching the SysTrack Cloud instance the subscriber signs in to, and it must correspond to the same region as the CLIENT ID value below.
CLIENT ID: The Azure AD B2C application identifier for the subscriber's SysTrack Cloud region. Sign in to the SysTrack Cloud dashboard and navigate to the tenant administration area, Tenant Information page, at https://cloud.lakesidesoftware.com/Cloud/Dashboard/Admin/TenantInformation (substituting the regional host for EU/UK or Australia tenants). The CLIENT ID is the long identifier value shown below the Cloud ID. Subscribers can also contact SysTrack Support and request the "Azure AD B2C ID" to obtain this value. The Cloud ID displayed alongside it identifies the region: eab7a011-36fc-4c1b-94dd-cb6f31473ff3 for the United States, 4b68aeaa-cb67-4280-87a1-016fecb772b3 for the EU/UK, and 84220ad6-2194-4096-b2c7-4cb311ba4090 for Australia. Confirm the Cloud ID shown matches the region of the API URL entered above before saving. The value takes the shape of a GUID, for example 11111111-2222-3333-4444-555555555555; use the real value for your own region rather than this illustration.
USER NAME: The service account user name. On the same Tenant Information page, take the long identifier value shown below the Tenant ID and append @cloud.api to it. For example, a Tenant ID value of 00000000-1111-2222-3333-444444444444 produces the user name 00000000-1111-2222-3333-444444444444@cloud.api. Subscribers can also contact SysTrack Support and request the "Azure AD B2C username" to obtain this value.
PASSWORD: The password for the service account. As a tenant administrator, sign in and navigate to the Manage Service Accounts page at https://cloud.lakesidesoftware.com/Cloud/Dashboard/Admin/ManageServiceAccounts (substituting the regional host where applicable), then select Change Password next to the API account to set a new password. Subscribers can also contact SysTrack Support and request assistance with setting the "Azure AD B2C password". iPaaS.com stores this value in encrypted form. No example is given here because the value is set by the subscriber and must never be shared or reproduced.
TENANT NAME: The subscriber's Azure AD B2C tenant name, provided by SysTrack Support. This value is structural, not cosmetic — it is substituted directly into the Azure AD B2C token address the integration calls, in two places, so an incorrect value produces an unreachable sign-in host rather than a rejected credential.
ROPC POLICY: The name of the Azure AD B2C Resource Owner Password Credentials policy for the tenant, also provided by SysTrack Support. Like TENANT NAME, it is substituted into the token address and determines which sign-in policy Azure AD B2C evaluates.

To see how TENANT NAME and ROPC POLICY combine, consider a token address of the form https://exampletenant.b2clogin.com/exampletenant.onmicrosoft.com/b2c_1_ropc_auth/oauth2/v2.0/token. In that example the TENANT NAME is exampletenant and the ROPC POLICY is b2c_1_ropc_auth. Enter only the two bare names in the settings — iPaaS.com builds the full address. Both values must be entered exactly as SysTrack Support supplies them, including case.

NOTE: Never share the service account password, and do not reuse an interactive administrator account for the integration. Use the dedicated service account SysTrack Support provisions, so that administrator password changes and personnel changes do not silently break the integration.

Configure Subscription Settings

The following settings are configured on the iPaaS.com Subscription Settings page during installation and remain available for ongoing reference and updates. After changing any value, click Apply to save and re-establish the connection.

The iPaaS.com Subscription Settings page for the SysTrack integration, showing the Name and Versions fields, the Create Default Mappings checkbox, the six SysTrack credential and endpoint fields, and the throttle and concurrency fields

Field	Description	Required	Example
Name	A unique identifier for the subscription within the company. Conventional format: [Product Name] - [Environment/Purpose].	Yes	SysTrack - Production
Versions	The SysTrack integration version. iPaaS.com selects the latest compatible version by default; subscribers can pin an earlier version when required for compatibility.	No	Latest
API URL	The regional SysTrack Cloud API base address. See Configuration Details above for the per-region values.	Yes	`https://cloud.lakesidesoftware.com/api`
CLIENT ID	The Azure AD B2C application identifier for the subscriber's SysTrack Cloud region, obtained from the Tenant Information page or from SysTrack Support.	Yes	`11111111-2222-3333-4444-555555555555`
USER NAME	The service account user name, formed by appending @cloud.api to the Tenant ID value, or obtained from SysTrack Support.	Yes	`00000000-1111-2222-3333-444444444444@cloud.api`
PASSWORD	The service account password, set on the Manage Service Accounts page. Stored encrypted by iPaaS.com.	Yes	Set by the subscriber; no example is given
TENANT NAME	The Azure AD B2C tenant name supplied by SysTrack Support. Used to build the token address.	Yes	`exampletenant`
ROPC POLICY	The Azure AD B2C ROPC policy name supplied by SysTrack Support. Used to build the token address.	Yes	`b2c_1_ropc_auth`
API Throttle Limit	Maximum number of API calls per throttle window sent from iPaaS.com to SysTrack.	Yes	500
API Throttle Seconds	Duration in seconds of each outbound throttle window.	Yes	60
API Throttle Limit (To iPaaS)	Maximum number of record transfers per throttle window sent into iPaaS.com during inbound Customer and Message synchronization.	Yes	500
API Throttle Seconds (To iPaaS)	Duration in seconds of each inbound throttle window.	Yes	60
Concurrent Connections	Maximum number of simultaneous API connections to SysTrack.	Yes	10
Concurrent Batch Executions	Maximum number of batch operations that can run simultaneously for this subscription.	Yes	10

DESTRUCTIVE SETTING — API URL and CLIENT ID. These two settings together select which regional SysTrack Cloud tenant the subscription reads from. Each regional host is a separate tenant with its own independent identifiers, so changing either value on a subscription that has already imported records repoints the subscription at a different record namespace. The existing external-id links between iPaaS.com records and SysTrack users and messages will no longer resolve, and subsequent synchronization will create duplicate iPaaS.com records rather than updating the originals. Set API URL and CLIENT ID correctly at install and do not change them on an existing subscription. If you are unsure, consult your MiSP (Managed Integration Service Provider) or implementation partner before proceeding — the recovery cost if the change is wrong is significantly higher than the consultation cost.

Changing USER NAME, PASSWORD, TENANT NAME, or ROPC POLICY is not destructive on its own, provided the new credentials authenticate against the same SysTrack tenant. These are the values to update during routine credential rotation.

Authentication Methods

Azure AD B2C Resource Owner Password Credentials (ROPC) — the only supported authentication method

How it works:

Using the TENANT NAME and ROPC POLICY values from the Subscription Settings, iPaaS.com builds the Azure AD B2C token address for the subscriber's tenant.
iPaaS.com submits the CLIENT ID, USER NAME, and PASSWORD to that address using the password grant, requesting offline access so that a refresh token is returned alongside the access token.
Azure AD B2C returns an access token and a refresh token. iPaaS.com stores both, together with their expiry times, against the subscription.
Subsequent API calls are issued against the API URL host with the access token attached, and with JSON content and accept headers.

Token lifecycle:

Access token: Short-lived. iPaaS.com records the expiry time returned by Azure AD B2C and reuses the token until it expires.
Refresh token: Longer-lived. iPaaS.com stores it alongside the access token with its expiry. Where Azure AD B2C does not return an explicit refresh token lifetime, iPaaS.com applies a fourteen-day lifetime.
Re-authentication: When the access token has expired, iPaaS.com re-authenticates using the USER NAME and PASSWORD values held in the Subscription Settings. The service account password must therefore remain valid in SysTrack at all times, and must be updated in iPaaS.com in the same session it is changed in SysTrack.

Error conditions:

If any of the six credential settings is blank, no token request is attempted and the connection cannot be established.
If TENANT NAME or ROPC POLICY is incorrect, the token request is sent to an address that does not exist or to a policy that does not apply, and authentication fails before any SysTrack API call is made.
If the service account password has been changed in SysTrack but not updated in iPaaS.com, token acquisition fails as soon as the current access token expires. Update the PASSWORD setting at the same time the password is changed in SysTrack.
Authentication and API failures surface in iPaaS.com under Dashboard / Integration Monitoring / Error Logs.

Credential Rotation

Rotating the SysTrack service account password:

In SysTrack, sign in as a tenant administrator and open the Manage Service Accounts page.
Select Change Password next to the API account and set the new password.
In iPaaS.com, update the PASSWORD Subscription Setting with the new value and click Apply.
Verify the connection using the steps under Connection Validation below.

Perform steps 2 and 3 together. Because iPaaS.com continues to use the current access token until it expires, a gap between the two steps produces a failure that appears later and is harder to attribute to the password change.

If SysTrack Support issues a replacement service account, update USER NAME and PASSWORD together, and confirm with SysTrack Support whether CLIENT ID, TENANT NAME, or ROPC POLICY also change. Because SysTrack has no sandbox, schedule the change during a low-activity window.

Connection Validation

To verify the connection after installation or credential rotation, use the Customer flow. Both collections apply mapping filters, and a record excluded by a filter is skipped silently — so the absence of error rows on its own does not confirm that the connection works.

In SysTrack, choose a user whose email address is populated and is not the SysTrack placeholder text "Not collected". Users failing either test are excluded by the collection's mapping filter and produce no Customer record and no error row, so a user chosen at random is not a valid test subject. Note that user's SysTrack account identifier.
From the iPaaS.com Manual Sync page, initiate a Manual Sync of that user into iPaaS.com as a Customer record, using the account identifier from step 1.
Confirm in iPaaS.com that the expected Customer record was created or updated with values matching the SysTrack user. This is the success signal. If no Customer record appears, the connection is not verified, whether or not any error was logged.
Review Dashboard / Integration Monitoring / Error Logs for the resulting entries. An authentication or connectivity failure produces an explicit error row identifying the failed call and the response received. An empty Error Log alongside a missing Customer record means the mapping filter excluded the user — re-run step 1 with a different user rather than treating the run as successful.

The Message flow can be validated the same way, with one caveat: only sensor events that are not hidden, whose system has a primary user email address recorded, and for which SysTrack already offers an automation become iPaaS.com Messages. A sensor alert chosen without reference to those conditions may legitimately produce nothing at all, so a Message flow test that yields no record is inconclusive rather than a failure. Where a suitable alert cannot be identified in advance, treat the Customer test above as the connection check — it exercises the same authentication and the same SysTrack Cloud host.

Initialization Support

Currently, initialization is not supported for SysTrack in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process. Initialization is the bulk import of existing records at the point a subscription is first connected.

Records reach iPaaS.com through scheduled polling instead, and the two entities behave differently. Messages are retrieved for the window between the high-water mark recorded at the end of the last successful poll and the current time; on the very first poll, where no mark exists yet, no lower bound is applied and the request covers the tenant's full available sensor history. Subscribers or their MiSP should expect the first message poll to be substantially larger than subsequent ones and should run it during a quiet period. Customers are retrieved differently: every scheduled poll requests the full user list and the comparison against previously transferred records happens after retrieval, so customer poll volume does not decrease over time. Polling is driven by a polling event you configure under Integration Monitoring and Diagnostics / Events, which is also where the cadence is set. SysTrack publishes no inbound webhook, so this polling event is the only automatic path for inbound records.

Subscribers who need a larger historical set loaded than polling provides should use the documented bulk sync approach described in syncing a large dataset using iPaaS.com and Postman Runner.

Throttling

The integration uses configurable throttle and concurrency settings to control the rate and volume of API traffic. These settings are pre-populated with recommended defaults during installation and can be adjusted on the Subscription Settings page.

API Throttle Limit and API Throttle Seconds: Control the outbound call rate from iPaaS.com to SysTrack — the calls made when dispatching a SysTrack automation run and when retrieving records on demand.
API Throttle Limit (To iPaaS) and API Throttle Seconds (To iPaaS): Control the rate at which inbound Customer and Message records are pushed into iPaaS.com during polling and transfers.
Concurrent Connections: Limits the number of simultaneous API connections to SysTrack.
Concurrent Batch Executions: Limits the number of batch operations running simultaneously for this subscription.

NOTE: Lakeside Software does not publish a numeric rate limit or per-period quota for the SysTrack Cloud API, and the integration does not automatically reschedule calls that are rejected for rate reasons. Because there is no SysTrack test environment, tuning has to be done against the live tenant. Subscribers or their MiSP should start from the installed defaults, increase throughput in small increments, and watch Dashboard / Integration Monitoring / Error Logs after each change. If SysTrack returns timeouts or the tenant shows degraded response times during heavy transfers, reduce the throttle limits and concurrency values and stagger large synchronization runs rather than running them concurrently.

For more detail on throttle configuration, see Subscription Configuration – Edit.

SysTrack Connections and Settings