FlowRunner
PricingContact
Theme
Start Free

WeChat

Communication

Connect AI agents to your WeChat Official Account. Agents send template and customer service messages, manage followers, tags, and remarks, build custom menus, upload media, and generate parameterized QR codes.

14 actions OAuth available
WeChat website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
An order ships from the storefront to a customer who follows the Official Account
Get User Info confirms the customer's OpenID is an active subscriber
The agent picks the compliant lane: a pre-approved template for the notification, or the customer-service channel if the user interacted within the last 48 hours
Send Template Message delivers the shipping notification with order details filled into the approved placeholders
Tag Users applies the buyer tag and Update User Remark stamps the order reference for operators
The customer replies with a question, and the agent drafts a response with the order context
The support owner reviews the drafted reply before it goes out under the account's name
Send Customer Service Message delivers the approved reply inside the 48-hour window

What This Integration Enables

WeChat is not another messaging channel; it is a governed one. Template messages must be pre-approved, customer-service replies are only allowed for 48 hours after the user's last interaction, and the account's menu and media live under platform quotas. Treating those rules as obstacles is how accounts get restricted. FlowRunner treats them as the workflow's rails: agents send what the platform permits, in the lane the platform defines, and route everything else to a person. - Push order, shipping, and appointment notifications through pre-approved template messages - Answer customers inside the 48-hour service window with text, media, and Mini Program cards - Segment followers with tags, enrich profiles with internal remarks, and page through the full subscriber base - Attribute new followers to campaigns with parametric QR codes carrying scene values - Maintain the custom bottom menu and reusable media assets from a flow instead of the console Since the account speaks to the entire follower base at once, its most sweeping operations sit behind a [human-in-the-loop](/concepts/human-in-the-loop) gate.

Without FlowRunner

Notifications sent by hand, or not at all Order and appointment updates reach WeChat followers only when someone remembers to post them
The 48-hour window expires unused Customer messages sit in a queue, and by the time support replies, the service window has closed
Followers are one undifferentiated list Nobody knows which campaign brought a follower or which followers actually buy

With FlowRunner

Notifications ride approved templates Order, shipping, and appointment updates go out the moment events fire, inside platform rules
The window is worked, not wasted Drafted replies wait only for human sign-off, so answers land while the channel is still open
The follower base is segmented and attributed Tags mark behavior, remarks carry context, and QR scene values tie each follower to a campaign

Use Case Scenarios

Order notifications that never miss

A [Shopify](/integrations/shopify) order fires. The agent resolves the buyer's OpenID, fills the approved order-confirmation template with the order number, items, and delivery estimate, and calls Send Template Message. When the parcel ships, the shipping template follows the same path. The customer gets updates inside the app they check most, and every message used a template the platform already blessed.

Every follower has a source

Each campaign gets its own parametric code from Create QR Code, temporary for events, permanent for evergreen placements, with a scene value naming the campaign. When scans convert to follows, the attribution logs to [Google Sheets](/integrations/google-sheets) by scene value, and Get User Info enriches the new follower's profile before the agent syncs it to [HubSpot](/integrations/hubspot) with nickname and tags intact. The question "which placement fills the funnel" gets a data answer.

Segmentation as a running process

A weekly sweep walks the follower base with Get User List, 10,000 OpenIDs per page. Buyers, event attendees, and lapsed followers get their tags through Tag Users in batches of 50, with new segments minted through Create Tag as campaigns need them, inside the account's 100-tag budget. Get Tags reports each segment's size to the channel, so the team watches segments grow instead of guessing.

Human-in-Loop Highlight

Create Menu does not edit the Official Account's menu; it replaces it. The API overwrites the entire existing structure in one call, and Delete Menu removes every menu including the conditional ones, in front of the whole follower base at once. The menu is the account's storefront: the moment a flawed structure goes live, every follower who opens the conversation sees it, and there is no staged rollout. So FlowRunner treats menu changes like a production deploy. The agent fetches the live structure with Get Menu, builds the proposed replacement, and presents both side by side: what exists, what will replace it, which buttons disappear. The account owner approves the swap, and only then does Create Menu execute. Message automation runs continuously; the storefront changes only on a human's word.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

14 actions

Messaging

2
  • Send Template Message Sends a pre-approved template notification to a subscriber by OpenID, with placeholder values, optional colors, and a redirect URL or Mini Program target. Requires template permission on a verified account.
  • Send Customer Service Message Sends a customer-service message, text, image, voice, video, music, news, or Mini Program card, within the 48-hour window after the user's last interaction. Media types reference a media_id from an upload action.

Followers

3
  • Get User Info Retrieves a subscriber's profile by OpenID: nickname, avatar, language, subscription time and status, tags, and remark. The enrichment read behind CRM sync.
  • Get User List Pages through the follower base at up to 10,000 OpenIDs per call, continuing from the returned next_openid. The backbone of segmentation sweeps.
  • Update User Remark Sets a subscriber's internal remark, up to 30 characters, visible to account operators. The place order references and context live.

Tags

3
  • Get Tags Lists the account's tags with each tag's ID, name, and current subscriber count.
  • Create Tag Creates a new tag, unique and 30 bytes or fewer, within the account's 100-tag limit.
  • Tag Users Applies one tag to up to 50 subscribers per call, preserving their existing tags. The batch write behind behavioral segmentation.

Menu

3
  • Create Menu Creates or replaces the account's custom bottom menu, up to 3 top-level buttons with up to 5 sub-buttons each, across click, view, Mini Program, scan, photo, and location button types. Overwrites the entire existing menu, and the operation this page's human gate exists for.
  • Get Menu Retrieves the currently configured menu, including conditional menus. The before-state read in every menu change.
  • Delete Menu Deletes the custom menu, including all conditional menus, leaving the account bare until a new one is created.

Media

2
  • Upload Temporary Media Uploads a file from a public URL as temporary media with a media_id valid for 3 days, for customer-service messages. Supports image, voice, video, and thumb with per-type size limits.
  • Add Permanent Material Uploads a file from a public URL as permanent, non-expiring material for menus, articles, and reuse, subject to per-account quotas. Video requires a title and description.

Growth

1
  • Create QR Code Creates a parametric QR code, temporary with an expiry or permanent, whose scene value attributes each scanner. Returns a ticket and a ready-to-open QR image URL. The instrument behind campaign attribution.

Frequently Asked Questions

What can FlowRunner do with WeChat?

FlowRunner agents can run Send Template Message, Send Customer Service Message, and Get User Info in WeChat, plus 11 more actions.

Does connecting WeChat to FlowRunner require OAuth?

Yes. WeChat connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can WeChat trigger a FlowRunner workflow automatically?

WeChat doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with WeChat

$100 in credits. No card required. Connect in minutes.