Enable a user to implement a webhook model for document storage without consuming the accounts Event Notification Endpoint, while still ensuring that notifications are sent back to Salesforce.

Notifications are currently sent back to Salesforce without using an approach that takes up an Event Notification slot. The Salesforce Connector allows your callback URL to be implemented, although it's still a single URL.

Prerequisites

• The Synergy system is in place as the imaging system.

• Salesforce is integrated with Conga Sign for status updates and notifications.

• Current platform limitations include a single Event Notification Endpoint per Conga Sign account.

Examples

Configuring Synergy for Document Storage

• Scenario: The IT team configures Synergy to accept documents from their internal systems.

1. The team sets up Synergy to receive document entries and metadata.

2. System administrators ensure all compliance requirements are addressed in Synergy's configuration.

Implementing Webhooks in Synergy

• Synergy: Your company needs to dynamically store document metadata as transactions occur.

1. The IT team designs a webhook model.

2. The webhook model facilitates data entry into Synergy's storage system without manual intervention.

Verifying Salesforce Notification System

• Scenario: A banking transaction occurs and the notification system needs to update the status in Salesforce.

1. A customer finalizes a document through Conga Sign.

2. The Synergy system processes the documents storage.

3. The notification sends the transaction completion status back to Salesforce via the callback URL setup in the Salesforce Connector.

4. The IT team verifies that the status update appears correctly in Salesforce.