Changes to the _New Connection_ Trigger

(John Jackson) #1

Customers have been finding New Connection difficult to use because it only triggers the very first time a user connects to a bot.

You’ve also told us that you want to use this trigger every time a user starts a new conversation (when clicking Start in Telegram or Get Started in Messenger).

So later today, this trigger will be renamed New Conversation, and it will fire every time a user:

  • Clicks Get Started in Messenger.
  • Clicks Start or types /start in Telegram.
  • Installs your bot in Slack.

The welcome text will also be shown for each of these events, right before New Conversation triggers.

This does mean that the trigger might fire multiple times for the same user, so be prepared for that.

(John Jackson) #2

We’ve now made the change, so you’ll find that New Connection is now New Conversation and triggers every time someone starts (or restarts) a conversation with a bot.

To be precise:

  • Clicks Get Started in Messenger.
  • Clicks Start or types /start in Telegram.
  • Installs your bot in Slack.
(Chaitanya Shravanth) #3

Hi John, the new conversation trigger doesn’t have all the outputs, that is User Name and handle. The documentation says that the only difference between the outputs of New Message and New Conversation is the message and the message type. Is this a miss or intentional?

(John Jackson) #4

The docs are wrong actually, we’ll fix right now. Those outputs are only currently available on New Message. We’re looking into the possibility of adding the New Conversation.

Thanks for the report.

(John Way) #5

@johnjackson

Is the New Conversation trigger deprecated? I don’t see that as a trigger option.

(Daniel Beckett) #6

Hi @John_Way

That trigger is no longer available.

There is instead the New Message and Catch-All triggers that can be used.

When users first connect to the bot a message is sent in the background for ‘start’ so if you need a flow to run for first time users you can filter for ‘start’ as a keyword.