Documentation Bookings and calendars DenGro

Bookings integration

DenGro

DenGro integration overview
  • CategoryBookings
  • AuthWebhook

Overview

DenGro connects to MessageMind as an inbound webhook: the DenGro card lives in the trigger settings in the MessageMind dashboard, mints a per-account webhook URL and a signing key on first view, and asks the practice to paste both into DenGro's outbound webhook settings. DenGro then POSTs lead and enquiry events to MessageMind, which authenticates each delivery, finds or creates the matching contact and fires the dengroNewLead or dengroNewEnquiry trigger. The connection is one-way: MessageMind never calls DenGro and there is no Integration document; the webhook URL and signing key are the connection.

What MessageMind can do with it

  • Receive DenGro's 'lead-assigned' event (a lead created in, or assigned to, the practice) and fire the dengroNewLead automation trigger.
  • Receive DenGro's 'enquiry-created' event (a lead form submitted without a recognised treatment) and fire the dengroNewEnquiry trigger.
  • Find or create the matching MessageMind contact from the DenGro payload before firing the trigger.
  • Authenticate every delivery with the URL token (routes to and identifies the account) and an HMAC verified from the 'dengro-signature' header.
  • Expose the lead's or enquiry's own fields as campaign tokens (for example {dengro_treatment}, {dengro_message}, {dengro_source}); a field DenGro did not send prints nothing instead of failing the whole send.

Requirements

  • A DenGro account that can configure outbound webhooks.
  • The ability to paste a URL and a signing key into DenGro's webhook settings.
  • At least one active MessageMind automation on the dengroNewLead or dengroNewEnquiry trigger for inbound deliveries to do anything.

How to connect

  1. In the MessageMind dashboard, open the trigger settings and select the DenGro card. On first view MessageMind mints a webhook URL (carrying a per-account token in the path) and a signing key, both revealed only to the account owner.
  2. Copy the webhook URL and the signing key from the DenGro card.
  3. In DenGro, open the outbound webhook settings and paste the webhook URL and the signing key. Save.
  4. DenGro's first delivery hits the probe endpoint and MessageMind replies with HTTP 200 and body { acknowledgement: true, message: 'DenGro webhook endpoint live' } so the connection reads as working on DenGro's side.
  5. If you ever need to invalidate the credential, use the Rotate control on the DenGro card to regenerate the URL and signing key; both must be repasted into DenGro before deliveries resume.

Authentication and permissions

Mechanism
Inbound webhook. The per-account token in the URL path routes and authenticates the delivery (checked in constant time against the stored token shape), and the delivery body is signed with an HMAC that MessageMind verifies from the 'dengro-signature' request header.
Credentials
A per-account webhook URL token and a signing key, both minted by the server on first view of the DenGro card and both revealed only to the owner. Reading or rotating either value is gated by the 'configure' integration permission.

Available data and actions

Reads

  • DenGro's outbound webhook body for each delivery: the event slug (lead-assigned or enquiry-created), the DenGro record id, the person on the lead or enquiry, and the lead or enquiry fields exposed to campaigns as {dengro_*} tokens.

Writes

  • Contacts: a DenGro lead or enquiry creates or merges a MessageMind contact from the webhook payload.
  • Automation triggers: dengroNewLead or dengroNewEnquiry fires into every active automation that wants it, with the lead's or enquiry's own fields available as campaign tokens.

AI agent use cases

  • Start a welcome automation the second DenGro records a new lead, with the lead's own fields (treatment, message, source) available to tokens.
  • React to a lead form that came in without a recognised treatment by listening on the dengroNewEnquiry trigger instead of dengroNewLead.
  • Rotate the webhook URL and signing key from the DenGro card if the signing key is ever compromised, then repaste both into DenGro to resume delivery.

Configuration

  • Supported events: 'lead-assigned' (fires dengroNewLead) and 'enquiry-created' (fires dengroNewEnquiry). The event slug on the payload decides which trigger fires.
  • Field tokens for campaigns include {dengro_treatment}, {dengro_message}, {dengro_source}; a field DenGro did not send prints nothing rather than failing the message.
  • Delivery rate is limited by a per-webhook bucket (DENGRO_WEBHOOK_RATE_LIMIT / DENGRO_WEBHOOK_RATE_WINDOW_MS) so a burst from a busy practice cannot drown the handler.

Example workflows

A new DenGro lead starts a campaign

  1. DenGro POSTs the 'lead-assigned' event to the MessageMind webhook URL, with the HMAC in the 'dengro-signature' header.
  2. MessageMind resolves the URL token to the owning account and verifies the signature.
  3. The contact is found or created from the person on the DenGro record.
  4. Every active automation on the dengroNewLead trigger starts for that contact, with the lead's own fields available as {dengro_*} tokens.

An enquiry without a recognised treatment

  1. DenGro POSTs 'enquiry-created' when a lead form arrives without a recognised treatment.
  2. MessageMind authenticates the delivery and finds or creates the contact.
  3. Every active automation on the dengroNewEnquiry trigger fires with the enquiry's own fields exposed as tokens such as {dengro_message} and {dengro_source}.

Limitations

  • DenGro's connection is inbound only. MessageMind never calls DenGro, so there is no historical backfill: automations start on deliveries received after the webhook is live.
  • Only two DenGro events are mapped to automation triggers: 'lead-assigned' (dengroNewLead) and 'enquiry-created' (dengroNewEnquiry).
  • MessageMind stores no Integration document for DenGro; the webhook URL and signing key on the card are the connection. Rotating either value invalidates deliveries using the old pair until DenGro is repasted.
  • Reading or rotating the webhook URL and signing key is gated by the 'configure' integration permission, because both replies reveal the delivery credential.

Troubleshooting

DenGro's outbound webhook test returns an error from MessageMind.

Fetch the current webhook URL and signing key from the DenGro card in the MessageMind dashboard and paste both into DenGro again. The URL token routes the delivery and the signing key feeds the 'dengro-signature' HMAC check, so a mismatch on either side fails the delivery.

A lead was delivered but no automation started.

Confirm an active automation in MessageMind is listening on the matching trigger (dengroNewLead for 'lead-assigned', dengroNewEnquiry for 'enquiry-created') and that the token in the DenGro webhook URL still matches the one on the DenGro card.

The server log mentions 'signing key unreadable, verification skipped: regenerate the webhook'.

The stored signing key for this webhook could not be read back for verification. Open the DenGro card and use Rotate to mint a fresh URL and signing key, then paste both back into DenGro.

Disconnect and reconnect

  • Remove the webhook URL from DenGro's outbound webhook settings. DenGro will stop delivering immediately.
  • In the MessageMind dashboard, use Rotate on the DenGro card to invalidate the stored URL and signing key.
  • Contacts already created from DenGro deliveries are kept; disconnecting does not remove them.