Vendu Docs
ProductDevelopers
/

Product

Getting started

  • What Vendu does
  • How the agent decides what to say

Team

  • Roles and permissions

Orders

  • The order lifecycle

Automation

  • Triggers and actions

Apps

  • What apps are

Conversations

  • When the agent hands over

Developers

API

  • Build on Vendu
  • API error codes
  • Make your first API call
  • MCP server
  • Migrate from offset to cursor pagination
  • Outbound webhooks
  • Rate limits
  • Versioning and deprecation

Apps

  • Build an app

automation · reference

Triggers and actions

Every event a workflow can start from and every action it can take, with the conditions each one needs.

A workflow is one trigger, optional conditions, and a list of actions. This page lists what is available.

Triggers

Message events

TriggerFires when
message.receivedAny customer message arrives
message.contains_keywordA message contains one of the keywords you list
intent.detectedThe agent classifies a message as a particular intent
conversation.startedA new conversation begins
no_reply_timeoutNobody has replied for the number of minutes you set

Customer events

TriggerFires when
customer.first_messageSomeone writes for the first time
customer.returnedSomeone writes again after the number of days you set
customer.taggedA specific tag is added to a contact

Order events

TriggerFires when
order.createdAn order is created
order.status_changedAn order reaches a status you name
order.abandoned_cartAn order sits unfinished for the minutes you set
order.deliveredAn order is delivered

Agent events

TriggerFires when
ai.confidence_belowThe agent is less sure than the threshold you set
ai.escalation_requestedThe agent asks for a human
supervisor.rejectedA safety check rejected a draft answer

Time and other events

TriggerFires when
schedule.cronOn a schedule you define
delay.after_triggerA set time after another trigger fired
csat.submittedA customer rates a conversation
referral.completedA referral is completed

Actions

Change how the agent behaves

ActionEffect
ai.inject_instructionAdds an instruction for this conversation only
ai.override_toneChanges tone for this conversation
ai.set_contextSwitches mode: sales, support or onboarding

These affect one conversation. They do not change your agent's settings.

Talk to the customer

ActionEffect
send.messageSends a message; supports {{ variables }}
send.product_carouselSends products matching a filter
send.referral_inviteSends your referral link

Organise work

ActionEffect
tag.add / tag.removeTags a contact
assign.to_operatorAssigns to a specific person
assign.autoAssigns round-robin or to whoever is least busy
note.addAdds an internal note

Assignment pauses the agent by default: once a person owns a conversation, the agent should not also answer.

Control the flow

ActionEffect
delay.waitWaits, then continues
wait_until_replyWaits for the customer, with a timeout branch
condition.branchSplits into two paths
workflow.stopEnds the workflow

wait_until_reply has no "on reply" branch on purpose: if the customer answers, the workflow simply carries on with the actions after it — the same thing a person would do. The onTimeout list runs only when they do not.

Reach outside

ActionEffect
webhook.sendCalls your endpoint
skill.invokeCalls a tool from an installed app
code.executeRuns sandboxed code
metric.incrementCounts something

Bring in a human

ActionEffect
escalate_to_humanHands the conversation over
escalate_with_contextHands over with a summary of why

Two things worth knowing before you build one

Workflows run on every matching event, including replays. Delivery is at-least-once, so an action that creates or charges something must tolerate running twice. Sending a message twice is visible to the customer; design around it rather than assuming it cannot happen.

A workflow that writes to the customer competes with the agent. If a workflow sends a message while the agent is also answering, the customer sees both. Pause the agent (assign.*) or stop the workflow when the agent is handling the conversation.

Trying one safely

Every workflow can be dry-run before it is enabled: it reports what it would have done without doing it. Use it for anything that sends a message or touches an order.

Last updated 2026-07-29

On this page

  • Triggers
  • Message events
  • Customer events
  • Order events
  • Agent events
  • Time and other events
  • Actions
  • Change how the agent behaves
  • Talk to the customer
  • Organise work
  • Control the flow
  • Reach outside
  • Bring in a human
  • Two things worth knowing before you build one
  • Trying one safely