Setting Up m3sh Webhook Triggers

Documentation Index

Fetch the complete documentation index at: https://docs.m3ter.com/llms.txt

Use this file to discover all available pages before exploring further.

• Overview
• Prerequisite Configuration
• Creating m3sh Webhook Triggers
• Testing Active m3sh Webhook Triggers
• Implementation Notes
• Monitoring Execution Logs

​

Overview

• Scheduled Polling. Automated batch jobs that run on a configurable schedule - at 15, 30, or 60 minute intervals.
• Manual/On-Demand Execution. Administrator-initiated webhook sent from the UI.
• Flow/Apex Invocable Actions. Developer-triggered webhook sent from Salesforce Flows or custom Apex code.

​

Prerequisite Configuration

• Enabling m3sh Webhook Triggers
• Configuring Remote Site Settings

​

Enabling m3sh Webhook Triggers

1. In your Salesforce Org, navigate to Setup > Custom Settings > m3 Org Settings > Manage > Edit:

2. Check the Enable m3sh Triggers box and then select Save.

​

Configuring Remote Site Settings

1. In your Salesforce Org, navigate to Setup > Security > Remote Site Settings:

2. Under Remote Site Settings > Remote Site Details enter these settings for the m3ter Webhook endpoint:

• Remote Site Name: m3ter_Webhook
• Remote Site URL: https//<m3ter_Org_ID>>.webhook.m3ter.com
• Active: TRUE

​

Creating m3sh Webhook Triggers

1. In your Salesforce Org, navigate to the m3ter Admin app.
2. Under Setup, select the m3sh Triggers tab:

3. Select Create New Trigger. The tab adjusts and you can enter the details of the new Trigger:

• Use the m3ter Workflow drop-down to select the m3sh Workflow in your m3ter Organization that will be triggered. (Required)
• Enter the Webhook URL.
• Use the Salesforce Object drop-down to select which object’s data will be sent to the selected m3sh Workflow. (Required)
• Select Active to enable the new Trigger.

4. Select Create. The new m3sh Trigger is saved:

• Note that if you want to review or edit an active m3sh Webhook Trigger, you can return to the m3sh Triggers tab and use the Active drop-down to select the Trigger:

• Select Edit if you want to update the configuration of the Trigger.
• Use the Active switch if you want to deactivate the Trigger.

​

Testing Active m3sh Webhook Triggers

1. In your Salesforce Org, navigate to the m3ter Admin app.
2. Under Setup, select the m3sh Triggers tab.
3. In the Active drop-down list, select the m3sh Webhook Trigger. The Trigger configuration is shown and you can read-off:

• The Salesforce Object the Trigger is configured to transfer data for to the m3sh Workflow - in this example Account.
• The Status of the Trigger - in this example Never Run.
• The Webhook URL defined for the Trigger.

4. Select Test. A Test Webhook modal opens:
5. On the modal, select the Account you want to run the test for, and then select Run Test:

• A successful test should return 200 http status code and a response such as the following example:

​

Implementation Notes

• Adding Webhooks as Triggers for m3sh Workflows
• Implementation Patterns - Options

​

Adding Webhooks as Triggers for m3sh Workflows

​

Implementation Patterns - Options

• Use in Salesforce Flows
• Use in Apex
• Scheduled Apex Jobs

​

Salesforce Flows

• Config Developer Name:
  • You can find this by navigating to the underlying CMDT record, that is from Setup > Custom Metadata > find** m3sh Trigger Configs** and select Manage Records.
• Record IDs:
  • The Ids for the Salesforce Records to send to the Webhook. These must be of the same type as the configured Salesforce Object.
  • The platform will send each record in a separate transaction.

​

Apex

// Trigger delegation pattern
trigger AccountTrigger on Account (after insert, after update) {
    AccountTriggerHandler.handleAfterInsertUpdate(Trigger.new, Trigger.oldMap);
}

// Trigger Handler class
public class AccountTriggerHandler {
    
    public static void handleAfterInsertUpdate(List<Account> newRecords, Map<Id, Account> oldMap) {
        if (Trigger.isInsert || (Trigger.isUpdate && needsSync(newRecords, oldMap))) {
            Set<Id> recordIds = new Map<Id, Account>(newRecords).keySet();
            sendToWebhookAsync(recordIds, 'Account_Realtime_Sync');
        }
    }
    
    @future(Callout=true)
    public static void sendToWebhookAsync(Set<Id> recordIds, String configDeveloperName) {
        // Note: In subscriber orgs, use the namespace prefix 'm3' before class names
        // Example: m3.M3shSendWebhookService for production installations
        
        m3.M3shSendWebhookService.M3shWebhookRequest request = new m3.M3shSendWebhookService.M3shWebhookRequest();
        request.configDeveloperName = configDeveloperName;
        request.recordIds = new List<Id>(recordIds);
        
        List<m3.M3shSendWebhookService.M3shWebhookResult> results = 
            m3.M3shSendWebhookService.sendToWebhook(new List<m3.M3shSendWebhookService.M3shWebhookRequest>{ request });
        
        if (!results.isEmpty() && !results[0].success) {
            System.debug(LoggingLevel.ERROR, 'Webhook failed: ' + results[0].message);
        }
    }
    
    private static Boolean needsSync(List<Account> newRecords, Map<Id, Account> oldMap) {
        // Implement your logic here
        return true;
    }
}

• Note that given the service makes callouts, it will need to be wrapped in a @future(Callout=true) method.
• See: https://help.salesforce.com/s/articleView?id=000386018&type=1

​

Scheduled Apex Jobs

• Query all the fields for the records from the associated Salesforce Object that have been updated/created since the last run.
• Prepare the request payload.
• Send the records to the Webhook endpoint.

​

Monitoring Execution Logs

• Scheduled - From scheduled batch jobs.
• Manual - From admin UI Run Now or Test buttons.
• Invocable Action - From Flow or Apex invocations.