Changes to list membership actions in the v4 Automation API

[Dadams]

What's changing?

The “alter list membership” action ("actionTypeId": "0-13") is being split into two distinct actions: “add to list” (actionTypeId 0-63809083) and “remove from list” (actionTypeId 0-63863438). These new separate action types will be used instead of including the "operation": "REMOVE" or "ADD" in the fields data for the step.

Previously, this was the format for a step to remove a record from a list:

{
  "actionId": "3",
  "actionTypeVersion": 0,
  "actionTypeId": "0-13",
  "fields": {
    "operation": "REMOVE",
    "list_id": "1234"
  },
  "type": "SINGLE_CONNECTION"
}

This is the updated format to remove a record using the new action type:

{
  "actionId": "3",
  "actionTypeVersion": 0,
  "actionTypeId": "0-63863438",
  "fields": {
    "listId": "1234"
  },
  "type": "SINGLE_CONNECTION"
}

This change is part of a broader effort to make actions more consistent, so that each operation has its own action type instead of using an action type with a separate operation field.

When is this happening?

This change has already been applied to existing workflows, resulting in updated API responses reflecting the new action types.

While we recommend updating to the new action types as soon as possible, the “alter list membership” action ("actionTypeId": "0-13") can still be used for now. Keep in mind that any workflows created or updated using this type will be converted to the appropriate separate action types, meaning that the API response for the workflow will not match the original JSON sent by your integration.

See the Workflows API documentation for more details. Please let us know if you have any questions by replying below.