Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
+1
person also asked this
people also asked this
Replies
37 replies
Subscribers
7 subscribers
Views
37153 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
integration of Appian workflow with DocuSign
rishub
over 8 years ago
Hi All,
We want to integrate Appian workflow with Docu Sign. Is there any plugin exists for that? Our Use case is that we want to email the document to client for sign & they can just sign digitally in email & it can send us signed document back to the workflow & workflow will continue after that.
OriginalPostID-243579
Discussion posts and replies are publicly visible
Parents
0
Tyler Criste
Appian Employee
over 8 years ago
Sure. Endpoint is the same as on http query. For example:
demo.docusign.net/.../envelopes
Request string is the request body, and would be the json structure you posted above, with the ###docId### in place of the base64 encoding of the document.
Request header keys and values correspond to http headers on http query, with the header keys being the header name and the header values being the value.
So for example, you might need a content type header and an authentication header. In that case your header keys would be {"Content-Type", "X-Docusign-Authentication"} and your header values would be something like {"application/json", a!toJson(
{
Username: <username>,
Password: <password>,
IntegratorKey: <integrator key>
}
)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Tyler Criste
Appian Employee
over 8 years ago
Sure. Endpoint is the same as on http query. For example:
demo.docusign.net/.../envelopes
Request string is the request body, and would be the json structure you posted above, with the ###docId### in place of the base64 encoding of the document.
Request header keys and values correspond to http headers on http query, with the header keys being the header name and the header values being the value.
So for example, you might need a content type header and an authentication header. In that case your header keys would be {"Content-Type", "X-Docusign-Authentication"} and your header values would be something like {"application/json", a!toJson(
{
Username: <username>,
Password: <password>,
IntegratorKey: <integrator key>
}
)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data