* Marketing Cloud Intelligence *

*** Important change for:  Update Permissions for TriggeredSend SOAP API by June 19, 2026 ***On June 19, 2026, Salesforce is changing the permission requirements for executing TriggeredSend SOAP API calls within Marketing Cloud Engagement.  

Required Actions

Beginning on June 19, only API users and installed packages that have the required permissions can make TriggeredSend calls via the SOAP API. Depending on your authentication method, update your permissions using these steps.

Installed Package

1. From Setup, in the Quick Find box,enter Installed Packages, and then select Installed Packages.
2. Select the package to modify.
3. In the Components section, click Edit for your integration.
4. In the Channels section, under Email, select Read, Write, and Send.
5. Save your changes.

Username and Password

This step applies only to users with the API User setting enabled. If a user doesn’t have this setting enabled or doesn’t perform triggered email sends, no action is required.

1. From Setup, in the Quick Find box, enter Users, and then select Users.
2. Select a user, and then click Manage Roles.
3. Select Edit Permissions.
4. In the Email | Interactions | Messages | Email section, next to Triggered, select Allow.
5. Save your changes.

Follow the step-by-step instructions in the Knowledge Article to update permissions for packages and API users.

Impact of Noncompliance

If you don't update the permissions by June 19, 2026, your TriggeredSend SOAP API calls will not send emails and return an API Permission Failed error.

Why Are We Making This Change?

To provide a more predictable and streamlined operational environment, Salesforce is aligning the permission requirements for TriggeredSend SOAP API calls used throughout Marketing Cloud Engagement. This change extends the same access controls from our other messaging features to your integrations.

What to Expect

After you update your permissions, your TriggeredSend SOAP API calls continue to function with no impact on the email delivery experience for your recipients.

To ensure uninterrupted service, update your integration permissions by June 19, 2026.

Need help?

Connect with Agentforce on Salesforce Help.

#Marketing Cloud

Can anyone translate this into a usable date for the day field?  

2026-02-05T17:44:28.265Z 

Just a few of the things I've tried:

• changing the formatting in the preview to different syntaxs like dd-MM-yyyy'T'HH:mm:ss.SSS'Z'
• PARSEDATE((SUBSTITUTE(csv['creation_time'],'T',' ')),'dd-MM-yyyy HH:mm:ss.SSS')
• PARSEDATE(SUBSTITUTE(csv['creation_time'],'T',' '),'dd-MM-yyyy HH:mm:ss.SSS z')
• PARSEDATE(csv['creation_time'],'dd-MM-yyyy'T'HH:mm:ss.SSS z')
• PARSEDATE((LEFT(csv['creation_time'],10)),'yyyy-MM-dd')
• PARSEDATE(orig-date,yyyy-MM-dd) 
  var orig-date = LEFT(csv['creation_time'],10);

Those have all passed validation,  but then when I run a evalution, I get a message like this: 

📣 Connections "CNX" call for speakers is LIVE! 

The Community Hub is back! Connections is back! The stages are ⭐️ BIGGER ⭐ than last year! If you're leading real change in email, design, AI, or customer connection, we want to hear from you. Have you recently built something that made your campaigns better, your customers happier, had a I wish I could share how I solved it moment? Bring it to the stage at Connections: http://sfdc.co/GVsqB

We're looking for that bold, no fluff, bring on that good stuff content. Created by you! Not AI. Not recycled. 

If you want to share ideas and best practices on: 

➡️  Email design/template 

➡️  Email accessibility 

➡️  A/B testing 

➡️  Deliverability 

➡️  Email authentication 

➡️  Templates that scale 

➡️  Email Gotcha's 

➡️  Data strategy, etc. 

Pro Tip: 

• If you want to present at the Community Hub, make sure to select “Community Networking” in the “What is the suggested length of time for your proposal?” field. 
• If your session is selected you will receive a complimentary speaker pass

Let’s make this another unforgettable Connections!  #Connections