We’ve added new event triggers specifically for Identity Lifecycle State changes. These triggers are now available in both the Workflows and Event Triggers, giving admins more flexibility and precision when building automated processes tied to identity state transitions.
New Capabilities
Two new workflow triggers:
Identity Lifecycle State Changed
Fires when the identity’s cloudLifecycleState attribute changes (e.g., from Active to Inactive).
(It offers a more targeted alternative to the broader Identity Attributes Changed trigger.)
Identity Lifecycle State Change Processed
Fires after the system evaluates and processes any configured actions for the lifecycle state change, even if no changes to access were made.
No immediate action is required. To start using the new triggers, navigate to Workflows or Event Triggers and select ‘Identity Lifecycle State Changed’ or ‘Identity Lifecycle State Change Processed.’
Important Dates
Sandbox Rollout: July 7th, 2025
Production Rollout: The week of July 14th
Calendar
By RSVP’ing to this event you will be reminded of this release prior.
Thanks for adding new triggeres. I see this new Identity Lifecycle State Change Processed trigger. I was looking for the documentation for this trigger and a sample payload but I was not able to find it in Workflow Triggers - SailPoint Identity Services. Can I know when this will be updated.
I still don’t understand why you guys don’t release documentation alongside the sandbox release of the functionality? Is there any actual reason for this? Just to intentionally make things more confusing and make testing new features in sandbox more difficult before prod release?
Either way we’re happy to see new triggers getting added even if one of them is a lesser copy of another existing trigger. Still patiently waiting (begging) for a generic fire and forget access request submitted trigger to be added.
We understand the desire for documentation for staging releases. However, the content at documentation.sailpoint.com is the legal warranty of the product. Since features in staging are not fully rolled out, they are not included in the legal warranty until prod releases.
We are currently investigating how we can improve our communications around upcoming releases and appreciate your patience as we continue that work.
Thanks for clarifying Rachel, that’s a very weird setup, good to hear it’s being worked on. Just a separate documentation page that’s not part of the warranty for things that are in sandbox but not production yet would be awesome.
Hi @ipobeidi ,
These are more targeted than the Attribute Changed trigger and focus specifically on lifecycle state transitions.
Think of the new triggers like this:
Identity Lifecycle State Changed - before provisioning
Identity Lifecycle State Change Processed - after provisioning
Can someone help understand why Lifecycle State Changed trigger could still be useful when the current Identity Attribute Changed trigger can be repurposed with a simple filter to only look for cloudLifecycleState? I mean, is there any difference except for the cosmetic change?
Will a lifecycle change event, trigger Identity Attributes Changed and Identity Lifecycle State Changed both and we get to choose which one is better for a use case?
Correct, if your use case only depends on the lifecycle change event, you can use the Identity Lifecycle State Changed trigger directly, rather than using Identity Attributes Changed and filtering for lifecycle state.
Thank for your quick response. Is it possible to update the JSON to include more identity fields, such as Username? The Sailpoint Identity GUID would not be useful for our use case.
By RSVP’ing to this event you will be reminded of this release prior.