Triggers

Overview

A trigger is the first node in every automation. It defines who gets enrolled and when. Each workflow has exactly one trigger. If a contact already has an active run in this workflow, a second trigger event will not start another run (the enrollment lock holds), unless your re-entry policy allows it. See Re-entry and frequency.

Chat message matched

Fires when a visitor in one of your chatbots sends a message that matches your rules. Best for hot-lead routing, intent-based handoffs, and conversational lead capture.

Fields

• Chatbots: which chatbots to listen to. Leave empty to listen to all.
• Mode: keyword (exact phrase match) or semantic (vector similarity, paraphrase-aware).
• Keywords / phrase: the strings to look for.
• Match type (keyword mode): any fires if any keyword matches, all requires every keyword.
• Case sensitive: off by default.
• Whole word (keyword mode): on by default. Avoids partial matches like "costume" firing for "cost".

Make sure your chatbot already exists and has lead capture enabled. The trigger only fires after Grivo has identified the visitor as a contact. See Lead capture.

Added to list

Fires when a contact joins a specific list, either by importing a CSV, completing a signup form, or being added via the API or another automation.

Fields

• List: pick the list to watch. Use the inline + Create list option if you don't have one yet.

This is the most common trigger for welcome series and newsletter onboarding. See Use cases.

Contact tagged

Fires when a specific tag is applied to a contact. Tags get applied manually, from the chatbot, from another automation's Add tag action, or via API.

Fields

• Tag: the exact tag string to watch (e.g. hot-lead, trial-expired).

Tags are case-sensitive. Pick a naming convention and stick to it: kebab-case works well.

Manual

Fires only when you explicitly start a run from the dashboard or call the API. Useful for one-off VIP sequences, testing in production safely, or kicking off campaigns from external tools.

Fields

• No configuration. Start runs from the workflow detail page or via POST /api/v1/automations/:id/run. See API getting started.

Coming soon

• Form submitted: fires when a specific form (newsletter, demo request) is submitted. Track our changelog for the rollout.

Next steps