Send DingTalk message on new Azure DevOps Pull Request
Configured with HTTP Request, My Sql, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Data store
- Trigger
- Code
- Web / API
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| LoadDingTalkAccountMap | Data store | My Sql | select |
| ReceiveTfsPullRequestCreatedMessage | Trigger | Webhook | See node parameters |
| BuildDingTalkWebHookData | Code | Code | See node parameters |
| SendDingTalkMessageViaWebHook | Web / API | HTTP Request | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
mySql
Workflow notes
Send DingTalk message on new Azure DevOps Pull Request
Send DingTalk message on new Azure DevOps Pull Request
This template automates sending a DingTalk message on new Azure Dev Ops Pull Request Created Events. It uses a MySQL database to store mappings between Azure users and DingTalk users; so the right users get notified.
Set up instructions
- Define the path value of ReceiveTfsPullRequestCreatedMessage Webhook node of your own, copy the webhook url to create a Azure DevOps ServiceHook that call webhook with Pull Request Created event.
- In order to configure the LoadDingTalkAccountMap node, you need to create a MySQL table as below: |Name|Type|Length|Key| |-|-|-|-| |TfsAccount|varchar|255| |UserName|varchar|255| |DingTalkMobile|varchar|255|
- You can customize the Ding Talk message content by editing the BuildDingTalkWebHookData node.
- Define the URL of SendDingTalkMessageViaWebHook Http Request node as your Ding Talk group chat robot webhook URL.
- Send test of production message from Azure DevOps to test.
Send DingTalk message on new Azure DevOps Pull Request
Send DingTalk message on new Azure DevOps Pull Request
Purpose and structure
This folder contains the Send DingTalk message on new Azure DevOps Pull Request workflow. Its executable nodes use code, httpRequest, mySql, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
ReceiveTfsPullRequestCreatedMessage
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Webhook/0376_Webhook_Code_Create_Webhook.json MIT; preserve source notices.