#Sales Cadences0 人がディスカッション中

Hi Everyone,

I am trying to implement WhatsApp messaging through Salesforce Sales Engagement Cadences using WATI API integration, but I am facing issues with Cadence Step Flow execution and variable passing.

Current Architecture:

Contact Record Triggered Flow

→ Add Contact to Cadence

→ Cadence Step Flow

→ Apex Invocable Action

→ Queueable Apex

→ WATI API Callout

My goal:

When a contact reaches a cadence step, I want to automatically send a WhatsApp template message through WATI.

What I have implemented:

1. Cadence Step Flow
2. Apex Invocable Method
3. Queueable Apex with Database.AllowsCallouts
4. Named Credential for WATI
5. Formula payload generation in Flow

Current Flow Payload:

959585****|||abd|||{"name":"Rakesh"}

Invocable Apex:

public with sharing class WatiWhatsAppService {

public class Request { @InvocableVariable(required=true) public String rawInput; } @InvocableMethod( label='Send WATI WhatsApp Message' description='Cadence-compatible WhatsApp action.' ) public static void sendWA(List<Request> requests) { List<String> rawInputs = new List<String>(); for(Request req : requests){ if(String.isNotBlank(req.rawInput)){ rawInputs.add(req.rawInput); } } System.enqueueJob(new WatiQueueable(rawInputs)); } 

}

Issue:

• Cadence Step Flow is not executing automatically
• Sometimes the flow step does not launch from cadence
• Input variables like MobilePhone and FirstName were initially blank
• I fixed variable mapping using input variables
• Formula payload is now generating correctly
• Apex action now appears in flow correctly
• However, cadence screen flow execution itself is inconsistent

Questions:

1. Does Cadence Step Flow require manual user interaction from Work Queue to execute?
2. Is Cadence Step Flow suitable for backend API automation like WhatsApp sending?
3. Has anyone successfully implemented automatic WhatsApp sending from Sales Cadence?
4. Would Record Triggered Flow + Apex be a better architecture than Cadence Step Flow?
5. Are there limitations with Invocable Apex inside Cadence Step Flow?

Any guidance or recommended architecture would be very helpful.

Thanks! 

#Salesforce Developer #Apex #Sales Cadences #Flow

There is the ability to report on Cadences with Monthly metrics (seen below), but the business folks at the org I'm supporting want to see Daily or Weekly cadence metrics. Is this possible? I haven't seen a way to accomplish this via custom Report Types.

Also, is this a normal/reasonable request? I don't see anyone else questioning these missing metric intervals in the community at all which leads me to believe that standard sales orgs are fine with monthly cadence reporting without getting more granular. Daily/Weekly reporting all seems to be done at the User/Rep level.

#SalesEngagement #Sales Cadences #HVS Sales Cadences #Reporting

Our company recently added Salesforce Sales Engagement. As we've been working with it, we've discovered Action Buttons called "Add to Cadence" and "Remove from Cadence" that can be added to the Contacts and Leads tabs.   I adjusted the formatting in the page layouts to display the buttons, but we've run into a problem.

The "Add" and "Remove" cadence buttons appear in list views of the Leads and Contacts. On individual Leads or Contacts, the "Add" button is visible, but not the "Remove" button.

Our staff who use Sales Engagement are able to add and remove prospects from the cadences and can see the buttons when they're in Sales Engagement.   

As I've been looking into this, I found some documentation that said there was a version of Sales Engagement for certain variations of Salesforce, but not for all.  We use Enterprise Edition, which required the purchased add-on of Sales Engagement. 

Question about the cadence buttons - on regular Leads and Contacts, are they there for the other versions of Salesforce, but won't work with Enterprise Edition?

Is there any other reason the buttons won't appear when I add them to the tabs?

Thanks.

#Sales Cadences