Outbound webhooks

Manage Coralogix outbound webhooks directly from your AI agent. The Model Context Protocol (MCP) server provides a unified tool to create, retrieve, update, and delete webhooks, and to generate infrastructure-as-code definitions from webhook configurations.

Tool

Use manage_webhooks for all outbound webhook operations.

Action value	Description
create	Create a new webhook.
get	Retrieve a specific webhook by ID.
list	List webhooks with an optional case-insensitive name filter.
update	Update an existing webhook. The agent retrieves the current configuration first, then applies your changes.
delete	Delete a webhook by ID.
generate_openapi	Generate the OpenAPI JSON payload for use with the Coralogix REST API.
generate_kubernetes	Generate a Kubernetes Operator YAML manifest for the Coralogix Operator.
generate_terraform	Generate Terraform configuration for the Coralogix Terraform Provider.

Supported webhook types

The tool supports the shared Terraform and Kubernetes Operator subset: generic, Slack, PagerDuty, Send Log, Email Group, legacy Microsoft Teams, AWS EventBridge, and several third-party webhook integrations.

Example prompts

Create a generic webhook

Create a generic HTTPS outbound webhook named production-alerts-webhook.
Use URL https://example.com/coralogix-alerts, method POST, and header
Content-Type=application/json.

Create a Slack notification webhook

Create a Slack outbound webhook named slack-critical-alerts with integrationId
prod-slack, fallbackChannel alerts, and channel critical-alerts.

Export an existing webhook

Generate Terraform configuration and Kubernetes Operator YAML for the outbound webhook
named production-alerts-webhook.

Update a webhook

Update the outbound webhook named production-alerts-webhook by changing its
description to "Production alert notification target".

Important behaviors

• Update requires retrieval first. Retrieve the current webhook, modify it, then update with the complete webhook definition.
• Unsupported webhook types fail validation. Teams Workflow and Event Notifications are not part of the shared infrastructure-as-code subset.
• Kubernetes support is narrower for overrides. Some override entity types might work in the backend but not in Kubernetes output.