guides
Trigger Node

Trigger Node

The Trigger node is the starting point of every bot flow in Blueticks. It defines the conditions under which your bot is activated and which users can interact with it.

Trigger Node

Overview

Every bot flow must begin with a Trigger node. This node controls:

  • Which messaging channels can activate the bot
  • Which contacts are allowed to interact with the bot
  • Any specific conditions that must be met for the bot to start

Configuration Options

Source Selection

The first step in configuring a Trigger node is selecting the source that can activate your bot.

Currently, Blueticks supports the following trigger source:

  • WhatsApp Extension: Messages received through WhatsApp Web

Contact Rules

You can control which contacts can trigger your bot flow by setting contact rules:

There are two options for contact list types:

  1. Block List - All contacts can trigger the flow except those specifically listed
  2. Allow List - Only contacts specifically listed can trigger the flow

Contact List

After selecting your contact list type, you can add specific contacts.

Simply enter the name or number of contacts you wish to add to your list.

Allow List with Selected Contact

This is a great way to test your bot during development - you can use the Allow List to restrict access to only yourself or specific team members before making it available to a wider audience.

Common Use Cases

  • Customer Support Bot: Use a Block List to prevent specific problematic customers from accessing support
  • Private Service Bot: Use an Allow List to restrict access to only paying customers
  • Public Information Bot: Skip contact restrictions to make your bot available to anyone who messages
  • Testing Environment: Use an Allow List with just your number to safely test bot functionality

Best Practices

  1. Consider your audience: Choose your contact rules based on your bot's purpose and target users
  2. Start with restrictions: If in doubt, start with a more restricted list and open up access gradually
  3. Review trigger settings regularly: Update your contact lists as your user base changes
  4. Test with limited users: Always test new bot flows with a limited Allow List before deploying widely

Connecting to Other Nodes

After configuring your Trigger node, connect it to the next action in your flow:

  • Message Node: To send an initial greeting
  • Question Node: To start gathering information
  • Webhook Node: To verify user status before proceeding

Notes and Limitations

  • Every bot flow must have exactly one Trigger node
  • The Trigger node must be the first node in the flow
  • Changes to Trigger node settings only take effect after redeploying the bot