在 Docusign 的 Power Automate 自定义连接器中设置触发器
Setup trigger in Power Automate custom connector for Docusign
我正在 Power Automate 自定义连接器中创建一个新触发器来接收 DocuSign 事件,有人知道我应该使用什么 URL、header 和 body 吗?谢谢。
来自:
https://docs.microsoft.com/en-us/connectors/custom-connectors/create-webhook-trigger
The webhook is created on the GitHub side by an HTTP POST to
/repos/{owner}/{repo}/hooks. When a new logic app or flow is created,
it posts to this URL using the trigger defined in the OpenAPI
definition. It also posts to the URL if the trigger is modified. In
the sample below, the post property contains the schema of the request
that is posted to GitHub.
我怀疑您没有意识到这是一个高级选项,要求您在另一端也有一个网络应用程序。如果您是开发人员并且拥有网络应用程序 - 那么您将了解您的应用程序的 URL。
如果您正在寻找 no-code/low-code 选项以从 DocuSign 获取触发器,最好的选择是使用那里已经存在的连接器 - https://flow.microsoft.com/en-us/connectors/shared_docusign/docusign/
DocuSign触发器的url是https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/connect(测试系统)。 body 是
{
"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"]
}
}
我正在 Power Automate 自定义连接器中创建一个新触发器来接收 DocuSign 事件,有人知道我应该使用什么 URL、header 和 body 吗?谢谢。
来自: https://docs.microsoft.com/en-us/connectors/custom-connectors/create-webhook-trigger
The webhook is created on the GitHub side by an HTTP POST to /repos/{owner}/{repo}/hooks. When a new logic app or flow is created, it posts to this URL using the trigger defined in the OpenAPI definition. It also posts to the URL if the trigger is modified. In the sample below, the post property contains the schema of the request that is posted to GitHub.
我怀疑您没有意识到这是一个高级选项,要求您在另一端也有一个网络应用程序。如果您是开发人员并且拥有网络应用程序 - 那么您将了解您的应用程序的 URL。
如果您正在寻找 no-code/low-code 选项以从 DocuSign 获取触发器,最好的选择是使用那里已经存在的连接器 - https://flow.microsoft.com/en-us/connectors/shared_docusign/docusign/
DocuSign触发器的url是https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/connect(测试系统)。 body 是
{
"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"]
}
}