Triggers & Actions
A complete reference of available triggers and actions for Wyatt automations.
How Triggers and Actions Work
Every automation starts with a trigger — the event that causes it to run. When the trigger fires, Wyatt executes one or more actions in sequence. Together, they form the building blocks of your automation.
Available Triggers
Document Created
Fires when a new document is created in your workspace. You can scope it to a specific folder so it only triggers for documents in that location.
Example: When a document is created in the "Meeting Notes" folder, automatically run the Summarize skill.
Row Added
Fires when a new row is added to a specific database table. This is one of the most commonly used triggers for data-driven workflows.
Example: When a row is added to the "Support Tickets" table, send a notification to the support team.
Row Updated
Fires when a field in an existing row changes. You can optionally filter to a specific column — for instance, only trigger when the "Status" column changes.
Example: When a task's status changes to "Done," update the completion date automatically.
Schedule
Fires on a recurring time-based schedule (daily, weekly, monthly, or a custom cron expression). See the Scheduling guide for details.
Example: Every Friday at 5 PM, generate a summary of the week's completed tasks.
Document Updated
Fires when an existing document is edited. Useful for keeping other systems in sync or logging changes.
Example: When a policy document is updated, notify the compliance team.
Triggers include context about the event — like which document was created or which row changed. Actions can use this context to make decisions.
Available Actions
Create Document
Creates a new document in your workspace. You can specify the folder, title, and initial content. Combine this with template text or AI-generated content for powerful workflows.
Example: When a new client row is added, create a "Client Onboarding" document pre-filled with their details.
Update Row
Modifies one or more fields in a database row. Useful for setting timestamps, changing statuses, or filling in computed values.
Example: When a task is marked as "Done," set the "Completed At" column to today's date.
Send Notification
Sends a notification to one or more workspace members. You can target specific people, a role, or the person referenced in a Person column.
Example: When a document is added to "Needs Review," notify the assigned reviewer.
Run Skill
Executes a built-in or custom skill and stores the result. This is how you bring AI into your automations.
Example: When a meeting notes document is created, run the "Extract Action Items" skill and add them to the Tasks database.
Create Row
Adds a new row to a database table with specified field values. Useful for logging events or creating records from other triggers.
Example: When a document is created, add a row to the "Document Log" table with the document name and creation date.
Send Email
Sends an email to a specified address. You can use information from the trigger to personalize the subject and body.
Example: When a support ticket status changes to "Resolved," email the customer with a confirmation.
You can chain multiple actions in a single automation. For example: run a skill, create a row from the result, and send a notification — all from one trigger.
Combining Triggers and Actions
Here are some complete automation examples to inspire you:
| Automation | Trigger | Actions |
|---|---|---|
| Meeting follow-up | Document created in "Meeting Notes" | Run Summarize skill, create rows in Tasks table for action items |
| Task escalation | Row updated (Priority changed to "Urgent") | Send notification to team lead, update row with escalation timestamp |
| Weekly report | Schedule (every Monday, 8 AM) | Run "Weekly Summary" skill on Tasks database, create document with results |
| Client onboarding | Row added to "Clients" table | Create onboarding document, send welcome email, notify account manager |
Be mindful of automation loops. For example, if an automation triggers on row updates and also updates a row, it could run repeatedly. Wyatt includes safeguards, but it's good practice to design your triggers carefully.