Exposing custom Meta Fields to Webhooks#1579

I would like the custom Meta Fields to be exposed to webooks so we can track identifiers across different systems that we feed into from Uptime Robot. We utlize tagging for other purposes and would like to have Meta fields for better organizing and distuinguishing between the two.

Hey Francis - This should already be possible. Here is a screenshot from my test. Feel free to message back here if you are having issues but I will mark this one closed meanwhile.

Thanks for the update! Talking with Support/Uptime Robot AI chat said this was not possible and to put in a feature request and I also could not find any documentation on how to reference this so looks like there might be some internal updates to docs that need to be made! :)

Hm it’s not working for me for some reason (test alerts will not send with the formatting below even though the JSON validator marks it as valid). how are you formatting your POST request in the Uptime Robot webhook? The meta fields will be different for every alert so I am trying the below:

{“original_source”:”Uptime Robot”,”my_custom_field”:”*customFields*”}

I also did a direct JSON query and do not see custom fields as a response object either

{
    "stat": "ok",
    "pagination": {
        "offset": 0,
        "limit": 50,
        "total": 1
    },
    "monitors": [
        {
            "id": 1234456,
            "friendly_name": "my_site",
            "url": "x.x.x.x",
            "type": 3,
            "sub_type": "",
            "keyword_type": 0,
            "keyword_case_type": 0,
            "keyword_value": "",
            "port": "",
            "interval": 120,
            "timeout": 30,
            "status": 2,
            "create_datetime": 1756919680
        }
    ]
}

I figured this out with a simple GET request instead of the POST I was doing earlier.

Can you update documentation / point me to the correct documentation that goes over this?

Hey Francis - Thanks for detailing your steps. I have updated the docs with an example covering this and also added a note next to this variable: https://help.uptimerobot.com/en/articles/14498593-webhook-integration

When you use this variable, you should remove the quotation marks and just use it as *customFields* instead of "*customFields*". I have now updated this in the documentation and I admit we should improve the UX here.

So for your example, this updated version should work:

{“original_source”:”Uptime Robot”,”my_custom_field”:*customFields*}

Thank you for that! So you’re saying you can send those in POST from Uptime? Because when I tried that without quotes, the JSON validator did not pass and I could not save the webhook in Uptime Robot if I didn’t put quotes around customFields.

Yes you can send those in POST. It seems like an issue with the characters you use for quotation marks.

Try to use exactly this one:

{"original_source": "Uptime Robot","custom_metadata": *customFields*}

The one I pasted earlier was from your original comment so it cascaded the issue. If it doesn’t work, reach in via chat in dashboard, I will help you through there by checking the integration setup in your account.

It was the silly quote type. It’s working now, thanks for all your help! It would also be useful if that field was added as nice quick reference within the webhook wizard itself for the future