Skip to main content

​
Overview

Webhooks let external services — such as DocuSign — push events into Royaltyport. Each webhook endpoint gives you a unique receiver URL and a signing secret; every incoming delivery is verified against that secret before it is accepted. Verified deliveries can then start automations through the Webhook trigger — for example: a signed contract arrives from DocuSign, an automation validates it and uploads it into a project’s contract pipeline. Only organization Admins can create, change, or delete webhook endpoints. All organization members can view endpoints and their delivery log.

​
Accessing Webhooks

1

Go to Organization Settings

Navigate to your organization from the Dashboard, then click Settings in the navigation.
2

Select Webhooks

Click the Webhooks tab in the settings sidebar.

​
Creating a Webhook Endpoint

1

Enter an endpoint name

Give the endpoint a descriptive name, e.g. “DocuSign — signed contracts”.
2

Choose a provider

The provider preset fills in the correct verification settings for the sending service:
3

Choose how the signing secret is set

The signing secret is the shared key used to verify that deliveries genuinely come from the sending service:
4

Copy the receiver URL

After creating the endpoint, a dialog shows the unique receiver URL (and the secret, if generated). These are shown only once — copy them immediately and configure the sending service with them.
The receiver URL and signing secret cannot be viewed again after the dialog is closed. If you lose the secret, use Rotate secret on the endpoint to set a new one.

​
Setting up DocuSign

To connect DocuSign, you need admin access to your DocuSign account. The flow: create an HMAC key in DocuSign, create the endpoint in Royaltyport with that key, then point a DocuSign Connect configuration at the receiver URL.
1

Create an HMAC key in DocuSign

In DocuSign: Settings (Admin) → Connect → HMAC keys (Integrations section) and add a key. Copy the key — DocuSign also shows it only once.
Royaltyport verifies DocuSign’s first signature header, so the key you paste into Royaltyport must be the first (or only) active HMAC key on the DocuSign account.
2

Create the endpoint in Royaltyport

Create a webhook endpoint with provider DocuSign and paste the HMAC key as the secret. Copy the receiver URL from the dialog.
3

Create a Connect configuration in DocuSign

In DocuSign: Settings (Admin) → Connect → Add Configuration → Custom, with:
4

Send a test delivery

No new signature needed: open the Publish tab in DocuSign Connect, select an earlier completed (signed) envelope, and republish it with your new configuration selected. It can take a few minutes before the publish shows up in DocuSign’s Connect dashboard; once sent, the delivery appears in the endpoint’s delivery log in Royaltyport.
Webhook payloads are limited to ~4 MB, which fits envelopes with roughly 3 MB of PDF documents. Typical signed contracts (1–3 MB) are fine; contact support if your documents are larger.

​
The Delivery Log

Click View deliveries on an endpoint to open its delivery log. Each delivery shows: Admins can Replay a delivery: it is re-dispatched to the endpoint’s automations exactly as if it had just arrived — useful while building an automation, so you never need to re-sign a document to test.
A no_match status is expected until an active automation with a Webhook trigger is pointed at the endpoint. See Automation Triggers for connecting webhooks to automations.

​
Managing Endpoints