Trigger and Action Libraries

Explore what can start a workflow and what it can do next

Overview

Every workflow begins with a trigger — the event that kicks things off. After that, it moves through a series of actions — steps you define to automate your support, ops, or communication processes.

This section outlines the triggers and actions currently supported in Conduit.

Trigger Blocks

Triggers define when a workflow should run and what data gets passed into it.

Reservation Events

• New Reservation: Fires when a reservation is created

• Check-in: Fires when a guest checks in

• Check-out: Fires when a guest checks out

• Reservation Status Updated: Fires when the reservation's status changes (e.g. confirmed → cancelled)

Contact Events

• Conversation Tag Added: Fires when a tag is applied to a conversation. Great for escalations or category-based workflows

Manual Events

• Manual Trigger: Lets you manually start a workflow from a conversation or reservation. Useful for testing or on-demand workflows

Looking for something else? You can request additional triggers directly from the trigger picker.

Action Blocks

Actions define what happens after a trigger. You can chain together as many as needed to build logic-rich workflows.

Message & Communication

• Send SMS message

• Send WhatsApp message

• Send Email

• Send Slack message

• Notify a contact: Internal or external contact, depending on setup

Control Flow & Utility

• Add Delay: Wait a set period before proceeding

• Add Filter: Only continue if certain conditions are met

Routing & Assignment

• Assign to: Route the conversation to a specific teammate or inbox

AI Actions

• Agent Injection: Insert a human-looking AI message into the conversation

• Agent Injection (Phone): Same idea, but styled for phone message threads

• Send AI Message: Structured AI message using a templated tone or style

Don’t see the action you need? Just like with triggers, you can request more from the action picker.