Skip to main content
A platform event trigger runs an internal agent when something happens in your Conduit workspace: a reservation is created, a task is assigned, a call is missed, a guest pays in a portal. These are the same events that start workflows, so you don’t need to build a companion workflow. Pick the event, and the agent runs every time it fires. Use a platform event when the right response depends on judgment. When a cleaning status changes, a workflow can send the same message every time. An agent can check whether a guest arrives today, whether they asked for early check-in, and whether a message would help at all. Open the agent and select Runs on > Workflow. The sidebar row shows how many platform event triggers are active, or Setup when none are.

Event categories

Reservations and appointments

New and modified reservations and appointments, reservation labels, and runs timed to check-in or check-out.

Contacts and conversations

New contacts, contact attributes and labels, conversation tags and escalations.

Tasks

Tasks created, modified, started, assigned and completed.

Operations, calls and widget

Cleaning status changes, completed and missed calls, and widget forms and sessions.

Portals

Every guest portal event, from the first view to payments, deposits, check-in steps and reviews.

Integrations

Workflow webhooks, Stripe and Jobber.
The picker only offers events your workspace can produce. For example, portal events appear once your workspace uses Portals, and Stripe and Jobber events appear once those connections are set up.

Add a trigger

1

Pick an event

Select Add trigger, then search for the event or pick it from its category.
2

Narrow it down

Under Filters, choose which events should start the agent, such as only reservations in one inbox. Every filter is optional. For Check-in and Check-out, set the Timing instead. Each event page lists its filters.
3

Write the task

Under Task, tell the agent what to do with this event. Conduit sends the task to the agent with the event payload each time the trigger fires. The task is optional.
4

Save

Select Add trigger.
You can add each event once per agent. Check-in and Check-out are the exception: add them as many times as you need, each with its own timing.

How filters work

Filters use the same options as the workflow builder for that event. Leaving every filter empty runs the agent on every event of that type. Events without filters say so in the sheet: the agent runs on every event of that type. Many events can be filtered by Inbox. An empty inbox means any inbox. For most events, once you set a filter that depends on the inbox, such as a tag or a status, you also need to pick the inbox. The sheet shows “Select an inbox to use these filters” until you do. Select Clear to remove every filter from a trigger.

Write a good task

The agent gets the event payload and your task, then uses its tools to look up anything else. A good task says:
  • What the event means for this agent. “A reservation was just cancelled.”
  • What to check. “Look for open cleaning tasks for that stay.”
  • What to do. “Cancel them and post a note to #housekeeping in Slack.”
  • When to do nothing. “If check-in was more than 30 days away, do nothing.”

Test a trigger

Select Mock event while editing a trigger to run the agent once with an empty mock payload. To test with a realistic payload, use Run now > Workflow instead, pick the event type, and paste the payload as JSON. See Run now with a mocked trigger. Check-in and Check-out triggers can’t be mocked, because Conduit fires them per reservation.

Manage triggers

Each trigger in the list shows its event, its filters, and whether it’s Active or Inactive.
  • Use the switch to turn a trigger on or off.
  • Select edit to change its filters, timing or task.
  • Select delete to remove it. Deleting a trigger can’t be undone.

All platform events

In the agent sidebar, platform events live under Runs on > Workflow, because they’re the same events that power workflows.