anne_sample_f5

It's been a few years, but I did this exact thing using Zapier. In my case I was maintaining subscription preferences across multiple records. I had a smart campaign set up so that when someone filled out our preference form, if they were a possible duplicate, it would trigger a webhook into Zapier ...

No, I am using Update User Attribute. I'm updating system users, not person records, which is why I don't have the ID - it's directly in the URL. It is a datetime according to the documentation: expiresAt (string) - Date and time when user login expires. Example: yyyy-MM-dd'T'HH:mm:ss.SSS't'Z

That was the date I tried using first! I even tried more than one date converter to generate it and none of them actually work. I feel like I'm losing my mind. I copied from your post to try again and it still doesn't work. I'm so confused. My post body:{"action": "createOrUpdate","input": [ {"expi...

Sorry, I don't understand how to resolve that code into an actual date. I spent like two hours trying to figure it out yesterday.

Thanks - I put in an Idea for the suggestion but I'll take a look at your post about it too!

Thanks, I realized after posting that the old UI was slightly more efficient, but was realllllly hoping there was a method that could deal with more than 50 at a time. I'm dealing with literal thousands of assets here so even 50 at a time is pretty brutal. I didn't see it in the endpoint list either...

I just had this issue. Talk to Marketo support and they can help you fix it!