• Home
/
• Working in m3ter - User Guides
/
• m3ter Connector for Salesforce

Setting Up m3sh Webhook Triggers

The m3sh Webhook Triggers capability in the m3ter Connector for Salesforce managed package offers Salesforce administrators a declarative, no-code solution to send Salesforce record data to m3sh Workflows via webhook endpoints.

This topic explains how to set up and work with the m3sh Webhook Triggers feature:

• Overview

• Prerequisite Configuration

• Creating m3sh Webhook Triggers

• Testing Active m3sh Webhook Triggers

• Implementation Notes

• Monitoring Execution Logs

Overview

The m3sh Triggers feature is built on top of the existing custom metadata framework developed for the m3ter Connector. Three distinct integration patterns are supported:

• 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.

All three patterns leverage the same underlying webhook delivery infrastructure, ensuring consistent behavior, authentication, payload formatting, and execution logging across all integration methods.

Prerequisite Configuration

There is some prerequisite configuration you'll need to perform in your Salesforce Org before creating and deploying m3sh Webhook Triggers:

• Enabling m3sh Webhook Triggers

• Configuring Remote Site Settings

Enabling m3sh Webhook Triggers

In order to create m3sh Webhook Triggers for your m3ter Connector for Salesforce, you must first enable them in the m3ter Admin App.

To enable 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

The m3sh Webhook Triggers feature will make callouts to your m3ter Organization, which means you must configure a remote site setting for m3sh Webhook endpoints.

To create a remote site setting for m3sh Webhook endpoints:

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

When you've enabled m3sh Webhook Triggers feature for the m3ter Admin App in your Connector for Salesforce, you can create m3sh Webhook Triggers.

To create a m3sh webhook trigger:

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

You can run a test of an active m3sh Webhook Trigger.

To test an active m3sh trigger:

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

This section provides further guidance on successfully implementing the m3sh Webhook Triggers feature for your m3ter Connector for Salesforce managed package:

• Adding Webhooks as Triggers for m3sh Workflows

• Implementation Patterns - Options

Adding Webhooks as Triggers for m3sh Workflows

m3sh Workflows in m3ter can be configured to use different types of Trigger, including webhooks. In addition to the setup required in your Salesforce Org when implementing the m3sh Webhook Triggers feature, you must also ensure a corresponding webhook is configured in the m3ter Console as the Trigger for the target m3sh Workflow.

The correct credentials set up is necessary for the webhook you configure as a Trigger for the m3sh Workflow, and the m3sh Webhook Triggers feature uses the same Integration Credentials setup as used in the Connector for Salesforce managed package to sign requests made to m3ter. Therefore please ensure that when setting up the webhook Trigger for the m3sh Workflow, the integration credentials used match those of the service user used to set up the sync between the m3ter Connector for Salesforce managed package and m3ter, that is, the integration credentials in the managed package.

Implementation Patterns - Options

Once a m3sh Webhook Trigger has been successfully configured and tested, you are ready to implement it in your process. Three different implementation patterns are available.

• Use in Salesforce Flows

• Use in Apex

• Scheduled Apex Jobs

Salesforce Flows

The invocable action has two required inputs:

• 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

Java:

1

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

7
// Trigger Handler class
8
public class AccountTriggerHandler {
9
    
10
    public static void handleAfterInsertUpdate(List<Account> newRecords, Map<Id, Account> oldMap) {
11
        if (Trigger.isInsert || (Trigger.isUpdate && needsSync(newRecords, oldMap))) {
12
            Set<Id> recordIds = new Map<Id, Account>(newRecords).keySet();
13
            sendToWebhookAsync(recordIds, 'Account_Realtime_Sync');
14
        }
15
    }
16
    
17
    @future(Callout=true)
18
    public static void sendToWebhookAsync(Set<Id> recordIds, String configDeveloperName) {
19
        // Note: In subscriber orgs, use the namespace prefix 'm3' before class names
20
        // Example: m3.M3shSendWebhookService for production installations
21
        
22
        m3.M3shSendWebhookService.M3shWebhookRequest request = new m3.M3shSendWebhookService.M3shWebhookRequest();
23
        request.configDeveloperName = configDeveloperName;
24
        request.recordIds = new List<Id>(recordIds);
25
        
26
        List<m3.M3shSendWebhookService.M3shWebhookResult> results = 
27
            m3.M3shSendWebhookService.sendToWebhook(new List<m3.M3shSendWebhookService.M3shWebhookRequest>{ request });
28
        
29
        if (!results.isEmpty() && !results[0].success) {
30
            System.debug(LoggingLevel.ERROR, 'Webhook failed: ' + results[0].message);
31
        }
32
    }
33
    
34
    private static Boolean needsSync(List<Account> newRecords, Map<Id, Account> oldMap) {
35
        // Implement your logic here
36
        return true;
37
    }
38
}
39

• 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

For a configured m3sh Webhook Trigger, you can to set up scheduled Apex jobs to periodically send records to the m3sh Webhook:

After selecting a Run Interval - available options are every 15 mins, every 30 mins, or every hour - select Enable Scheduled Runs:

With this feature enabled the m3ter Connector for Salesforce managed package will, for every configured m3sh Webhook Trigger:

• 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

To aid debugging and monitoring of the callouts made to m3sh Workflows, a new object and tab has been added to the m3ter Connector for Salesforce managed package. This new tab in the m3ter Admin App is called m3sh Execution Logs:

Each time a callout is made, the request payload, the response, and HTTP Status code is logged, along with other useful information like the Execution Type and name of the CMDT Config. 

The possible values for the Execution Type are listed below:

• Scheduled - From scheduled batch jobs.

• Manual - From admin UI Run Now or Test buttons.

• Invocable Action - From Flow or Apex invocations.

Additional Support