Skip to content
Thirdlane

Webhooks

Incoming Webhooks let outside applications post messages into a Thirdlane Connect Channel - so a monitoring system, CI pipeline, ticketing tool, or custom script can drop alerts and updates where your team is already collaborating, instead of sending yet another email. Creating a Webhook gives you a unique URL; any app that POSTs a JSON payload to that URL has its message appear in the associated channel.

Note that Thirdlane Connect Webhooks are designed to be generally compatible with applications that use Slack webhooks format.

Create/Edit Webhook

Name. A short name for the Webhook.

Description. Webhook description.

Channel. A Channel associated with this Webhook, where the messages from the Webhook will be posted.

Enabled. Specify whether this Webhook is enabled i.e. will be sending messages to the Channel.

Owner. Select a Thirdlane Connect user who will have administrative privileges for this Webhook.

Best practices

  • Treat the webhook URL as a secret - anyone who has it can post to the channel. Regenerate it (recreate the webhook) if it may have leaked.
  • Point each integration at a channel where its messages are actually wanted; noisy automated alerts in a busy team channel get ignored.
  • Because the payload format is Slack-compatible, most tools that already support Slack incoming webhooks can post to Thirdlane Connect with only a URL change.

For how incoming webhooks work for end users, see Webhooks in the Thirdlane Connect User Guide.

  • Channels - the destination a webhook posts into.
  • Outbound Webhooks - send PBX events out to external systems (the reverse direction).