Need guidance for updating outsourced employee accounts from workflow with multiple PATCH requests and different source paths

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi ,

TestUpdateforServiceNow20260513
TestUpdateforServiceNow202605132285×1917 248 KB

I am working on a SailPoint Identity Security Cloud workflow to update outsourced employee data through an External Trigger.

The external system sends a payload containing multiple attributes that need to be updated. Based on the payload, the workflow loops through the update items and sends PATCH requests.

Current design:

  1. External Trigger receives the update payload.

  2. Workflow gets the identity/account details.

  3. The outsourced employee may have accounts on two different sources.

  4. Inside the Loop, I check the attribute/type and send a PATCH request to the relevant source/account.

  5. Some updates go to one source, and other updates go to another source.

  6. The issue is that I may send multiple PATCH requests to the same account during the same workflow execution.

The problem I am facing is that when multiple PATCH requests are executed against the same account, I sometimes see conflicts or unexpected behavior. I understand that the Loop operator executes items in parallel and does not guarantee order, so multiple updates to the same account may happen at the same time.

In my case, I cannot simply use one static PATCH body because the attributes have different target paths depending on the source and attribute type.

For example, the external payload may contain updates like:

[
  {
    "attribute": "manager",
    "value": "managerIdentityId"
  },
  {
    "attribute": "approvalManager",
    "value": "approvalManagerIdentityId"
  },
  {
    "attribute": "endDate",
    "value": "2026-06-30"
  }
]

But each attribute may need to be patched using a different path or sent to a different source/account.

My questions are:

  1. What is the recommended workflow design when I need to update multiple attributes on the same account but each attribute may have a different PATCH path?

  2. If yes, what is the best way in ISC Workflows to dynamically build a JSON Patch array from the incoming payload?

  3. Is there any supported way to force Loop iterations to run sequentially instead of in parallel?

  4. For a user who has two source accounts, what is the best practice to group updates by source/account and then send one PATCH request per account?

2

Hi,

Does the target support PUT operation by any chance ? That will solve all your problems. But with PATCH it becomes a bit tricky to only sent 1 attribute at a time.

Thanks

3

Hi, I know that PUT request will be easier but the issue that every time the workflow when triggered i don’t know which attribute need to be updated or at this case i can use many PUT requests instead of Patch