Summary

An iPaaS.com Message that originated from a SysTrack sensor event can be used to ask SysTrack to run a remediation automation, through the iPaaS.com Message Update outbound trigger and on-demand Manual Sync. This collection is not a general field-level record update: no SysTrack record is replaced field by field. It sends a single autofix request naming the sensor automation to run, the application it belongs to, and the monitored system it should run on, and SysTrack queues that automation for that endpoint. On success it writes the returned batch identifier back onto the originating iPaaS.com Message, closing the loop for endpoint remediation without anyone needing to sign in to SysTrack.

ID Format

Manual Sync ID Format

On the iPaaS.com Manual Sync page, enter the iPaaS.com Message id to dispatch the remediation for that message.

Pattern: the iPaaS.com Message id.

External ID Format

This collection does not use a source-system ID entered by hand. The SysTrack identifier stored against the iPaaS.com Message is the value the integration matches on to confirm the message genuinely corresponds to a SysTrack sensor event before dispatching. It combines the sensor and the monitored system in a single value.

Pattern: sensor id, a vertical bar, then system id.
Example: 101258|100007.

This value is recorded automatically when the message arrives through Add SysTrack Sensor Event TO iPaaS.com; subscribers or their MiSP do not enter it by hand. A Message created directly in iPaaS.com with no SysTrack origin has no such link and cannot be dispatched by this collection.

Deleted Record Support

Deleted Record Support is not supported for this entity. The integration does not implement a delete operation, and delete mappings are not included in the default template. Deleting a Message in iPaaS.com does not remove or cancel anything in SysTrack, and deleting a record in SysTrack does not propagate to iPaaS.com. Creating SysTrack records from iPaaS.com is likewise not supported in this direction: this collection acts on an existing linked message only.

Mapping Collection Status

Status: Enabled.
Trigger Events: the iPaaS.com Message Update outbound trigger dispatches this collection when outbound transfers are enabled in the subscription's Outbound Data Flows section. Manual Sync dispatches a single message on demand. There is no outbound webhook and no outbound polling for this direction; those two paths are the only ways this collection runs.

Duplicate or Conflicting Mappings

Add SysTrack Sensor Event TO iPaaS.com brings SysTrack sensor events into iPaaS.com and seeds the two automation control fields this collection reads and writes. It runs in the opposite direction and does not conflict with this collection — the two are designed to work as a pair.

Run-Once Guard

This collection does not use collision handling. Repeat dispatch is prevented by the mapping filter described below, which reads the SysTrack Sensor Automation Batch Id custom field: a message that already carries a batch identifier is skipped, so the same remediation is not dispatched twice.

No Unmapped Field Overwrite Risk

Because the outbound path issues a remediation request rather than replacing a SysTrack record, no SysTrack field is overwritten and no unmapped field is cleared. Fields present in SysTrack but absent from this collection are unaffected. The only change to iPaaS.com data is the write-back of the batch identifier and the initiated flag on the originating message.

Supported Child Collections

None. This collection has no dependent child collections.

System Caveats

SysTrack Caveats

An approved automation must exist for the sensor: SysTrack can only run remediation it already has configured. If the sensor has no automation matched to it for that system, the inbound transfer leaves SysTrack Sensor Automation 1 Sensor Id empty and this collection has nothing to dispatch. A message arriving with that field empty is an alert for which no remediation is available.
The dispatched automation may not match the alerting sensor: the SysTrack API does not relate a triggered sensor's name to an automation's name; only their identifiers are available, and the only automation values provided are the identifiers needed to execute an autofix. A message generated for one sensor may therefore carry an automation intended to resolve a different sensor's issue, and this collection dispatches whatever identifier SysTrack Sensor Automation 1 Sensor Id holds. Because a dispatch runs a real remediation on a real endpoint, subscribers or their MiSP should confirm in SysTrack that the referenced automation addresses the condition described in the message before triggering it, and should not present the transfer as a guaranteed fix for the alert the reader is looking at.
Acceptance is not completion: the batch identifier returned by SysTrack confirms the remediation was accepted and queued, not that it finished or resolved the underlying condition. Check the outcome of the run in SysTrack.
No sandbox environment: SysTrack does not offer a separate sandbox or test tenant. Any dispatch made while validating this collection runs a real remediation against a real endpoint. Validate against a small, low-risk set of systems before enabling automatic outbound transfers broadly.
Concurrency is governed by the subscription's throttle settings: SysTrack does not publish a per-tenant request quota for this path. Rather than dispatching a large backlog of remediations at once, stagger manual runs and review the concurrent connection and concurrent batch execution values on the subscription before a bulk push, so a mass dispatch does not overwhelm the tenant or the monitored endpoints.

