Set Up Webhooks

Table of Contents

• About Webhooks
• Before You Begin
• Create a Webhook
• Test Your Webhook
• Choose a Payload Format
  • Generic JSON
  • Slack
  • Microsoft Teams
• Webhook Event Types
• Use Webhooks with Zapier
• Troubleshooting
• Current Limitations

About Webhooks

Webhooks let Conserv Cloud send an HTTPS notification to a URL you choose whenever an environmental event is triggered or resolved. You can use webhooks to post alerts into a Slack channel or Microsoft Teams channel, start a Zapier workflow, or integrate alerts into your own systems.

Each organization can configure one webhook. You manage it in Setup → Integrations.

Before You Begin

Ensure you have:

• Permission to manage Setup in Conserv Cloud
• A destination URL that accepts HTTPS POST requests (for example, a Slack incoming webhook URL, a Microsoft Teams incoming webhook URL, a Zapier catch hook URL, or an endpoint in your own system)
• At least one event profile configured, so there are alerts to deliver. See Set up Events and Alerts for instructions.

Create a Webhook

1. Sign in to Conserv Cloud.
2. Go to Setup → Integrations.
3. Click Add webhook.
4. Enter a Name for the webhook.
5. Enter the destination URL. The URL must begin with https://.
6. Select a Payload format: Generic, Slack, or Microsoft Teams.
7. Set the webhook to Active if you want it to receive live event notifications.
8. Click Save.
   The webhook appears on the Integrations page.

Test Your Webhook

You can send a test notification at any time to confirm your URL and payload format are configured correctly.

1. Go to Setup → Integrations.
2. Locate your webhook.
3. Click Test webhook.
   A confirmation message appears when the test is sent successfully. If delivery fails, an error message shows what went wrong.

The test sends a sample notification with placeholder data (Test Sensor, Test Space, Test Location). For the Generic format, the payload uses the event type webhook.test. For Slack and Microsoft Teams, the message reads "This is a test notification from Conserv."

Choose a Payload Format

Generic JSON

Choose Generic when integrating with Zapier, your own applications, or any system that consumes JSON. Live events send a payload with this structure:

{

 "event": "alert.triggered",

 "timestamp": "2026-06-16T12:00:00.000Z",

 "data": {

 "event_uuid": "...",

 "event_type": "temp1",

 "sensor_name": "Gallery 2 Sensor",

 "space_name": "Gallery 2",

 "location_name": "Main Building",

 "reading_type": "Temperature",

 "reading_value": 22.21,

 "reading_direction": "below",

 "threshold_value": 30,

 "alert_profile": { "uuid": "...", "name": "Gallery Temperature" }

 }

}

The event field identifies the type of notification. Use it to route or filter notifications in your integration.

Slack

Choose Slack to post formatted alert cards directly into a Slack channel. Create an incoming webhook in Slack, then use the generated URL as your webhook URL in Conserv Cloud. For instructions, see Sending messages using incoming webhooks in the Slack documentation.

Slack notifications include a headline with an emoji for the reading type (for example, 🌡️ for temperature), a plain-language description of the alert with the current reading and threshold, and a footer with the location, alert profile, and sensor names.

Microsoft Teams

Choose Microsoft Teams to post formatted alert cards into a Teams channel. In Microsoft Teams, create a workflow using the Post to a channel when a webhook request is received template, then use the generated URL as your webhook URL in Conserv Cloud. For instructions, see Create incoming webhooks with Workflows for Microsoft Teams in the Microsoft documentation.

Teams notifications contain the same headline, description, and footer content as Slack notifications, formatted as an Adaptive Card.

Webhook Event Types

Event types appear in the event field of Generic JSON payloads. Slack and Microsoft Teams messages convey the same information in the message text instead of a machine-readable field.

Use Webhooks with Zapier

To build a Zapier workflow from Conserv alerts:

1. Create a Zap with the Webhooks by Zapier trigger, using Catch Hook.
2. Copy the catch hook URL that Zapier generates.
3. In Conserv Cloud, create a webhook with that URL and the Generic payload format.
4. Click Test webhook to send sample data to Zapier.
5. In Zapier, use paths or filters on the event field to handle each notification type:

• alert.triggered for new alerts
• alert.resolved for cleared alerts
• webhook.test for test notifications

Troubleshooting

The test succeeds, but live alerts do not arrive.
Check that the webhook is set to Active. Test notifications work while a webhook is inactive, but live alert delivery requires the webhook to be active. Also confirm that your alert profiles are configured and triggering.

The test reports a delivery error.
Verify the URL is correct and reachable, and that your destination responds within 15 seconds with an HTTP success status (2xx). A destination that responds with an error status or times out is reported as a failed delivery.

I cannot save an HTTP URL.
Webhook URLs must use HTTPS. Update your destination to provide an HTTPS endpoint.

I cannot create a second webhook.
Each organization is limited to one webhook. Edit or delete the existing webhook instead.

I cannot create a webhook for offline events.
At this time (July 2026), webhooks can be created for Temperature, Relative Humidity, Illuminance, Movement, and Leak events. Offline equipment alerts cannot be currently set up through webhooks.

The webhook notifications are all in metric units.
All webhook notifications currently only report in °C (Celsius) and Lux. Footcandles and °F (Fahrenheit) are not currently supported.

Current Limitations

• One webhook per organization
• Webhooks created in Conserv Cloud do not support authentication headers; use a unique, secret URL from your destination service
• Notifications are sent for environmental alerts only