Hi @MikeL.53962 (Customer)​ , Thank you for reaching out to the Okta Community! 

Suspending a user in the downstream application would be dependent on the app's API and whether or not it supports such actions. 

The public references we have, typically refer to the Okta user status, not the downstream one. Example: 

Suspend User

Trigger a flow when a user is suspended in Okta API

I've checked the Workflows Discussion Group as well as the Workflows Templates list on the devforum side and haven't found an example for this particular use case, but you can post your question there to see if someone perhaps has something that helps. 

Regards.

--

Help others in the community by liking or hitting Select as Best if this response helped you.

@MikeL.53962 (Customer)​  -- You will need to refer to the vendors API documentation.

Typically an API key would require a "Custom" connection with the API Connector. The custom connection provides a Key:Value header pair. It would look something like:

• Authorization
• Bearer YourKeyValue

Okta for example doesn't use Bearer YourKeyValue it used SSWS YourKeyValue which is why it is important to see what their server expects via their documentation.

Then the next step would be to do a simple method GET query to confirm the connection is working. Example URL: https://example.com/api/v1/users/yourUserId for the service. If it returns a payload with your data you know the connection is working.

The next step would be to locate their documentation on how to deactivate/disable/delete what ever the process you need to do for a specific user account.

For example to "Deactivate" a user you may need to use the specific user ID which might be a unique value ffor their system. xx-543890 or something. Since you don't know what that value is.. can you "GET" user data with something you do know such as "Email"? And if so does that contain the xx-543890 value you need to use later for the deactivate?

Once you work out that process through your manual testing you can then automate it by leveraging an Event - Okta card monitoring for a specific event type. For example "User Deactivated". Using the card will create an Event Hook in Okta pointing to that specific Workflow. So when a user becomes deactivated the System Log event will be passed via an Event Hook to Workflows. This will inform on who the deactivated user is and can be used to perform the "manual steps" that you successfully tested previously.

If you want something like this scoped, built out, tested for you it would require a Professional Services (PS) engagement. If you are interested in a PS engagement please reach out to your Okta Account Executive.

Here are some useful links for learning workflows:

Getting Started with Okta Workflows

https://support.okta.com/help/s/article/Getting-started-with-Okta-Workflows

Getting Started with Okta Workflows Videos

https://support.okta.com/help/s/article/okta-workflows-getting-started-videos