> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# DevCon 2021 Session 13 Recipient Connect Webhooks for Inbound DocuSign Transactions | Events

#### DevCon 2021 Session 13 Recipient Connect Webhooks for Inbound DocuSign Transactions | Events

Recipient Connect is a webhook service that pushes notifications to your app when an event that you’ve subscribed to occurs, just like DocuSign Connect. Recipient Connect differs from DocuSign Connect in that it provides event notifications when a specific domain user in your organization is a recipient (a signer or cc recipient) of an envelope and a subscribed action occurs, rather than when they are a sender and the action occurs. This means that you can now track events without polling for an envelope that you have received but did not send. Organizations receiving envelopes will now have the ability to receive real-time statuses, envelope data and documents for incoming DocuSign transactions, giving decision-making visibility into business processes.