Webhooks and SSL certificates in Enfocus Switch

1. Understanding Webhooks in Enfocus Switch

A webhook is a way for an application to send an automated message or payload to a URL when an event happens. In Switch, you can use webhooks to receive notifications or data from external apps (for example, a job submission from a web portal).

In short: Switch listens for a webhook and waits for an HTTP request from another system.

2. Setting up webhooks in Enfocus Switch to receive the payload

To receive webhooks, Switch must expose a public URL that the other system can reach using an HTTP method. This is done in the “Path” property of the “Webhook” flow element.

3. Setting up webhooks to send from an external service

This configuration is done in the external service. Most services that support webhooks include instructions in their documentation. For example, Jotform’s webhook setup instructions are available here.

Example sending URL: https://switch.companyname.com/scripting/notifySwitch

4. Why SSL Certificates Matter

By default, HTTP traffic is unencrypted. Anyone between Switch and the other system could intercept the data. SSL certificates ensure the connection is secure by:

• Encrypting the connection so data can’t be read by third parties.
• Authenticating the server so the client knows it’s talking to the right endpoint.
• Preventing modification of data in transit.

5. Installing and Managing SSL Certificates in Switch

Enfocus Switch relies on the Windows or macOS certificate store, and certificates must be added via Switch’s settings.

5.A. Obtain an SSL certificate from a trusted CA (for example Let’s Encrypt, DigiCert, GoDaddy).

We recommend a wildcard certificate (e.g. *.companyname.com) if you are able to share the same certificate for multiple hostnames. If your SSL provider supplies a certificate that includes the private key, request the certificate and private key as separate files — Switch requires both files separately.

Once you have the certificate and private key files, upload them via: Switch > Preferences > HTTPS settings. If your private key has no password, you can leave the password field blank.

5.B. Make your Switch Server accessible from the internet

To make your Switch Server accessible from the internet, complete the following steps:

      5.B.1. Reserve the server’s local IP address

• Log into your router’s admin interface.
• Find the DHCP reservation or Static IP settings.
• Reserve the local IP of your Switch Server (for example 192.168.1.50) so it never changes, even after restarts.

     5.B.2. Create a DNS name for your server

• Go to your domain’s DNS settings (where your domain is registered).
• Add an A record:
• Name / Host: e.g. switch.companyname.com
  Value / Points to: your network’s public IP address (search “what is my IP” to find it).
• This DNS name must match your SSL certificate hostname unless you’re using a wildcard certificate (e.g. *.companyname.com).

    5.B.3. Set up port forwarding

• In your router’s settings, create a port forward that sends requests from the public IP to your Switch Server’s local IP using the same port number. Example:

  Public Port: 51088 → 192.168.1.50:51088

• The port can be found or set in Switch’s Web services preferences (default: 51088).
• Replace 192.168.1.50 with your Switch Server’s actual local IP address.

6. Create Firewall Rules to Allow Inbound and Outbound Requests

Once port forwarding is in place on your network router, you will need to allow HTTP traffic on the port defined in the Switch>Preferences>Switch Web Service property:

• Edit your firewall rules in Windows Defender, Mac OS Firewall settings, and/or in your network firewall appliance if required.
• Create an inbound and an outbound rule that permits traffic to tyhe defined port.

7. Testing and Troubleshooting

• Use Postman to send a test POST request to Switch.
• Check Switch’s Messages panel for incoming request logs.
• Verify the SSL handshake succeeds (no certificate errors) using an online SSL checker such as SSLShopper.
  • Common SSL error: missing intermediate certificate(s)

A common error when checking certificates is a missing intermediate certificate. Ways to determine which intermediate certificate(s) you need:

• The SSL checker should indicate the required intermediate certificate.
• Search for the intermediate certificate for the SSL product you purchased.
• Contact your SSL provider and ask which intermediate is required.
• Once acquired, append the intermediate certificate(s) to the certificate Switch is using (or include it in the certificate chain as required by your platform).