Skip to main content

Understanding triggers

The starting point of every automation - understand when you need which trigger

Mika Hally avatar
Written by Mika Hally
Updated today

A trigger is the starting point of every automation. It determines when your automation will run.

Good to know: Choosing the right trigger is often the trickiest part of building an automation. But don't worry - once you've got this figured out, the rest is easy!

Message Trigger

New incoming conversation / Reopened conversation

In the trigger menu you'll see 3 separate cards:

  1. "New incoming conversation"

  2. "Reopened conversation"

  3. "New & reopened conversations"

But these aren't 3 different triggers! All three open the same trigger, just with different preselections in the "When should the automation be triggered?" menu:

Option 1: "New conversations only"

  • Triggers when a contact sends a message on this channel for the very first time

  • No conversation with this contact exists yet on this channel in Superchat (but there may be conversations on other channels)

  • Perfect for: Welcome messages, first greeting per channel

Important - Autoresponder conflict with "New conversations only": If you have a welcome message enabled in the inbox settings AND build an automation with "New conversations only", BOTH will be triggered - the customer gets 2 messages! Remember to deactivate one.

Option 2: "Reopened conversations only"

  • Triggers when a conversation has the status "Done"

  • AND the customer (not your team!) sends a new message

  • The conversation automatically changes from "Done" to "Open"

  • Important: Does NOT trigger when:

    • A user manually reopens the conversation

    • A user sends a message to a done conversation

  • Perfect for: "Customer comes back" flows, new support ticket

Option 3: "For new & reopened conversations"

  • Triggers in both cases mentioned above

  • Perfect for: General "first touch" flow (e.g., activate AI agent)

Additional filter options: You can limit the trigger to specific channel types (e.g., WhatsApp only), specific channels (e.g., WhatsApp number 1 only), or inboxes.

Common use cases:

  • Welcome flow with quick responses

  • Activate AI agent + assign conversation to team

  • Support ticket automation

New incoming message

When exactly does this trigger fire?

This trigger is activated by every incoming message from a contact, as long as no active run of this automation is already in progress.

Example: Customer sends 5 messages in a row → Automation triggers the first time. As long as this automation run is still running, the automation won't be triggered again - even if the customer sends more messages. Only after the run is completed can the automation trigger again.

That's why you should almost always combine it with a filter, otherwise the automation runs with every message and can quickly become chaotic and cost a lot of credits.

When does this trigger make sense?

  • You want to react to specific words (combine with message filter)

  • You want to reply automatically outside business hours (combine with business hours filter)

Additional filter options: You can limit the trigger to specific channel types (e.g., WhatsApp only), specific channels (e.g., Instagram account 2 only), or inboxes.

Common use cases:

  • Keyword automations (message contains "advertising" → mark conversation as spam)

  • Outside business hours (filter: only outside → AI agent responds)

For whom? Advanced users - beginners should start with other triggers.

Contact scans QR code / opens link

When exactly does this trigger fire?

This trigger works for WhatsApp (most common use case), but also for Instagram, Telegram, Facebook Messenger, and other channels - you select the channel during setup.

  1. You create a QR code / chat link with prefilled text in the trigger (e.g., "Summer offer")

  2. Customer scans the QR code or clicks the link

  3. The channel (e.g., WhatsApp) opens with the text already prefilled in the input field

  4. Customer presses "Send"

  5. Now the automation triggers!

Important: The automation only triggers when the customer actually sends the prefilled message, not just by scanning / clicking alone.

Folgepfade:

  • Opt-in word sent: Customer sends the opt-in word (e.g., "Summer offer")

  • Opt-out word sent (optional): Customer sends the opt-out word (e.g., "Unsubscribe")

Common use cases:

  • WhatsApp newsletter opt-in: QR code with "Subscribe" → Customer sends → Add to contact list

  • Offline to online: QR code on flyer / poster / product packaging → Automation starts

  • Event registration: QR code at event → "Event2024" → Attendee list

Benefit: GDPR-compliant double opt-in (customer must actively send)

Channel-specific triggers

WhatsApp template sent

When exactly does this trigger fire?

This trigger runs as soon as a specific WhatsApp template is sent.

Important: You must select the exact template in the trigger. The trigger only works for this one template.

What happens then?

  • If the template has no quick reply buttons: Automation starts as soon as the template is sent

  • If the template has quick reply buttons: Automation waits for customer response and creates different paths for each button option

Follow-up paths for quick reply buttons: The small dots on the trigger show the different paths:

  • Each button = its own path (e.g., "Buy now" → Path 1, "Learn more" → Path 2)

  • "If contact doesn't respond" = its own path

  • "If contact writes something else" = its own path

Common use cases:

  • Integration workflows: Calendly appointment → Make / Zapier / n8n sends WhatsApp template → Customer responds → Automation reacts

  • Newsletter campaigns: 500 contacts receive WhatsApp template → Process all responses automatically

Filter options: Only trigger for templates sent via:

  • Manual: Sent by a user from the inbox in Superchat

  • Campaign: Sent via a campaign

  • Automation: Sent by another automation

  • Integration: Sent via external tools like Make, Zapier, n8n, or API

Instagram: Reply to story & comment on post

These are 2 separate triggers in the trigger menu:

  1. "Comment on Instagram post"

  2. "Reply to Instagram story"

Both work very similarly, so we'll explain them together here.

When exactly does this trigger fire?

  • Comment on Instagram post: As soon as someone comments on one of your posts

  • Reply to Instagram story: As soon as someone replies to your story

What happens then?

The automation automatically opens a DM conversation with the person.

Why is this valuable?

