iPaaS.com to Moveworks Message Mapping Documentation
Moveworks messages can be sent from iPaaS.com Messages. When a Message is created in iPaaS.com, the integration delivers it to one or more recipients for a specified Moveworks event. The transfer is outbound only (from iPaaS.com to Moveworks).
ID Format
Manual Sync ID Format
When transferring a message manually, enter the iPaaS.com Message internal ID in the IPAAS.COM input field on the Manual Sync page.
Example: 381443
External ID Format
Because Moveworks does not return a unique message identifier, the integration saves the iPaaS.com message Id as the Moveworks message Id (via the Id mapping). This maintains a one-to-one relationship and prevents the same message from being sent more than once.
Deleted Record Support
Outbound delete is not supported. Deleting a message in iPaaS.com does not remove or recall it in Moveworks, and delete mappings are not included in the default templates.
Custom Field Support
Custom fields are used to provide Moveworks contextual slot values. Create a custom field on the Message module whose name matches your Moveworks context slot, then map a value to it; each custom field is delivered as a slot. Custom field values can also be read inside a formula, for example:
var value = GetCustomFieldValue(CustomFields, "Moveworks Message Recipients");
Mapping Collection Status
Status: Enabled
Trigger Events: Create (Add)
Duplicate or Conflicting Mappings
Duplicate prevention is handled by the Id mapping, which records the iPaaS.com message Id as the Moveworks message Id. The integration does not provide collision handling or record matching for messages; identity is maintained only through the Id mapping. Do not remove the Id mapping.
System Caveats
Moveworks Caveats
The Event ID mapped to EventId must already exist in the Moveworks Events Workspace.
Recipients are the email addresses of the employees who should receive the message.
Moveworks returns no unique message identifier; duplicate prevention relies on the Id mapping.
iPaaS.com Caveats
Keep the Id mapping from the template so each message is sent only once.
For manual transfers, enter the iPaaS.com message internal ID on the Manual Sync page.
Setup Requirements
The subscription must be configured with the Moveworks API URL, Client ID, and Client Secret (OAuth 2.0 client-credentials). See the Moveworks Installation Instructions for how to obtain these values from Moveworks Creator Studio.
Integration Flow
A Message is created in iPaaS.com.
The mapping collection maps the message text, the target Event ID, the recipient email addresses, and any contextual slot values.
The integration sends the message to Moveworks for the specified event.
The iPaaS.com message Id is recorded as the Moveworks message Id so the same message is not sent again.
Mappings
Moveworks Message Add From iPaaS.com
No mapping filter is configured by default, so every iPaaS.com Message is eligible to transfer. Add a mapping filter that matches your business rules so only the intended messages are sent.
Description: Sends a message to Moveworks for a specified event and list of recipients, with optional contextual slot values.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Moveworks) | Description |
Field |
| MessageText | Required. The message body to send, formatted in Moveworks' version of HTML. Actual character limits can vary based on your chat platform. |
Dynamic Formula | See formula below | Recipients | Required. The list of recipient email addresses, read from the "Moveworks Message Recipients" custom field and converted to a list of strings. Placeholder value — replace during implementation: "Moveworks Message Recipients" is an example custom field name; ensure it exists or change the formula to read your own recipient source. |
Static |
| EventId | Required. Placeholder value — replace during implementation: the static value shown is an example Event ID; replace it with your own Moveworks Event ID (the event must exist in the Events Workspace). |
Dynamic Formula |
| Id | Required. Records the iPaaS.com message Id as the Moveworks message Id for duplicate prevention. Do not remove. |
Dynamic Formula | See formula below | Slots | Optional. Populates Moveworks context slots from the iPaaS.com message Detail Fields. Values here are combined with any supplied through custom fields. |
Static |
| Source System (custom field) | Optional. Demonstrates populating a context slot from a static custom field value. |
Recipients formula:
var value = GetCustomFieldValue(CustomFields, "Moveworks Message Recipients"); if (value != null && value != "") return StringListFromString(value); return null;
Slots formula:
//Adds iPaaS message detail fields as context slots
var slots = new Dictionary<string,string>();
if(DetailFields != null && DetailFields.Count > 0){
foreach(var detailField in DetailFields){
slots[detailField.Key] = detailField.Value;
}
return slots;
}
return null;Error Handling
Authentication error on save — The Client ID or Client Secret is incorrect, or the API URL is wrong. Resolution: re-enter the credentials from Moveworks Creator Studio and confirm the API URL.
Message rejected for missing recipients — The message did not include any recipient email addresses. Resolution: confirm the Recipients mapping resolves to at least one email address.
Message rejected for an invalid or unknown event — The Event ID is missing or does not exist in the Moveworks Events Workspace. Resolution: define the event in Moveworks and map the correct Event ID.
Errors appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs.
Testing & Validation
Test Scenarios
Create a Message in iPaaS.com that targets a valid Moveworks event and at least one recipient email address; confirm the message is delivered to the recipient(s) in Moveworks.
Transfer the same message again; confirm a duplicate is not sent (the Id mapping maintains the one-to-one relationship).
Transfer a message with no recipient address; confirm it is rejected and an error appears in Error Logs.
Transfer a message with an Event ID that does not exist in Moveworks; confirm it is rejected with an appropriate error.
Map a custom field whose name matches a Moveworks context slot; confirm the slot value is delivered with the message.
Validation Checklist
The Recipients mapping resolves to one or more email addresses.
The EventId mapping points to an event that exists in the Moveworks Events Workspace.
The Id mapping is present.
A mapping filter limits which messages transfer.
Additional Notes
This integration is outbound only (messages from iPaaS.com to Moveworks). For the full list of constraints, see the Moveworks Integration Known Limitations document.