dibales.ai - TikTok Trigger icon

dibales.ai - TikTok Trigger

Receives TikTok webhook events and routes them: each configured trigger entry gets its own output port (matched message/comment events), and all unmatched or non-matchable events (echoes, reads, comment visibility changes, etc.) exit via the trailing 'No Match' port.

dibales.ai - TikTok Trigger

AI-generated

Summary

Starts a workflow from dibales.ai TikTok webhook events, routing DMs and video comments through ordered keyword rules to separate output ports, with optional ports for passive events and a "No Match" catch-all.

Inputs

  • signatureVerification — When enabled, checks the X-Dibales-Signature and X-Dibales-Timestamp headers (HMAC-SHA256 over "timestamp.body", v1= prefix, 5-minute tolerance). Failures get HTTP 401. Recommended; off by default.
  • webhookSecret (required) — Webhook secret from dibales.ai Agent Settings. Shown only when signature verification is on. If empty, the webhook returns 500.
  • triggers — Ordered list of match rules. The first rule that matches wins, and the Match port fires. Each rule has a Type.
  • triggers.type — "User Comments on Video" or "User Sends a Direct Message".
  • triggers.videoScope / videoId — Comment rules only. Match a specific video (picked from a list or entered as a numeric TikTok item ID) or any video. A specific-video rule with no ID never matches.
  • triggers.matchMode / includeKeywords / excludeKeywords — Comment rules only. "Any Comment" matches every comment. "Specific Keywords" requires at least one include keyword to appear (case-insensitive substring) and none of the exclude keywords. Empty lists are ignored.
  • triggers.messageMatchMode / messageKeywords — DM rules only. "Contains" matches substrings and "Match (Exact)" requires the whole text to equal a keyword, both case-insensitive. A DM rule with no keywords, or a DM with no text, never matches.
  • forwardEvents — Multi-select of passive events to expose on their own output ports: Outbound Echo, Read Receipts, Comment Deleted, Comment Visibility Changed, Comment Echo. Unchecked types are dropped.

Output shape

One item per received event, emitted on a single output port. Port order: Match, then one port per enabled forward event (Echo, Reads, Comment Deleted, Comment Visibility, Comment Echo), then No Match. The item's json is the full dibales.ai event envelope.

Matched items add _trigger: {index, type}. Postback and quick_reply events always go to Match with _trigger.passthrough = true, regardless of rules. Unmatched message.received and comment.created events go to No Match. Forwarded events go to their own port. Other events are dropped. The webhook replies HTTP 200 immediately with a small JSON status (matched, forwarded, dropped). Invalid JSON gets 400. A GET request with ?challenge=... is echoed back for dibales.ai URL verification. Requires dibalesAiApi credentials.

Examples

Example 1: Reply to TikTok comments that say "price" on one video, and ignore comments containing "spam".

Add a trigger of type User Comments on Video, with Scope Specific Video (pick the video), Match Specific Keywords, Include "price" and Exclude "spam". Enable signature verification and paste the secret.

Example 2: Start an automated DM flow when a user sends "start" exactly.

Add a trigger of type User Sends a Direct Message with Match Rule Match (Exact) and Keywords "start". Connect the Match port to the reply logic and No Match to a fallback.

Example 3: Log when the business account's own comments echo back, to avoid reply loops.

Select Comment Echo in Forward Events, then connect the new Comment Echo port to a filter or logging step.

Links

Discussion