Moveworks Integration Known Limitations
This document lists the known limitations of the Moveworks integration and what each means for you as a subscriber.
This integration was developed with a partner with whom iPaaS.com does not currently have an active relationship, and there is no live sandbox environment for continuous testing. As a result, iPaaS.com cannot keep the integration continuously updated and tested on an ongoing basis.
What this means for you: If you want to use this integration, iPaaS.com will perform a Quality Assurance (QA) review after you connect Moveworks to iPaaS.com. Allow for a brief delay while the connection is validated. For questions about the partnership status or this process, contact partnerships@ipaas.com.
Outbound Only (Messages From iPaaS.com)
The integration sends messages from iPaaS.com to Moveworks. It does not retrieve data from Moveworks, poll for changes, or support updating or deleting a message after it has been sent.
What this means for you: Use this integration to deliver messages to Moveworks recipients. It cannot pull Moveworks data into iPaaS.com, and a message cannot be edited or recalled through the integration once it has been sent.
Recipients Are Required
Every message must include one or more recipient email addresses. The template provides a Recipients mapping that reads a comma-separated list of addresses from a custom field.
What this means for you: Configure the Recipients mapping so each message carries at least one recipient email address. A message with no recipients will be rejected by Moveworks.
An Event ID Is Required and Must Exist
Messages are sent for a specific Moveworks event, identified by an Event ID. The event must already be defined in your Moveworks Events Workspace.
What this means for you: Define the event in Moveworks and map its Event ID. If the Event ID is missing or does not exist in Moveworks, the message will not be delivered.
Template Placeholder Values to Replace
The template ships example values that you must review and replace for your environment before enabling the collection:
Event ID — the EventId mapping ships a sample value (aa501bbc-695d-497d-8c55-3bd280cc7a68). Replace it with your own Moveworks Event ID (the event must exist in your Events Workspace).
Recipients custom field — the Recipients formula reads an example custom field named "Moveworks Message Recipients". Ensure a custom field with that name exists, or adjust the formula to read your own recipient source.
What this means for you: Until these placeholders are replaced, messages will target the wrong or a non-existent event and may not resolve recipients. Replace them as part of installation, before enabling the collection.
No Mapping Filter Is Included by Default
The template mapping collection does not include a filter, so by default every Message created in iPaaS.com is eligible to transfer to Moveworks.
What this means for you: Add a mapping filter that matches your business rules so that only the intended messages are sent. Without a filter, messages you did not intend to send may be transferred to Moveworks.
Duplicate Prevention Depends on the Id Mapping
Moveworks does not return a unique identifier for a sent message. The integration records the iPaaS.com message Id as the Moveworks message Id (via the Id mapping) to keep a one-to-one relationship and prevent the same message from being sent twice.
What this means for you: Do not remove the Id mapping from the template. If it is removed, the same message can be sent to Moveworks more than once.
No Bulk Historical Sync
The integration does not provide a bulk-pull or initialization mode for sending a large backlog of messages at once.
What this means for you: To send a large set of messages as a one-time operation, use the bulk sync using Postman workflow.
No Collision Handling or Record Matching
Collision handling and record matching are not supported for messages. Message identity is maintained only through the Id mapping described above.
What this means for you: There is no duplicate-detection step beyond the Id mapping. Manage which messages send by configuring the mapping filter rather than relying on collision handling.
This release of the Moveworks integration has 9 known limitations.