"Send From" HighLevel Setup Guide

This guide covers the Send From feature in HighLevel. First, enable the sub-account’s SEND FROM toggle so the available devices and SIMs appear. Then configure the latest myCRMSIM snapshot workflow and the updateSendFrom action. Finally, select a device or SIM for a contact and send a test message.

Important: Do not create the old external HighLevel webhook. The current setup uses the latest myCRMSIM snapshot, the Contact changed trigger, the Send from (mySMSGateway) → Has changed filter, and the updateSendFrom custom action.
1. Prerequisites

Before enabling Send From, confirm the following:
  1. The HighLevel location is connected to myCRMSIM.
  2. The required devices and SIMs are connected and online.
  3. The devices and SIMs are assigned to the correct HighLevel location or sub-account.
  4. You have access to the myCRMSIM Subaccounts Management page.
  5. You have access to HighLevel App Marketplace, Settings, Automation, and Contacts.
  6. The HighLevel connection has permission to create and update contact custom fields.
2. Enable the SEND FROM Toggle
This is the first step. Once the toggle is enabled, the Send From [mySMSGateway] field is created or synchronized in HighLevel contact records. This field displays the devices and SIMs assigned to the sub-account.
  1. Open the Subaccounts Sim page in the myCRMSIM dashboard.
  2. Find the sub-account where Send From should be enabled.
  3. Locate the SEND FROM column in the sub-account’s row.
  4. Click the SEND FROM toggle.
  5. Review the confirmation window:
    Enable 'Send From' override for [Subaccount Name]?
  6. Click Enable.
  7. Confirm that the following success message appears:
    Send From override enabled - contacts with a device selected now send from it.
After the toggle is enabled:
  • The Send From [mySMSGateway] custom field becomes available in contact records.
  • The field displays the devices and SIMs assigned to the sub-account.
  • Selecting a specific device or SIM overrides normal Message Routing for supported sending methods.
  • Selecting Automatic uses the normal assigned-user or Message Routing behavior.
Note: If the SEND FROM toggle is OFF, any device selection on the contact is ignored, and the message follows normal Message Routing.


3. Install or Update the Latest myCRMSIM Snapshot
The latest myCRMSIM snapshot is required for the Send From feature. The snapshot includes the Send From workflow and the updateSendFrom custom action

3.1 Download the Latest Snapshot Directly

