Hi @Luca_Lattarini - both of these integrations are pretty complex and I would recommend using Adobe Consulting or a competent Adobe Solution Partner. I have done both of these and even with the help of the Adobe Pipeline/Triggers integration team it was a struggle to implement properly as the docum...

Hi Jon - the typology hack definitely works. Added a Delivery Code to the built-in template so I could find it. Do you have any idea how to get access to the dataSource data from within the typology code? Cheers Darren

Hi @Sukrity_Wadhwa - I havent actually had a chance to test this out yet. I'll try to post something up when I do get a chance 

I would talk to your Adobe rep or your partner that is assisting you with the installation. They should help you locate your Client name

Hi @Luca_Lattarini - your client name is usually visible after the "@" symbol in the URL when you log on to Experience Cloud instance. e.g._domainkey isn't really replaced with anything, but the other values for subdomain.com etc on either side of the CNAME are replaced with your provisioned sending...

@DimitrisChatzosThe full code you need to insert after the delivery isvar delivery = NLWS.nmsDelivery.load(vars.deliveryId); delivery.operation_id=instance.operation_id; delivery.workflow_id=instance.id; delivery.save();

Thanks Jon - nice idea. Let me have play with it and see what I can get working. Slack also allows email integration so I can just push the alert messages directly into a Slack channel so I'm invetigating that as well. Cheers Darren

I am in the process of setting up Slack webhooks for all of our Campaign alerting. However, I can't find if its possible to intercept any alerts generated to the workflow supervisor. It looks like they are generated directly by the server and not processed in any workflows.Right now, the only way I ...

You can try using mutibyte unicode escaping in your JSON output e.g. "fare": " price at \u20ac 20,00 with discount \u20ac 34"

Hi @kkedem - we implemented the typology list as you mentioned. This was fine but had to be managed for any new numbers on the "allow" list.One other thing we did on our non-prod environments was to invalidate the mobile of any recipients we didn't want to contact. On our daily data import, we just ...