While on the Event Notification Dashboard, use the following steps to create your first notifications.

1: Create a New Callback

1. From the dashboard, click + New in the top-right corner.

2. You'll navigate to the callback configuration page

2: Configure Basic Settings

• Callback Name (Required)

  • Enter a descriptive name to identify this callback Example: "Salesforce Transaction Updates" or "Customer Portal Notifications"

• Callback URL (Required)

  • Enter your HTTPS endpoint URL Must use HTTP or HTTPS protocol Example: https://api.yourcompany.com/webhooks/conga-events

• Status

  • Toggle between Active and Inactive. Inactive callbacks won't send notifications. By default, new callbacks are set to Active.

3: Select Events

Click the Events tab to choose which events trigger notifications.

Account Events (Transaction Lifecycle)

4: Configure Advanced Options (Optional)

Click the Advanced Options tab for additional settings.

Toggle Include the full document bytes (base64 encoded) in the callback payload

When Disabled (Default):

• Webhook includes only metadata and document references

• Smaller payload size

• Use Conga Sign APIs to retrieve document content when needed

• Recommended for most use cases

When Enabled:

• Full document content included as base64-encoded data in the payload

• Applies only to Transaction Completed events

• Significantly larger payloads (can be several MB)

• Ensure your endpoint can handle large payloads

5: Configure Authentication

Click the Authentication tab to secure your webhook endpoint.

Authentication Type Options:

• None:

  • No authentication headers sent

  • Endpoint receives requests without authentication

  • Use for: Internal/trusted endpoints, testing environments

• Basic Authentication:

  • Sends API key in Authorization header

  • Format: Authorization: Bearer <your-api-key>

  • Use for: Simple API authentication, basic security requirements.

    • Configuration:

      • Select Basic Authentication

      • Enter Username

      • Enter Password

      • Credentials are Base64-encoded and sent as: Authorization: <Basic64String>

• OAuth 2.0:

  • Full OAuth 2.0 client credentials flow

  • Tokens automatically refreshed

  • Use for: Enterprise integrations, high-security requirements

    • Configuration:

      • Select OAuth 2.0

      • Enter Client ID - Your OAuth application client identifier

      • Enter Client Secret - Your OAuth application secret

      • Enter Authentication Server URL - Token endpoint (e.g.,https://auth.example.com/oauth/token)

      • Enter Scope - Space-separated OAuth scopes (e.g., read/write)

    • The system automatically:

      • Requests access tokens using client credentials

      • Refreshes tokens before expiration

      • Includes tokens in callback requests using Bearer authentication

    • Connector

      • Designed for Salesforce Connector integration

      • Enables Salesforce flows and field updates

      • Use for: Triggering Salesforce automation without writeback

      • Configuration:

      • Contact Conga Support for Connector authentication setup assistance.

6: Preview Payload

Click the Payload Preview tab to see the exact JSON structure sent for each event.

{
  "name": "transactionCompleted",
  "sessionUser": "abc",
  "packageId": "abc",
  "message": "Callback Events",
  "documentId": null,
  "createdDate": "2026-01-28T17:37:42.976Z"
}

• Selected events

• Document bytes toggle setting

• Applied filters

Use this preview to:

• Understand the data structure

• Design your endpoint's data processing logic

• Verify the information available for each event type

7: Test your Callback

Before activating, test your endpoint connectivity:

1. Ensure you've entered a valid Callback URL

2. Ensure Status is set to Active

3. Click the Test button in the top-right corner

8: Save Configuration

1. Review all settings across tabs

2. Click Save in the top-right corner

3. System validates configuration

4. Success message confirms the callback is saved

The Save button enables only when changes are detected.

Additional Actions:

• Cancel: Discard unsaved changes and return to dashboard

• Clear: Reset all fields to start over

• Delete: Permanently remove the callback (only on existing callbacks)