Conga Product Documentation

Welcome to the new doc site. Some of your old bookmarks will no longer work. Please use the search bar to find your desired topic.

Event Notifications

Event notification management enables administrators to configure webhooks in order to receive real-time notifications from specific events for Conga Sign. You can use this feature to integrate Conga Sign events with external systems and workflows, automate business processes based on transaction lifecycle events, build custom integrations without polling APIs and monitor and troubleshoot event deliveries.

Prerequisites

Before configuring event notifications, ensure you have:

  • Administrator permissions in Conga Sign.

  • A webhook endpoint that can receive HTTPS Post requests.

  • Authentication Credentials (if using basic auth or OAuth 2.0)

  • A network configuration allowing outbound HTTPS connections to your endpoint.

In order to utilize event notifications, you must first create an event registration value.

Getting Started

  1. Login to Conga Sign as an administrator.

  2. Navigate to Admin Home > Automation, select Event Notifications.

  3. You will see the Event Notification Management dashboard displaying:

    1. Total callbacks configured.

    2. Active callbacks count.

    3. Total deliveries attempted.

    4. Success rate percentage.

    5. Average response time.

Understanding the Event Notification Dashboard

Dashboard Metrics Cards

When you access Event Notification Management, the dashboard displays five key metric cards at the top. Each card uses color coding to help you quickly assess system health.

1. Total Callbacks (Blue)

The total number of callback configurations in your account, regardless of status (active or inactive).

Color Indicator:

  • Blue background: Informational metric, no health indicator

Interpreting the value:

  • Example: "4 Total Callbacks" means you have 4 configured callbacks

  • Includes both active and inactive callbacks

  • No maximum limit indicator shown (see Limitations section for any account limits)

When to take action:

  • Review regularly to ensure you're not maintaining unused callbacks

  • Consider deleting old/deprecated callbacks to keep your configuration clean

  • Monitor against account limits (if applicable)

2. Active Callbacks (Green)

The number of callbacks currently set to "Active" status and sending notifications.

Color Indicator:

  • Green background: Positive indicator - these callbacks are enabled and operational

Interpreting the value:

  • Example: "1 Active Callbacks" means only 1 out of your total callbacks is currently active

  • Active callbacks will trigger when their configured events occur

  • Inactive callbacks will not send any notifications, even if events fire

When to take action:

  • If Active < Total: Review inactive callbacks

    • Are they temporarily disabled for maintenance?

    • Should they be reactivated?

    • Should they be deleted if no longer needed?

  • If Active = 0: No callbacks are sending notifications

    • This may be intentional during maintenance

    • Verify if any callbacks should be active

3. Total Deliveries (Light Blue/Purple)

The cumulative number of webhook delivery attempts made by the system.

Color Indicator:

  • Light blue/purple background: Informational metric showing activity volume

Interpreting the value:

  • Example: "194 Total Deliveries" means 194 webhook requests have been sent

  • Includes both successful and failed deliveries

  • Counter accumulates over time

  • High numbers indicate active event volume

When to take action:

  • Cross-reference with Success Rate to understand delivery health

  • If unusually high:

    • Review event selections - are you subscribed to too many events?

    • Check if filters could reduce unnecessary notifications

    • Verify you're not experiencing event duplication issues

  • If zero or very low:

    • Verify active callbacks exist

    • Confirm events are actually occurring in your Conga Sign account

    • Check that callbacks are properly configured

4. Success Rate (Red/Pink or Green)

What it shows: Percentage of webhook deliveries that succeeded (received HTTP 2xx response).

Color Indicators:

  • Red/Pink background: Critical - indicates delivery failures

    • Typically shows when success rate is below a healthy threshold

  • Green background: Healthy - indicates good delivery success

    • Typically shows when success rate is above acceptable threshold

  • Yellow/Orange background (if implemented): Warning - indicates degraded performance

    • May show for moderate success rates (e.g., 50-80%)

Interpreting the value:

Success RateStatusInterpretation
0%Critical (Red)All deliveries are failing - immediate action required
1-49%Critical (Red)Majority of deliveries failing - urgent investigation needed
50-79%Warning (Yellow/Orange)Intermittent failures - investigate and address
80-94%CautionMostly successful but some failures - monitor and improve
95-100%Healthy (Green)Excellent delivery rate - normal operation