dibales.ai - Instagram Trigger icon

dibales.ai - Instagram Trigger

Receives Instagram 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 (postbacks, quick replies, reactions, etc.) exit via the trailing 'No Match' port.

dibales.ai - Instagram Trigger

AI-generated

Summary

Starts a workflow from dibales.ai Instagram webhook events, routing each event to a per-match output, optional passive-event ports, or a trailing "No Match" port based on configured trigger rules.

Inputs

  • signatureVerification — When on, checks the X-Dibales-Signature and X-Dibales-Timestamp headers (HMAC-SHA256 over "timestamp.body", 300s tolerance). Failures return 401. Off by default, so anyone with the URL can trigger the workflow.
  • webhookSecret (required) — Webhook secret from dibales.ai Agent Settings. Shown and required only when signature verification is enabled. If empty, the node returns 500 missing_webhook_secret.
  • triggers — Ordered list of match rules; the first matching rule wins. Types: comment on post/reel (specific or any post, include/exclude keywords), direct message (exact or contains keywords, at least one keyword required), story reply (specific or any story, include/exclude keywords), story mention (no filters), and live-broadcast comment (include/exclude keywords). Keyword matching is case-insensitive.
  • forwardEvents — Selects passive events to expose on their own output ports: Outbound Echo, Reactions, Read Receipts, Comment Echo. Unselected ones are dropped, and the webhook still replies 200.

Output shape

One item per webhook call, emitted on a single output port. The item's JSON is the full dibales.ai event envelope. Ports are: Match, then one port per enabled forward event (Echo, Reactions, Reads, Comment Echo), then No Match.

Matched items carry a _trigger field ({index, type}). Postback and quick-reply events always go to the Match port with _trigger: {passthrough: true}. Unmatched message, comment, story and live events go to No Match. Unselected passive events and unknown event types are dropped, producing no item. The match port is shared by all rules, so use _trigger.index to tell rules apart. The node answers GET ?challenge= setup requests by echoing the challenge. Invalid JSON returns 400. Otherwise it replies 200 with a small JSON status.

Examples

Example 1: Reply to a keyword comment on a specific reel with a DM

Add a trigger of type comment, scope Specific Post / Reel, pick the reel, Match = Specific Keywords with Include Keywords "link". Enable Signature Verification and paste the secret. Connect the Match port to a send-DM node.

Example 2: Handle DMs by keyword and send everything else to an AI agent

Add a message trigger with Match Rule Contains and keywords "price" and "help". Wire the Match port to your keyword handler and the No Match port to an AI agent.

Example 3: Avoid reply loops on your own comments

Select Comment Echo in Forward Events. Route that port to a No-Op node or to your loop-handling logic.

Links

Discussion