Update Avatar URL for a user through Automation

I don't believe User AvatarUrl is available to be set in any APIs, so there would be no method available to set it in an automation.

Mathew D'Amico (mdamico)  I've not tested this but could you not call the rest API from within the automation?

My mistake, you are correct there are REST endpoints for setting and updating the avatar.  Those can be called from within an automation.  

I'd be interested in seeing a full example of how to do this within an Automation.

The REST API for this look geared towards a user uploading an image using the browser, and the documentation for Group Avatars and User Avatars doesn't give you info on what you'd need to pass in for FileUploadContext when you're doing this programmatically.

In an example, I'd really like to see it updating a Group/User avatar using the URL of an image elsewhere on the web via an automation script. That'd be really useful & would help a lot of people trying to figure this out.

There is a core_v2_http Script API  widget API that will assist with making a REST Request.  

If Remote Avatars are allowed for users, you should be able to just directly set the AvatarUrl to the remote Url.

If remote Avatars are not allowed, or for group Avatars (which don't support setting the Url), you would need to use the Upload options when setting the avatar.  Upload the file to temporary storage and use FileUploadContext or Get the file in Byte[] format and use FileData parameter.

I have also filed a bug to have Group and User Avatar API calls added to the Velocity APIs.  That is another option as well, to create a custom velocity API that calls the In process APis and use that in your automation.  That is what the bug will fix, in the mean time you could use your custom velocity calls.  That would make it easier than using a REST call.

I have also filed a bug to have Group and User Avatar API calls added to the Velocity APIs.  That is another option as well, to create a custom velocity API that calls the In process APis and use that in your automation.  That is what the bug will fix, in the mean time you could use your custom velocity calls.  That would make it easier than using a REST call.