iPaaS.com Caveats

The message must have come from SysTrack: this collection dispatches remediation for an existing sensor event. A Message created directly in iPaaS.com with no SysTrack origin has no sensor, no system, and no stored link, and cannot be transferred.
The write-back is the only change to iPaaS.com data: a successful dispatch updates SysTrack Sensor Automation Batch Id and SysTrack Sensor Automation Initiated on the originating message. Nothing else on the Message is modified.
Clearing the batch identifier re-opens the message for dispatch: the run-once guard depends on SysTrack Sensor Automation Batch Id holding a value. If that field is emptied on a message that has already been actioned, the message passes the filter again and a second remediation is dispatched.

Setup Requirements

The full step-by-step is in the SysTrack Installation Instructions article; this section covers what this collection specifically depends on.

SysTrack Configuration

The SysTrack connection must be authorized to run an autofix for a sensor automation on a monitored system. Authentication is by a SysTrack service account; see the SysTrack Installation Instructions and SysTrack Connections and Settings articles for the values to gather.

iPaaS.com Configuration

Enable the outbound transfer. Outbound transfers are enabled in the subscription's Outbound Data Flows section by subscribing to the iPaaS.com Message Update outbound trigger. No automatic transfers occur until that subscription is enabled. Manual Sync is available regardless.
The control custom fields must exist on the iPaaS.com Message before the first transfer. SysTrack Sensor Automation Batch Id and SysTrack Sensor Automation Initiated must exist, because the mapping filter and the write-back both depend on them; if they do not exist the filter cannot evaluate and no message is dispatched. The ExternalId and Id mappings that carry the write-back must not be altered.
The source custom fields must be populated. SysTrack Sensor Automation 1 Sensor Id, SysTrack Sensor Automation 1 Application Id, and SysTrack System Id must hold values, which happens automatically when the message arrives through Add SysTrack Sensor Event TO iPaaS.com.

Integration Flow

The trigger fires — either the iPaaS.com Message Update outbound trigger or a Manual Sync on the Message id. The mapping filter is evaluated: a message whose SysTrack Sensor Automation Batch Id is unset or empty passes; a message that already carries a batch identifier is skipped, so the same remediation is not dispatched twice.
The integration confirms the message is linked to a SysTrack sensor record and resolves that link. If no link exists, or the link is not in the expected sensor-and-system form, the transfer stops with an error and nothing is sent to SysTrack.
It sends the remediation request, naming the sensor automation to run (SysTrack Sensor Automation 1 Sensor Id), the application the automation belongs to (SysTrack Sensor Automation 1 Application Id), and the monitored system to run it on (SysTrack System Id). If the automation identifier is empty, the transfer stops before contacting SysTrack and reports an error; the message is treated as an alert with no remediation available.
If SysTrack accepts the request and returns a batch identifier, the integration writes that outcome back onto the originating Message, setting SysTrack Sensor Automation Batch Id to the returned identifier and SysTrack Sensor Automation Initiated to true. Those two fields are the subscriber-visible record of the round trip.

Mappings

