@kapa.ai Notifications just showing that there were a failure, it does not contain any details

This behavior depends on the notification type and delivery method you're using. Webhook Notifications (Failed Sync) Webhook notifications for failed syncs do include detailed payload information, such as: • Workspace, connection, source, and destination details •

jobId

,

startedAt

,

finishedAt

•

bytesEmitted

,

recordsEmitted

,

recordsCommitted

•

errorMessage

,

errorType

, and

errorOrigin

Example fields from the failed sync payload: [Webhook Payload Docs]

{
  "data": {
    "errorMessage": "Something failed",
    "errorType": "config_error",
    "errorOrigin": "source",
    "success": false
  }
}

Other Notification Types — No Payload However, several other notification events sent via webhook do not contain a payload and only work for Slack notifications: • Connection Updates • Connection Updates Requiring Action • Warning - Repeated Failures • Sync Disabled - Repeated Failures • Warning/Sync Disabled - Upgrade Required For these events, the webhook notification will only show that something happened, without details. [Webhook Payload Docs] Email Notifications Email notifications also tend to be high-level alerts rather than detailed reports. Recommendations • If you need detailed failure information, use a webhook configured for the "Failed syncs" event — this is the only event type that returns a rich payload. • For deeper diagnostics, check the sync logs directly in the Airbyte UI on the connection detail page. • If you need programmatic access to sync details on failure, consider using PyAirbyte to trigger syncs and send custom Slack messages with full job details. [PyAirbyte Tutorial] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai can i customize the information the notification shows?

Based on the knowledge sources, Airbyte does not currently support customizing the content or format of its built-in notifications. The notification payloads are fixed and defined by Airbyte. However, there are a couple of workarounds: Option 1: Use a Middleware/Proxy Webhook You can point Airbyte's webhook to an intermediate service (e.g., AWS Lambda, a custom API endpoint) that receives the fixed Airbyte payload and then reformats/enriches it before forwarding it to your desired destination. [Discord Webhook Forum] Option 2: Use PyAirbyte for Custom Notifications You can bypass Airbyte's built-in notifications entirely and use PyAirbyte to trigger syncs programmatically and send fully customized notifications. For example, you can build a custom Slack message with exactly the fields you want: [PyAirbyte Tutorial]

def format_sync_details(sync_result, start_time, duration):
    details = (
        f"Job ID: {sync_result.job_id}\n"
        f"Start Time: {start_time.strftime('%Y-%m-%d %H:%M:%S')}\n"
        f"Duration: {duration:.2f} seconds\n"
        f"Records Synced: {sync_result.records_synced}\n"
        f"Bytes Synced: {sync_result.bytes_synced}\n"
        f"Job URL: {sync_result.job_url}"
    )
    return details

Option 3: Submit a Feature Request If you'd like native customization support, you can submit a feature request or contribute via a PR to the Airbyte project. [Contributing Guidelines] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.