Automation triggers

A trigger is the event that enrols a contact into an automation. You pick it at the top of the visual editor: click the trigger card and choose under Start this automation when…. This page lists every trigger Nybero has, what fires it, and how to configure it.

Multiple triggers per automation

An automation can have more than one trigger. In the editor, hover next to the trigger card and click the + to add another. Any of the triggers enrols the contact — for example, “Inbound message keyword START” or “Tag vip is added” can both lead into the same welcome flow.

Whatever the trigger, the same rules apply: a contact enters a given automation once per version, and never a second time while they’re still mid-flow. See Automations overview for details.

Contact is created

Fires when: a brand-new contact appears in your workspace — added by hand, imported, created by an inbound webhook, created by an opt-in, or created automatically when an unknown number messages you for the first time.

Configuration: none — every new contact qualifies.

Example: start a welcome sequence the moment a new lead lands in your CRM.

Caution

“New contact” doesn’t automatically mean “24-hour window open”. A contact imported from a list has never messaged you, so your first step usually needs to be an approved template (or a Condition on “24-hour window is open”). See Steps.

Inbound message keyword

Fires when: the contact sends you a WhatsApp message that matches your keyword. Button taps count too — when someone taps a reply button, the button text arrives as their message, so buttons can trigger keyword automations.

Configuration:

• The match mode:
  • Inbound contains the word (default) — the keyword appears as a whole word anywhere in the message (“price” matches “what’s the price?”).
  • Inbound contains the text — the text appears anywhere, even inside another word.
  • Inbound starts with / Inbound ends with — the message begins or ends with your text.
  • Inbound matches exactly — the whole message is exactly your text.
• The keyword or text itself. Matching ignores upper/lower case.

Example: contact sends “PRICE” → automation replies with your price list and a follow-up. (Full recipe in Recipes.)

Tip

Because the contact just messaged you, the 24-hour window is guaranteed open at the start of a keyword automation — free-form Send message steps, forms and product cards all work immediately.

Tag is added

Fires when: a tag is assigned to a contact — by you on the contact page, by another automation’s Add tag step, or by an integration.

Configuration: choose a specific tag from the picker, or leave it on Any tag to fire on every tag assignment. You can also type a new tag name; unknown tags are created automatically.

Example: whenever the tag webinar-signup is added, start the webinar reminder sequence.

Note

This trigger reacts to native Nybero tags (the ones under Contacts → Tags). ActiveCampaign tags are a separate system and don’t fire it — see ActiveCampaign integration.

Form submitted

Fires when: a contact submits one of your WhatsApp forms (a flow filled in directly inside the chat — see Forms).

Configuration: pick a specific form from the dropdown, or Any form to fire on every submission. If you have no forms yet, create one first under Forms.

Example: after someone completes your “Book a consultation” form, tag them and hand the chat to your AI agent for scheduling.

Webhook received

Fires when: an external system sends data to one of your inbound webhook URLs and Nybero has processed it into a contact — for example a signup from your website, a funnel tool, or Zapier/Make. Set webhooks up under Integrations → Webhooks.

Configuration: pick a specific webhook from the dropdown, or Any webhook to fire whenever any of them receives data. If the list is empty, create a webhook first under Integrations → Webhooks.

Example: your landing page posts each webinar registration to a Nybero webhook → the automation sends the WhatsApp confirmation and schedules the reminders.

Manual / API enrolment

Fires when: you (or your developer) enrol a contact explicitly via the Nybero API — nothing happens automatically.

Configuration: none.

Example: your own backend enrols a customer into an onboarding flow right after their purchase, at exactly the moment your system decides.

This trigger is the right choice when the “event” lives outside Nybero and you want full control over who enters and when. Your developer calls the enrol endpoint of the API with the automation and contact; everything after that behaves like any other run.

Which trigger should I use?

You want to react to…	Use
A contact writing a specific word or tapping a button	Inbound message keyword
A brand-new lead appearing in the CRM	Contact is created
A label you or a flow put on a contact	Tag is added
A WhatsApp form being completed	Form submitted
A signup/event in an external tool or website	Webhook received
Your own system deciding programmatically	Manual / API enrolment

Next: build what happens after the trigger — see Steps.