Skip to main content
A trigger tells an AI coworker to run a prompt every time a specific event arrives. Examples are a new message in a Slack channel, a new LinkedIn or WhatsApp message, or a new email, form response, or payment in a connected app. The coworker reacts on its own, without anyone asking.

​
Trigger sources

​
Add a trigger

1

Open the coworker's triggers

Open the coworker and go to Automations → Triggers. Click Add trigger.
2

Choose a source

In Choose a trigger source, pick Slack, LinkedIn, WhatsApp, or Integration, then set it up as described below.
3

Tell the coworker what to do

Fill in the final step:
  • Name (optional, up to 100 characters). If you leave it empty, the trigger uses the event name, such as “New message in #support”.
  • Prompt (required, up to 10,000 characters). What the coworker should do each time. For example: “Summarize the new file and send a Slack message to #updates”.
  • Only run when… (optional, up to 2,000 characters). A plain-language condition. See Only run when….
4

Check the expected actions

Vybe reads your prompt and shows chips for the actions each run should take, such as sending a Slack message. Remove any that don’t apply, or add missing ones. Runs that skip an expected action show a Verification warning.
5

Create it, then turn it on

Click Create Trigger. New triggers start off. Turn on the switch on the trigger card to start listening.
You can also ask the coworker to set up a trigger in chat. It creates the trigger and switches it on for you.
Whenever someone posts in #support, check whether it’s a bug report. If it is, open a Linear issue and reply in the thread with the link.

​
Slack

The New Slack message trigger runs “on every new human message, including thread replies” in one channel.
  1. In Slack channel, choose a channel. The list shows channels the coworker can use.
  2. Write the prompt and create the trigger.
Turning the trigger on joins the coworker to the channel if it’s public. This only works when the coworker’s Slack capability is set to Full access; otherwise, invite the coworker to the channel first. For a private channel, always invite the coworker in Slack first. Messages from bots, including other coworkers, don’t fire the trigger. If no channels are listed, you’ll see “No channels available. Install the agent in Slack or invite it to a channel, then retry.” See Slack to add the coworker to Slack and to channels.
To reply or post in the channel, the coworker needs Read and write access to it. A channel the coworker joins when you turn on the trigger starts at Read.

​
LinkedIn and WhatsApp

These triggers are in Beta. They use your own connected account. See LinkedIn and WhatsApp.
  1. Choose the account. If you haven’t connected one yet, click the connect button to connect it now.
  2. Choose the Event. A short description under the list explains when it fires.
  3. If the coworker doesn’t have enough access to the account yet, approve access when asked.
  4. Write the prompt and create the trigger.
Some LinkedIn events only work with certain LinkedIn products. New connections and new followers are for LinkedIn Classic only and can arrive up to six hours late.
New LinkedIn message and New WhatsApp message fire for messages you receive and messages you send. To react only to incoming messages, add a condition such as “Only run when the message was sent to me by someone else.”

​
Integration

Integration triggers work with connected apps that publish events. See Integrations to connect an app. The setup is a short wizard:
  1. Choose an integration. Search for the app.
  2. Account. Pick the connected account to listen on, or connect a new one.
  3. Integration access. If the coworker can’t use that account yet, you’re asked to “Give your agent access to the account before continuing.” Approve access to continue.
  4. Triggers. “Select the event that should trigger your agent.”
  5. Configure. Some events have settings, such as which folder or calendar to watch.
  6. Prompt. Write what the coworker should do, then click Create Trigger.

​
Turn a trigger on or off

Each trigger card has an on/off switch. When you switch on an integration, LinkedIn, or WhatsApp trigger, Vybe checks that the coworker can still use the account. If it can’t, a dialog asks you to “Give your agent access to the account before enabling this trigger.” Events that arrive while a trigger is off aren’t replayed when you turn it back on.

​
Only run when…

Only run when… is an optional condition written in plain language. “Describe what matters to you. Uncertain events get an agent check before any action.”
The email asks for my reply or decision, gives me a deadline, or reports blocked work. Ignore newsletters and promotions.
Events that don’t match are skipped. They still appear in the trigger’s Event history, with the reason.

​
Test the condition

Once you’ve written a condition, open Test filter without running actions:
  1. Choose a Sample source: one of the trigger’s 30 most recent events, or Paste a sample. New triggers have no events yet, so paste a Sample event such as an email or event payload.
  2. Click Test filter.
The result says Would run, Would filter, or Needs agent check, sometimes with an estimated match probability. No actions are run during the test.

​
Trigger cards

Each trigger shows:
  • The account it listens on (for LinkedIn, WhatsApp, and integration triggers) and its name. An Error badge appears when the last run failed or was blocked.
  • A model picker and the on/off switch.
  • The prompt and, if set, “Only run when:” followed by the condition.
  • Event history, every event the trigger received.
  • The number of recent runs, with a failed count. Expand it to see each run’s Input, Output, any Error, and the tool calls it made.
The Trigger actions (…) menu has:
Test trigger is a real run. The coworker follows your prompt on a test event (for Slack, the message “Test Slack message”) and can take real actions: post in Slack, send email, or update your tools. Write your prompt so a test can’t cause harm, or test where the side effects are safe.
To see every trigger run in one list, click View activity. It opens Usage & Activity → Activity filtered to trigger runs.

​
Event history

Event history on each card lists “All received events, including skipped events and their reasons.” It shows 30 events per page, with Previous and Next. Each row shows when the event arrived and its outcome, such as “done”, “failed”, Skipped, or Skipped by the agent. Expand a row to see the condition check and a View agent activity link when a run started.

​
Why an event was skipped

​
How events become runs

  • Close events are batched. When several events for the same trigger arrive in quick succession, Vybe groups them into a single run, so the coworker handles a burst together. An event that arrives after a quiet period runs right away.
  • Runs don’t overlap. A trigger never starts a new run while its previous run is still going. New events wait for the next run.
  • Every run uses credits. See Automations overview.