This collection dispatches a single remediation from one iPaaS.com Message and records the outcome back on that message. The subsection below lists every field mapping; the run-once mapping filter is described first.

Update SysTrack Autofix Run FROM iPaaS.com

iPaaS.com data type: Message

Mapping Filter

A mapping filter is applied, and it acts as the run-once guard for this collection. The filter reads two Message custom fields — SysTrack Sensor Automation Initiated and SysTrack Sensor Automation Batch Id — but it is the presence or absence of a value in SysTrack Sensor Automation Batch Id that decides the outcome. The filter applied is:

var initiated = GetCustomFieldValue(CustomFields, "SysTrack Sensor Automation Initiated");
var runId = GetCustomFieldValue(CustomFields, "SysTrack Sensor Automation Batch Id");// Only run once when the SysTrack Sensor Automation Initiated
if(string.IsNullOrEmpty(runId))
  return true;
return false;
//Custom fields will be true with batch id if already run

Filter Description. The filter returns true, allowing the message to be dispatched, only while SysTrack Sensor Automation Batch Id is unset or empty, which it treats as "not yet dispatched". Once SysTrack has returned a batch identifier and the integration has written it back to that field, the filter returns false and the message is skipped on any later run, so the same remediation is not dispatched twice. Both custom fields must exist on the iPaaS.com Message before the first transfer, or the filter cannot evaluate and no message is dispatched. If the batch identifier is later cleared on a message that has already been actioned, the message passes the filter again and a second remediation is dispatched.

Mapping Type	Source Field (iPaaS.com)	Destination Field (SysTrack)	Description
Field	SysTrack Sensor Automation 1 Sensor Id	SensorId	Required. Tells SysTrack which of the automations recorded on this message the remediation should run against, sourced from the SysTrack Sensor Automation 1 Sensor Id custom field, which Add SysTrack Sensor Event TO iPaaS.com populates from the first automation matched to the sensor result. The inbound collection can capture more than one automation, but this collection dispatches automation 1 only. If it is empty the integration stops before contacting SysTrack and reports an error; treat an empty value as an alert with no remediation available rather than a transfer failure. A populated value is not a guarantee the automation matches the alert — SysTrack does not relate a sensor's name to an automation's name — so confirm in SysTrack what the automation does before triggering it.
Field	SysTrack Sensor Automation 1 Application Id	ApplicationId	Required. The application value that scopes the autofix request, sent with every remediation and sourced from the SysTrack Sensor Automation 1 Application Id custom field, which the inbound collection populates. The integration supplies the same fixed application value on every request, so it does not vary from one message to the next. If it is empty, SysTrack cannot associate the request with an application and the request is rejected or has no effect. Because the value is carried forward from the inbound transfer, it is normally correct without action; it needs attention only if the inbound mapping has been changed or cleared.
Field	SysTrack System Id	Systems	Required. Identifies the monitored SysTrack system — the endpoint — the remediation should run on, sourced from the SysTrack System Id custom field, which the inbound collection populates. SysTrack has no target for the remediation without it, so an empty value results in a rejected or ineffective request rather than a queued automation. Normally correct without action; needs attention only if the inbound mapping has been changed or cleared.
Dynamic Formula	Dynamic Formula	ExternalId	Required. Resolves the SysTrack identifier already recorded against this iPaaS.com Message and returns it, so the request is tied to the SysTrack sensor record the message came from. The identifier combines the sensor and the monitored system, as described under ID Format. This mapping is what establishes that the message genuinely corresponds to a SysTrack sensor record before any remediation is requested, and it must not be altered. If the message has no recorded identifier, the transfer stops with an error and no remediation is requested — which in practice means the message must have arrived through Add SysTrack Sensor Event TO iPaaS.com first. Only the presence of the identifier is checked, not its form.
Dynamic Formula	`Id`	Id	Required. Passes the iPaaS.com Message identifier through unchanged. It is not part of the remediation request sent to SysTrack; the integration uses it to find its way back to the originating Message after SysTrack accepts the request, so it can write the outcome there. On a successful dispatch the integration writes the batch identifier to SysTrack Sensor Automation Batch Id and sets SysTrack Sensor Automation Initiated to true on the message this identifier points to. This mapping must not be altered; without it the remediation may still be accepted by SysTrack, but the confirmation cannot be written back, and the message's unset batch id would let the same remediation be sent again.

