Webhook notifications

Renta's webhook integration allows you to connect your data pipeline monitoring to external incident management systems, custom applications, or automation platforms such as Zapier, Pipedream, and Make. By using webhooks, you can build advanced workflows that trigger whenever a specific event occurs in your Renta workspace.

Adding webhook endpoints

Register your external URL to receive event data from Renta.

Navigate to Notification channelsStep 1

Go to Alerts in the sidebar and select the Notification channels tab.

Add webhookStep 2

Scroll down to the Webhooks section and click the Add webhook button.

Configure endpoint detailsStep 3

Enter a Display name (for example, "Engineering On-call"), the Endpoint URL where the data should be sent, and optional Authentication credentials if required by your system. Click Add webhook to save.

Verify endpoint statusStep 4

The new webhook will appear in the list with an Active status.

Enabling alerting rules

After registering your endpoint, you must subscribe it to specific events to receive data.

Setting up alerting rules

Define which events should trigger the webhook request.

Access Alerting rulesStep 1

Navigate to the Alerts tab. Find the Pipeline failed rule and switch it to On.

Assign webhook channelsStep 2

In the Send to dropdown, select the webhook channels you configured. You can send the same event to multiple webhooks and other channel types simultaneously.

Error deduplication

To prevent overwhelming your downstream systems with redundant requests, Renta applies deduplication. For persistent issues, a unique error event is triggered once every 24 hours unless the status changes to Resolved.

Webhook payload structure

When an event occurs, Renta sends a POST request to your configured endpoint with a JSON payload. The structure depends on the event type.

IntegrationFaulted event

This event is triggered when a pipeline integration fails during execution.

{
  "event_type": "IntegrationFaulted",
  "error": "Connection timeout after 30 seconds",
  "id": "a1b2c3d4-e5f6-7890-1234-567890abcdef",
  "run_id": "123e4567-e89b-12d3-a456-426614174000",
  "workspace_id": "987fcdeb-51a2-43d7-9012-34567890abcd",
  "source_type": "facebook_ads",
  "destination_type": "bigquery",
  "integration_name": "Facebook Ads to BigQuery"
}

SourceConnectionFailed event

This event is triggered when Renta cannot establish a connection to a data source.

{
  "event_type": "SourceConnectionFailed",
  "error": "Invalid API credentials",
  "source_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "source_name": "LinkedIn Ads Production",
  "source_type": "linkedin_ads",
  "workspace_id": "987fcdeb-51a2-43d7-9012-34567890abcd"
}

Standard fields common to all source types:

Facebook Ads specific fields

For facebook_ads sources, the payload includes these additional fields:

Best practices

1. Use HTTPS. Always use secure HTTPS endpoints to ensure that potentially sensitive metadata about your pipelines is encrypted during transmission.

2. Implement Basic Auth. To protect your endpoint from unauthorized requests, configure HTTP Basic Authentication in Renta and verify the credentials on your receiving server.

3. Handle payloads asynchronously. Ensure your receiving server responds quickly with a 200 OK status and processes the event data in the background to avoid connection timeouts.