Send Webhook

NOTE: The Workflow actions available to you depend on the Workflow model you select, the MDM system you use, and the OS of your devices.

Mobile Access Management can send HTTP notifications as part of a deployment. This may be used to send data to an asset management system, for example.

NOTE:

Webhooks are sent from Mobile Access Management's server, not the Launchpad, so expect requests to originate from the cloud.

Click to enlarge

  1. Specify when to send the webhooks. You can send webhooks during any of these three times:

    1. Click the Before Deployment tab to send webhooks at the beginning of a deployment, before any others actions.

    2. Click the After Success tab to send webhooks after the deployment is successful.

    3. Click the After Failure tab to send webhooks after any failure.

  1. Select the Method - HTTP GET, POST, PUT, or DELETE.

  2. In the URL box, enter the URL of the Webhook destination.

    You may add attributes (variables), such as "[Device Serial]" in the URL. Mobile Access Management will perform a substitution just before making the call.

  3. HTTP errors should fail the deployment: This option is available only for Before Deployment. If selected, any response to the webhook other that 200 or 202 will fail the deployment. Otherwise, the webhook response is ignored.

  4. Parse a JSON response into attributes:This option is available only for Before Deployment. If selected, Mobile Access Management attempts to interpret webhook responses and set device attributes to the values it finds.

    For example, your URL may return this response:

    Copy 
    { "Asset Tag": "12345"; "Color": "Red" }

    If you have created a device attribute with the name "Asset Tag", then Mobile Access Management will set the value of Asset Tag to "12345" for the device(s) in the deployment.

    NOTE:

    • The JSON response must be a simple object of key-value pairs. Arrays and nested objects are ignored.

    • You should create attributes before testing this feature.

    • Attribute names are case sensitive.

    • Keys that do not match attributes are ignored.

    • Values may be used in other parts of the same Workflow.

    • Automation rules are evaluated before deployments begin, so automation rules are evaluated before the webhook is called. For this reason, you can not use this technique to affect automation rules.

  5. In the Header box, add headers to the webhook. Separate multiple headers with new lines.

  6. In the Body box, add a body to POST and PUT calls.

    Format your data in XML or JSON. You may include attributes (variables) here as well. Mobile Access Management will perform a substitution just before making the call.

Testing Webhooks

Sites such as RequestBin or webhook.site are useful when testing webhooks.