【发布时间】:2021-11-05 06:16:49
【问题描述】:
【问题讨论】:
标签: docusignapi docusignconnect power-automate-custom-connector
【问题讨论】:
标签: docusignapi docusignconnect power-automate-custom-connector
来自: https://docs.microsoft.com/en-us/connectors/custom-connectors/create-webhook-trigger
Webhook 在 GitHub 端通过 HTTP POST 创建到 /repos/{owner}/{repo}/钩子。创建新的逻辑应用或流时, 它使用 OpenAPI 中定义的触发器发布到此 URL 定义。如果触发器被修改,它也会发布到 URL。在 下面的示例, post 属性包含请求的架构 已发布到 GitHub。
我怀疑您没有意识到这是一个高级选项,它要求您在另一端也有一个网络应用程序。如果您是开发人员并且有一个网络应用程序 - 那么您将知道您的应用程序的 URL。
如果您正在寻找从 DocuSign 获取触发器的无代码/低代码选项,您最好的选择是使用那里已经存在的连接器 - https://flow.microsoft.com/en-us/connectors/shared_docusign/docusign/
【讨论】:
DocuSign触发器的url为https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/connect(测试系统)。身体是
{
"connectId": "",
"configurationType": "custom",
"urlToPublishTo": "https://docusigntest.mysite.com",
"name": "test1234",
"allowEnvelopePublish": "true",
"deliveryMode": "",
"enableLog": "false",
"includeDocuments": "false",
"includeCertificateOfCompletion": "false",
"requiresAcknowledgement": "true",
"signMessageWithX509Certificate": "false",
"useSoapInterface": "false",
"includeTimeZoneInformation": "true",
"includeHMAC": "false",
"includeEnvelopeVoidReason": "true",
"includeSenderAccountasCustomField": "true",
"envelopeEvents": [
"Completed"
],
"soapNamespace": "",
"allUsers": "true",
"includeCertSoapHeader": "false",
"requireMutualTls": "false",
"includeDocumentFields": "true",
"eventData": {
"version": "restv2.1",
"includeData": ["documents","recipients"]
}
}
【讨论】: