This article provides a complete, practical walkthrough of the Webhook Code Create Webhook n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:
   Automating DingTalk Notifications for Azure DevOps Pull Requests Using n8n
   
   Meta Description:
   Learn how to automatically send customized DingTalk messages for new Azure DevOps pull request events with this n8n workflow. This tutorial covers webhook integration, MySQL mapping, and real-time notifications to streamline your code review process.
   
   Keywords:
   n8n workflow, Azure DevOps, DingTalk, pull request notifications, DevOps automation, DingTalk webhook, MySQL integration, PR review alerts, CI/CD, ChatOps
   
   Third-Party APIs Used:
   
   - Azure DevOps Service Hooks (Webhook for PR created events)
   - DingTalk Robot Webhook API
   - MySQL database (via n8n MySQL node)
   
   Article Body:
   
   In modern DevOps workflows, timely communication is vital for maintaining code quality and team efficiency. A particularly useful practice is notifying reviewers when new pull requests (PRs) are created. While Azure DevOps provides webhooks for automation, integrating these with team communication platforms like DingTalk can greatly amplify their impact. This article walks through a powerful n8n workflow that automatically notifies the right people in DingTalk when a new PR is submitted in Azure DevOps.
   
   Overview
   
   The n8n workflow we're discussing consists of an end-to-end automation that:
   
   - Listens for pull request creation events from Azure DevOps.
   - Maps Azure DevOps user accounts to their corresponding DingTalk accounts using MySQL.
   - Formats a customized markdown message.
   - Sends the message to a DingTalk group via robot webhook, while @-mentioning the appropriate reviewers.
   
   Let’s take a closer look at each component of the workflow.
   
   1. Webhook Listener from Azure DevOps
   
   The process begins with the ReceiveTfsPullRequestCreatedMessage node — a webhook receiver in n8n. This node listens for “Pull Request Created” events from Azure DevOps. You have to manually create a service hook in Azure DevOps and point it to the URL provided by this webhook. When a new PR is submitted, Azure DevOps triggers the webhook with a JSON payload describing the event, including details like the PR creator and reviewers.
   
   Webhook endpoint path: pr-notify-template  
   HTTP Method: POST
   
   Setup Tip: Make sure to customize the webhook path and copy the complete webhook URL into your Azure DevOps service hook settings.
   
   2. Load User Mapping Data from MySQL
   
   Once the webhook receives the Azure DevOps PR payload, n8n moves to the next node: LoadDingTalkAccountMap. This MySQL node queries a table containing user mappings between Azure DevOps and DingTalk.
   
   MySQL Table Structure:
   
   | Field          | Type    | Description                          |
   |----------------|---------|--------------------------------------|
   | TfsAccount     | varchar | Azure DevOps user’s domain name      |
   | UserName       | varchar | The user's full name                 |
   | DingTalkMobile | varchar | The user's DingTalk mobile number    |
   
   This mapping is crucial for matching reviewers to their DingTalk accounts so that they can be correctly @-mentioned.
   
   3. Customizing the DingTalk Message Content
   
   The heart of the customization lives in the BuildDingTalkWebHookData node. This is a JavaScript code node that:
   
   - Receives the PR data from Azure DevOps.
   - Iterates through the list of reviewers.
   - Maps the Azure usernames to DingTalk mobile numbers using the fetched MySQL data.
   - Constructs a markdown message containing the original PR description and appends an @-mention section targeting the reviewers.
   
   Special Logic Included:
   
   - If a review is requested from a “team” (i.e., group of people), the message will @ all users in DingTalk.
   - If a specific user is found in the MySQL mapping, they get an individual mobile-based mention.
   
   This method ensures that the message not only includes who opened the PR and what it’s about, but also directly tags the people who need to take action.
   
   Sample Output Message:
   > [PR Summary and Description]  
   >  
   > 请 @张三 @李四 评审
   
   4. Sending the Message via DingTalk Webhook
   
   Finally, the SendDingTalkMessageViaWebHook node is an HTTP Request node that uses DingTalk’s Robot Webhook API to send the constructed message.
   
   Request Type: POST  
   API Endpoint:
   https://oapi.dingtalk.com/robot/send?access_token=YOUR_ACCESS_TOKEN
   
   This node sends a payload that includes the markdown message, @-mention list, and a flag indicating if all users should be notified.
   
   Example API Body:
   {
     "at": {
       "atMobiles": ["18888888888", "19999999999"],
       "isAtAll": false
     },
     "msgtype": "markdown",
     "markdown": {
       "title": "New PR Notify",
       "text": "请 @张三 @李四 评审"
     }
   }
   
   Benefits of This Automation
   
   - Real-time communication: Reviewers are notified instantly through a platform they frequently use.
   - High accountability: By tagging users directly, it reduces the chance of missed reviews.
   - Scalability: The mapping system allows easy addition of new users without code changes.
   - Extensibility: The message format is fully customizable to match your team’s communication style.
   
   How to Set It Up
   
   To use this automation in your own environment:
   
   1. Import the n8n workflow JSON.
   2. Customize the webhook path and set up the Azure DevOps Service Hook for PR events.
   3. Create and populate the MySQL mapping table with your team's data.
   4. Update the DingTalk Robot API token in the HTTP Request node.
   5. Test with a real or test PR from Azure DevOps.
   
   Final Thoughts
   
   By connecting Azure DevOps to DingTalk using n8n, you create a lightweight, effective notification system that improves the speed and quality of your code review process. This workflow can act as a foundation for broader team collaboration workflows, integrating other tools and alerts as needed.
   
   For teams using DingTalk as their primary communication channel, this automation represents a smart step forward in DevOps maturity.
   
   Ready to give it a try? Clone the workflow, configure your mappings, and start receiving actionable pull request alerts in DingTalk today.

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.