"host": {
"connectionReferenceName": "shared_office365",
"operationId": "CalendarGetOnChangedItemsV3"
},
"parameters": {
"table": "AAMkAGQyZGYyZGM0LTE1OTAtNGU3OC1hZDViLTYzNDcwMjZjYWEyZQBGAAAAAACs0Sae0k2tTqrOIwOEQKWsBwABzLvNmSr7S4oMqDDhWDczAAAAAAEGAAABzLvNmSr7S4oMqDDhWDczAAKPjVYDAAA=",
"incomingDays": 300,
"pastDays": 50
}
}
Get calendar view of events (V3) result:
"id": "AAMkAGQyZGYyZGM0LTE1OTAtNGU3OC1hZDViLTYzNDcwMjZjYWEyZQBGAAAAAACs0Sae0k2tTqrOIwOEQKWsBwABzLvNmSr7S4oMqDDhWDczAAKPjPX4AAABzLvNmSr7S4oMqDDhWDczAAKrWTw6AAA=",
What's in my SharePoint:

Thanks! That cleared up how I should think about Apply to each and the link between the condition statement and how to update SharePoint.
However, It's a very different problem so I will likely create a new post to solve that and update here once the flow is functional. But if you're interested, here are the details of the new issue.
The Calendar id in the starting trigger isn't matching what is in SharePoint, so the condition fails every time and nothing gets updated. I selected a calendar event and checked that the Calendar Id matches the SharePoint Id info and it did. I used a Manual trigger > Get calendar view of events (V3) setup to doublecheck the ID before and after I made a change. Both times it was still the same as what's in SharePoint and not what this flow is pulling. Not sure where the other ID is coming from. I thought they were static, which is the crux of this whole flow and process.
What this flow is pulling:
When an event is added, updated or deleted (V3) - raw output
{