Skip to main content
This page is deprecated and no longer appears in the documentation navigation. It is kept only for old links. Please refer to the current example pages under Automation.
Scenario: After an e-commerce order status changes from “Paid” to “Shipped”, automatically notify a WeCom (WeChat Work) bot group so customer support and fulfillment stay in sync.

Prerequisites

  • Access token: Personal Access Token (PAT). Prefer providing via environment variable, for example process.env.TEABLE_TOKEN
  • IDs: The target orders table tableId, and required field fieldIds (e.g., fldStatus, fldOrderNo, fldCarrier, fldTrackingNo)
  • Webhook: WeCom robot Webhook URL (or Microsoft Teams/DingTalk Hook)
  • References: Get IDs and Access Token

Flow overview

  1. Create automation
  2. Create trigger node
  3. Create HTTP request action node
  4. Configure nodes
  5. Test nodes
  6. Enable automation

JavaScript example

API
Main function

Security and best practices

  • Use the least-privileged PAT and restrict accessible spaces/bases.
  • Store sensitive configurations (Token, Webhook) in a secure secret manager or environment variables; avoid hardcoding.
  • Before enabling, use “Test Node” to verify HTTP reachability and that template variables resolve correctly.
  • Configure reasonable timeouts and retries for external APIs, and monitor failures/alerts.
Last modified on May 26, 2026