From DocuSign, I'm Robert Knight, a member
of the developer center team.
In this screencast, I'll walk you
through how to set up a custom DocuSign connect configuration.
To follow along with this video, you'll
need a DocuSign developer account.
You can sign up for a free account
at go.dotdocusign.com/demo.
Connect is DocuSign's webhook solution
that notifies your application when selected events get
triggered, which means your application can
get event notifications when they happen
rather than your application polling for them.
In this screencast, we will enable
connect in a developer account, add a custom connect
configuration, and use a free online webhook
listener to test the new connect webhook configuration.
To enable connect, log into your developer account
and from the DocuSign e-signature home page,
select the Settings tab.
Under integrations on the left menu, click Connect.
If connect is not already enabled,
click the Enable connect button.
Click the Add configuration button
and select Custom from the dropdown menu.
First we need to choose a name.
I'm going to call our webhook connect 4
because it's an awesome game and it
was one of the few games I could consistently beat my brother
out when we were kids.
Next, we need a URL to publish to.
The simplest way to test your connect custom configuration
is to use the free online webhook test site,
I'll be using webhook.site.
There are other web plug test site you can choose
and of course, you can create your own webhook listener
using a cloud provider like Azure, Google Cloud, or AWS.
I'm going to leave enable log and require acknowledgment
checked and use the default data format rest v2.1,
which will send your message in JSON format.
The legacy data format sends XML.
Scrolling down, we have a number of checkboxes
we can use to select what information we
want sent in our message.
I'm just going to select recipients.
Note that if you choose to include documents
in your message, it will likely be very large, too
large to use free Cloud webhook listeners.
So only choose to send documents if you absolutely need to.
And keep in mind that this may complicate your webhook
listener solution.
Below the include data section are some other settings
will need to choose.
We're going to accept the default
to send messages for all users.
Next are two groups under trigger events,
one titled envelope events and one titled recipient events.
I'm going to choose envelope signed completed
for my triggering event.
Under integration and security settings,
we're not going to use HMAC encryption,
basic authentication, or mutual TLS,
since our webhook tester won't know
how to deal with those without some advanced configuration
to handle them.
These are recommended for production connect
configurations.
And you can find information about how to use them
in the developer center.
Check out the resources slide at the end
of this demo for links to connect content
in the developer center.
Next, we click Add configuration to return
to the main connect page.
Note that the status shows is active
and there's an Actions button that
opens a dropdown, which will let us edit, deactivate, or delete
our configuration.
Now we need to create a triggering event by signing
and completing an envelope.
I'm going to send myself an envelope.
Then open it, sign it, and finish it,
which will trigger our event.
Our event should be triggered.
Next, we go to our webhook test page
and look for the message sent by our webhook.
And there it is.
There's information about our envelope,
including the information we requested about the recipient.
If you have questions about how to develop
your integration with DocuSign, here are some resources.
I recommend checking out the Connect content under Platform
101 in the developer center, going to Stack Overflow,
reaching out to support, or signing up
for API office hours.
That's it.
Thanks for tuning in.
If you're watching from our YouTube channel,
please post questions and comments below the video
or email us at developers@docusign.com