> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/administrator-settings/admin-settings/webhook/multiple-webhooks.md). # Multiple Webhooks Yes, in emSigner, you can configure multiple webhooks. This allows you to send real-time updates to different source systems based on specific events. **Use Case:** Multi-System Webhook Integration in emSigner **Scenario:** XYZ Bank uses emSigner for digital document signing across multiple departments—Loans, HR, and Compliance. Each department requires real-time updates in their respective systems whenever a document is signed. To achieve this, emSigner allows configuring multiple webhooks with a "Request From" parameter to ensure updates are routed to the correct system. **How It Works:** * The Loan Department configures a webhook () with "Request From": "LoanManagement", ensuring loan agreements are automatically updated in the Loan Management System (LMS) once signed. * The HR Team sets up a webhook () with "Request From": "HRPortal", allowing the HR system to mark new employees as "Onboarded" after signing Offer Letters and NDAs. * The Compliance Team integrates a webhook () with "Request From": "ComplianceAudit", ensuring all signed contracts are logged in the Audit & Compliance System for regulatory tracking. With Multi-System Webhooks, emSigner enables businesses to streamline their document workflows, ensuring every department gets real-time updates without manual intervention. **Event-Based Configuration** – You can configure webhooks for different types of events, such as document status updates, signing completion, or user actions. **Multiple Destinations** – Organizations can define different webhook URLs for different departments or systems, ensuring that relevant updates are routed to the right destination. **Webhook Retry Mechanism** – If a webhook fails, emSigner has a retry mechanism that will attempt to send the update again based on configurable intervals. **Webhook Failure Alerts** – If a webhook continuously fails, an alert is sent to the Super Admin, informing them that the webhook needs to be fixed. Below are the steps to configure multiple webhooks. Confirmed — Authentication still has only **None** and **Basic**, and selecting Basic reveals **User Name** and **Password** fields. Here's the updated child section: *** Step 1: Navigate to the Settings page of the Administrator account. Step 2: Under Integrations & Automation, click on the 'Webhooks for Real-Time Updates' card.
Step 3: The grid with the existing webhooks configured will be shown on the Webhooks for Real-Time Updates page.
Step 4: The admin has to provide the Name and the events for which this webhook needs to be configured.
Step 5: For the default webhook URL, the admin can skip selecting the Department or the Request From. Step 6: If there are multiple source systems, then the admin has to mandatorily provide either the Department or the Request From parameter. This Request From parameter has to be mandatorily passed in the API so that the emSigner system identifies that for any change in the workflow status of this envelope, the particular source system has to be notified. Step 7: The admin has to select the type of authentication. If there is no authentication, "None" needs to be selected; otherwise, "Basic" needs to be selected. Selecting "Basic" reveals two additional fields — User Name and Password — which must be filled in with the target system's credentials. Once all the details are filled in, the admin has to click Save to save the webhook configuration. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.emsigner.com/administrator-settings/admin-settings/webhook/multiple-webhooks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.