The ExternalId mapping is a Dynamic Formula that looks up the stored SysTrack identifier for the message; it returns no value when no identifier is found, which produces the linkage error above rather than a silent skip. The Id mapping passes the Message identifier straight through.

Error Handling

Error messages this collection can raise — including the linkage error when a message has no stored SysTrack identifier, the error when the automation identifier is empty, and the connection and authentication errors common to every flow — are cataloged in the SysTrack Error Messages article, under the Update SysTrack Autofix Run FROM iPaaS.com flow. Errors appear on the iPaaS.com Dashboard under Integration Monitoring, in the Error Logs. A message that passes the run-once filter but has an empty automation identifier stops before contacting SysTrack and reports an error; a message already carrying a batch identifier is skipped silently by the filter and is not an error.

Testing & Validation

Test Scenarios

Dispatch a remediation from a linked message. Choose an iPaaS.com Message that arrived through Add SysTrack Sensor Event TO iPaaS.com, carries a populated SysTrack Sensor Automation 1 Sensor Id, and has an empty SysTrack Sensor Automation Batch Id. Run Manual Sync with its Message id. Expected outcome: SysTrack accepts the request and returns a batch identifier, which is written to SysTrack Sensor Automation Batch Id, and SysTrack Sensor Automation Initiated is set to true on that message.
Confirm the run-once guard. Run Manual Sync again on the same message. Expected outcome: the message is skipped — it no longer passes the filter, because its batch identifier is now set — and no second remediation is dispatched.
Attempt a message with no stored SysTrack link. Create a Message directly in iPaaS.com, or use one with no recorded SysTrack identifier, and run Manual Sync. Expected outcome: the transfer stops with an error and nothing is sent to SysTrack, visible under Dashboard / Integration Monitoring / Error Logs.
Attempt a message whose automation identifier is empty. Choose a linked message that arrived with SysTrack Sensor Automation 1 Sensor Id empty — an alert for which SysTrack had no matched automation — and run Manual Sync. Expected outcome: the integration stops before contacting SysTrack and reports an error; nothing is dispatched.
Confirm re-open on cleared batch identifier. On an already-actioned message, clear SysTrack Sensor Automation Batch Id and run Manual Sync. Expected outcome: the message passes the filter again and a second remediation is dispatched — confirming why the field must not be cleared on actioned messages.

Validation Checklist

Only messages with an empty SysTrack Sensor Automation Batch Id are dispatched; already-actioned messages are skipped.
A successful dispatch writes the returned batch identifier and sets SysTrack Sensor Automation Initiated to true on the originating message.
A message with no stored SysTrack link, or an empty automation identifier, stops with an error and dispatches nothing.
The SysTrack Sensor Automation Batch Id and SysTrack Sensor Automation Initiated custom fields exist on the Message before the first transfer, and the ExternalId and Id mappings are unaltered.
The batch identifier is understood as acceptance, not completion — the outcome of the run is confirmed in SysTrack.

Additional Notes

This collection executes a remediation in SysTrack; it does not modify, acknowledge, or close the sensor event that raised the alert, and a dispatch cannot be recalled from iPaaS.com once SysTrack has accepted it. The inbound side of the pair — how sensor events become iPaaS.com Messages and how the automation identifiers are captured — is documented in the SysTrack to iPaaS.com Sensor Event Mapping Documentation article. For the platform boundaries this collection inherits from SysTrack, see the SysTrack Integration Known Limitations article.

SysTrack Autofix Run From iPaaS.com Mapping Documentation