Instagram comments and story replies are often hot leads - people actively engaging with your content and showing interest. With this trigger you can:

  • Convert engagement into sales: "How much does it cost?" → Automatically send product info + purchase link in DM

  • Improve support: Answer questions directly in DM instead of publicly

  • Qualify leads: AI agent asks for details and routes to the right team

Advantage over manual handling:

Every interaction lands structured in your inbox instead of being scattered across Instagram. You won't lose any inquiries anymore.

Settings:

  • All posts / stories: Triggers on every post / story

  • Specific posts / stories: You can select individual posts / stories → automation only triggers on these

Tip: Combine with message filter to only react to certain keywords (e.g., only when comment contains "price", "buy", "link").

Common use cases:

  • Instantly convert comments with purchase interest into DM

  • Automatically follow up on story polls ("You voted for Option A - here's more info...")

  • Professionally handle support inquiries from comments in DM

  • AI agent qualifies leads and routes to sales/support

Live Chat opened

When exactly does this trigger fire?

This trigger runs as soon as a customer opens the live chat widget on your website for the first time - before they've even written a message.

Important: Only triggers when opening the chat window, not when sending the first message.

Perfect for: Icebreaker messages that appear immediately upon opening.

Using URL filter: You can build different automations for different pages:

  • URL contains /pricing → Automation 1 triggers → "Questions about pricing?"

  • URL contains /support → Automation 2 triggers → "Need help?"

  • URL contains /product/ → Automation 3 triggers → "Interested in the product?"

Common use cases:

  • Icebreaker with quick responses: "Hi! How can we help?" → Buttons: "Support", "Sales", "Question"

  • Page-specific greetings based on URL

Team & workflow triggers

Manually triggered

When exactly does this trigger fire?

This trigger makes the automation available in the chat controller via the lightning icon. Users must start it manually.

How it works:

  1. User opens conversation

  2. Clicks on the lightning icon in the chat controller

  3. Modal opens with all available automations

  4. User selects the automation they want to start

  5. If input fields are configured in the trigger, these must be filled out

  6. Automation starts for this specific conversation

Input fields:

You can define input fields that the user must fill out when starting. These values are then available as automation variables throughout the entire automation.

Example:

Input field "Discount code" → User enters "SUMMER20" → In message: "Here's your code: {{discount_code}}"

Settings:

  • Only in specific inboxes: Make automation visible only for specific teams/inboxes

  • Only once per contact: Prevents automation from being triggered multiple times for the same contact

Common use cases:

  • Marketing sequences: Input field: Discount code → Personalized message

  • AI agent handover: Input field: Context → AI takes over with context

  • External system updates: Input fields: Amount, number, date → HTTP request to accounting system (no tab switching!)

Conversation marked as done by user

When does this trigger fire?

Triggers when a user manually changes a conversation from "Open" to "Done".

Does NOT trigger when:

  • Automation changes status to "Done"

  • Integration changes status to "Done"

Additional filter options:

You can limit the trigger to specific channel types (e.g., WhatsApp only), specific channels (e.g., WhatsApp number 1 only), or inboxes.

Common use cases:

  • Feedback survey after ticket closure

  • CRM synchronization via HTTP request

  • Delayed follow-up (wait 3 days → "Is everything going well?")

  • Quality assurance (add label + notify team lead)

Time-based & integration triggers

Date / time reached

When exactly does this trigger fire?

This trigger runs based on a date / time contact attribute.

How it works:

  1. You have a contact attribute of type "Date" or "Date/Time" (e.g., "Birthday", "Contract end", "Onboarding start")

  2. You select this attribute in the trigger

  3. Optional: You set a time offset (e.g., "14 days before" or "7 days after")

  4. When the date (+ time offset) is reached → Automation triggers

Time offset examples:

  • "3 days before" → Automation runs 3 days before the date

  • "1 week later" → Automation runs 1 week after the date

  • No time offset → Automation runs exactly on the date

Annual recurrence:

Activate toggle → Automation runs every year on the same date (perfect for birthdays)

Important: The contact attribute must be filled in for the contacts, otherwise the automation won't trigger!

Common use cases:

  • Birthday greetings: Contact attribute "Birthday" + Annual recurrence + WhatsApp template "Happy Birthday!"

  • Contract expiration: Contact attribute "Contract end" + Time offset "14 days before" + Reminder

  • Onboarding follow-up: Contact attribute "Onboarding start" + Time offset "7 days later" + "How's it going?"

  • Payment reminders: Contact attribute "Next payment" + Time offset "3 days before" + Reminder

Webhook received

This trigger runs when your webhook URL receives an HTTP request from an external tool.

How it works:

  1. You create the automation with webhook trigger

  2. Superchat generates a unique webhook URL

  3. You copy this URL into your external tool (e.g., Shopify, Make, Zapier)

  4. When the external tool sends a request to the URL → Automation triggers

Webhook data is NOT automatically available!

The external tool does send data (JSON), but you must explicitly specify which fields you need:

  1. In trigger setup: Open "Saved variables"

  2. Select fields from the webhook body

  3. Give each variable a name (e.g., order_number, amount, customer)

  4. Only then can you use them as automation variables

Example - Shopify webhook:

Shopify sends: {"order_id": "12345", "total": "99.99", "customer": "Max Müller"}

You map:

  • order_id → Variable order_number

  • total → Variable amount

  • customer → Variable customer

Use in message: "Thanks {{variable.customer}}! Your order {{variable.order_number}} for {{variable.amount}} euros has been received."

Common use cases:

  • E-commerce: Shopify "Order placed" → Confirmation message with details

  • CRM: HubSpot "Deal won" → Start onboarding flow

  • Appointment tools: Calendly "Appointment booked" → Reminder 1 day before

  • Support: Zendesk "Ticket closed" → Feedback survey

Did this answer your question?