Chris_Francis

Can you really still not see WHO triggered a campaign from SFDC? this is a huge limiting factor of MSI.

Also after I was finally able to get the calls to work, I realized how terriblly inefficient my orignal code was. Looked at @SanfordWhiteman article https://blog.teknkl.com/and-yes-flowboost-can-be-that-webhook-aggregator/ and refactored to be more Promise oriented. Here is the final result:const ...

I started another discussion in hopes of resurrecting the conversation in case you want to follow there if answers arise.https://nation.marketo.com/t5/product-discussions/custom-activity-datetime-attributes/m-p/326440/highlight/true#M184271

I started a new discussion in case you want to follow for potential answers. https://nation.marketo.com/t5/product-discussions/custom-activity-datetime-attributes/m-p/326440/highlight/true#M184271

I started a new thread https://nation.marketo.com/t5/product-discussions/custom-activity-datetime-attributes/m-p/326440/highlight/true#M184271 if you would like to follow there in case it gets any answers

I agree. All date time fields should be stored in UTC.

So you never got an answer to this? Because I am seeing something similar. My instance is set at EDT when I look in the admin and being that we are in June we are definitely in Eastern Daylight time I am passing 2022-06-26T21:00:00.000Zin the custom activity I am seeing 2022-06-26 16:00:00but that ...

Thanks @SanfordWhiteman That was it. Had just cloned an old webhook and was running v19.

well the entire url https://975-FPO-828.mktorest.com which is our marketo instance and should meet all of the criteria listed and yet I still get the error posted