You can access the latest myCRMSIM HighLevel snapshot using the following link:
Download the HL Send From Snapshot
Open the link and follow the HighLevel installation or snapshot-import instructions provided there.
After installing the snapshot, continue with Section 4: Select the myCRMSIM Telephony Provider.
3.2 If Automatic Updates Are Enabled
If HighLevel is configured to install the latest app updates automatically, wait until the latest myCRMSIM snapshot is available. After the update is applied, continue with Section 4.
3.3 Manual Reinstall or Update
If an older myCRMSIM installation is present or the latest snapshot has not been applied, follow these steps:
  1. Open the relevant HighLevel location.
  2. Open App Marketplace from the left menu.
  3. Search for and open myCRMSIM - SMS, iMessage & WhatsApp.
  4. On the app details page, click Uninstall.
  5. Select the required sub-account or location.
  6. Click Continue.
  7. Select an uninstall reason. Select Other if appropriate.
  8. Click Uninstall.
  9. Wait for the following confirmation:
    App has been uninstalled successfully
    1. Open the myCRMSIM app page again in App Marketplace.
    2. Click + Install to more sub-accounts.
    3. Select the required sub-account or location.
    4. Click Continue.
    5. Review the installation permissions.
    6. Click Allow & Install.
    7. Wait for the installation to complete.
    8. Confirm that the latest snapshot and the Send From workflow are available in the location.
    Note: If a window titled External Authentication Configuration myCRMSIM - SMS, iMessage & WhatsApp appears during installation, close it using X. Click Cancel if required.


    4. Select the myCRMSIM Telephony Provider
    The myCRMSIM telephony provider must be selected for Send From routing to work.
    1. Open Settings in HighLevel.
    2. Select Phone System.
    3. Open the Additional Settings tab.
    4. Find the Current Provider section.
    5. Locate the following provider in the Custom Providers list:
      mySMS Gateway App - SMS, WhatsApp & Message
    6. Confirm that this provider is selected and has the Default badge.
    7. Click Save.
    8. Confirm that the following message appears:
      Telephony Provider updated
    5. Configure the Send From Workflow and Action
    The latest snapshot workflow detects changes to the contact’s Send From field. The updateSendFrom custom action then applies the selected device or SIM to the routing system.
    5.1 Configure the Trigger and Filter
    1. Open Automation from the HighLevel left menu.
    2. Select Workflows.
    3. Open the workflow named Send From.
    4. Click the first trigger block in the workflow builder.
    5. Under CHOOSE A WORKFLOW TRIGGER, select Contact changed.
    6. In the FILTERS section, add or edit the custom-field filter.
    7. In the custom-field dropdown, select:
      Send from (mySMSGateway)
    8. Set the operator to Has changed.
    9. Click Save in the trigger configuration panel.
    5.2 Confirm the updateSendFrom Action
    1. Confirm that the myCRMSIM custom action is present in the workflow.
    2. The action may be named #1 updateSendFrom.
    3. Do not remove this action.
    4. Do not replace it with the old external webhook.
    5. Confirm that the workflow structure is:
      Contact changed → Send from (mySMSGateway) → Has changed → #1 updateSendFrom
    5.3 Publish the Workflow
    1. Confirm that the trigger is Contact changed.
    2. Confirm that the filter is Send from (mySMSGateway) → Has changed.
    3. Confirm that the updateSendFrom action is present.
    4. Change the workflow status from Draft to Publish.
    5. Click Save in the top-right corner.
    6. Confirm that the following message appears:
      Saved! Workflow has been published and saved.
    If the following warning appears, the workflow has not been published:
    Workflow cannot be published yet. 1 issue needs to be resolved before this workflow can go live.
    Complete the trigger filter, confirm that the updateSendFrom action is present, and save or publish the workflow again.
    6. Select a Device or SIM for a Contact
    1. Open Contacts in the HighLevel location.
    2. Open the required contact.
    3. In the Contact Details panel, find Additional Info or the mySMSGateway section.
    4. Open the Send From [mySMSGateway] custom field.
    5. To use normal routing, select:
      Automatic (assigned user / default)
    6. To send messages through a specific device or SIM, select that device or SIM from the dropdown.
    7. An example option may look like:
      SMS - SIM 2 - Waqas Ahmad
    8. Wait for the selection to be saved.
    9. Confirm that the following success message appears:
      Success. Changes saved successfully
    The available options depend on the devices and SIMs connected to and assigned to the location. The device name, SIM number, carrier, and user name may vary depending on your account.
    What Each Selection Does

    Send From Selection

    Result

    Automatic (assigned user / default)

    Uses the normal assigned-user or Message Routing behavior.

    Specific device/SIM

    Sends supported HighLevel SMS messages through the selected device or SIM.

    SEND FROM toggle OFF

    Ignores the contact selection and uses normal Message Routing.

    7. Send a Test Message
    1. Keep the contact record open.
    2. Confirm that a specific device or SIM—not Automatic—is selected in the mySMSGateway field.
    3. Open the contact’s Conversations panel.
    4. Select the SMS tab.
    5. Enter a short test message, such as Hello.
    6. Click the Send icon.
    7. Confirm that the message was processed through the selected device or SIM.
    HighLevel’s built-in Send SMS workflow step and bulk SMS actions also respect the Send From selection when Send From is enabled.
    If an automation must always follow the configured Message Routing, use the mySMSGateway actions instead:
    • Send iMessage
    • Send WhatsApp
    • Send RCS
    These actions do not read the contact’s Send From field. They use their configured routing.
    8. Verify Workflow Execution
    1. Open Automation in HighLevel.
    2. Select Workflows.
    3. Open the Send From workflow.
    4. Open the Execution Logs tab.
    5. Find the test contact.
    6. Confirm that the execution status is Finished.
    7. Confirm that the Contact Changed trigger was executed.
    A completed execution confirms that the Send From field change was detected and the workflow ran successfully.
    9. Verify the Actual Device in myCRMSIM Message Logs
    Workflow completion alone is not enough. Also verify the actual device routing in Message Logs.
    1. Open the myCRMSIM dashboard in a separate browser tab.
    2. Open Message Logs.
    3. Find the test message.
    4. Check the message status, such as Queued or Sent.
    5. Check the Device ID column.
    6. Confirm that the Device ID matches the SIM or device selected in the contact’s Send From field.
    For example, if SIM 2 was selected for the contact, the Message Logs entry should show the corresponding SIM 2 device identifier.
    10. Troubleshooting
    The Send From Field Does Not Appear
    1. Confirm that the SEND FROM toggle is ON for the correct sub-account.
    2. Confirm that the latest myCRMSIM snapshot is installed.
    3. Confirm that the HighLevel location is connected to myCRMSIM.
    4. Refresh the HighLevel contact page.
    5. Open Additional Info in the contact again.
    6. Check the myCRMSIM telephony provider under Settings → Phone System → Additional Settings.
    7. Confirm that the Send From workflow is present and published.
    If the latest snapshot has not yet been released to your account, the field may not be available until the latest version is published.
    No Devices or SIMs Appear in the Dropdown
    1. Confirm that the device or SIM is connected and online.
    2. Confirm that it is assigned to the correct location or sub-account.
    3. Confirm that the latest snapshot is installed.
    4. Confirm that the myCRMSIM telephony provider is selected.
    5. Run Resync devices in myCRMSIM Message Routing.
    6. Refresh the HighLevel contact page.
    7. Open the contact’s mySMSGateway field again.
    The Workflow Cannot Be Published

    Confirm that:

    1. The trigger is Contact changed.
    2. The filter field is Send from (mySMSGateway).
    3. The operator is Has changed.
    4. The updateSendFrom custom action is present.
    5. The workflow was saved after the trigger was configured.
    The updateSendFrom Action Is Missing

    Install or reinstall the latest snapshot for the correct sub-account or location.

    Important: Do not replace this action with an external webhook.
    The Workflow Does Not Appear in Execution Logs
    1. Confirm that the contact’s Send From value actually changed.
    2. Confirm that the workflow is Published.
    3. Confirm that the trigger is Contact changed.
    4. Confirm that the filter is Send from (mySMSGateway) → Has changed.
    5. Confirm that the workflow and test contact belong to the same location.
    6. Change the Send From value again and review the logs.
    The Workflow Finished but the Wrong Device Was Used
    1. Confirm that a specific device or SIM—not Automatic—was selected.
    2. Confirm that the selected device belongs to the same location or sub-account.
    3. Confirm that the updateSendFrom action is present.
    4. Review the workflow execution logs.
    5. Check the message’s Device ID in myCRMSIM Message Logs.
    6. Confirm that the selected device was online when the message was sent.
    The Selected Device Is Offline

    If the selected device is offline, the message may wait for that device according to the existing sending behavior. Check the device connection.

    The Selected Device Was Removed from the Sub-Account

    Messages may fall back to normal Message Routing. Assign a valid device or SIM and run Resync devices if the dropdown does not update.

    11. Quick Checklist
    Before using Send From, confirm the following:
    • The SEND FROM toggle is ON for the correct sub-account.
    • Required devices and SIMs are connected and online.
    • Devices and SIMs are assigned to the correct sub-account.
    • The latest myCRMSIM snapshot is installed.
    • mySMS Gateway App - SMS, WhatsApp & Message is selected as the Default telephony provider.
    • The Send From workflow is present and published.
    • The trigger is Contact changed.
    • The filter is Send from (mySMSGateway) → Has changed.
    • The #1 updateSendFrom action is present.
    • The Send From [mySMSGateway] field appears in the contact record.
    • A specific device or SIM is selected when normal routing must be overridden.
    • The test message workflow execution status is Finished.
    • The correct Device ID appears in Message Logs.

    Was this article helpful?

    0 out of 0 liked this article

    Still need help? Message Us