Anatomy of a Calendar Trigger
Every calendar trigger has three parts:- Condition — which events match (e.g., “meetings with external attendees,” “1-on-1s with my direct reports”)
- Timing — when to fire relative to the event
- Action — what the agent does (e.g., “prep me and send the briefing on iMessage,” “draft a follow-up email”)
Timing Options
| Timing | Range | Use Case |
|---|---|---|
| Minutes before | 0-120 min before start | Meeting prep, join reminders |
| Minutes after start | 0-30 min after start | ”Am I late?” checks |
| Minutes after end | 0-120 min after end | Follow-ups, summary emails |
| On event change | Fires immediately | React to reschedules and cancellations |
Creating a Calendar Trigger
Describe the automation
Example: “10 minutes before any meeting with external attendees, prep me and send the briefing on iMessage.”
Meeting Presence Check
Triggers that fire after a meeting starts can check whether you’ve joined the Google Meet call:- Trigger fires N minutes after event start
- Agent checks Google Meet API for who’s in the call
- If you’re not present, sends an iMessage alert with the Meet link
Works with Google Meet links attached to calendar events. The agent can see who has joined, who is late, and who hasn’t connected.
Common Patterns
| Pattern | Timing | What to Tell the Agent |
|---|---|---|
| Meeting prep | 10 min before | ”10 min before external meetings, prep me and send on iMessage” |
| Late check | 5 min after start | ”5 min after any meeting starts, check if I’ve joined the Meet” |
| Follow-up | 5 min after end | ”5 min after external meetings end, draft a follow-up email” |
| Schedule alert | On event change | ”When investor meetings are rescheduled, message me on iMessage” |
| Join reminder | 1 min before | ”1 min before every meeting, message me with the meeting link” |
Troubleshooting Calendar Triggers
Trigger did not fire before my meeting
Trigger did not fire before my meeting
Check Settings > Automations to confirm the trigger is enabled. Verify the condition matches the event (e.g., “external attendees” requires at least one non-organization attendee). Also confirm Read Mode is off — it pauses action-taking automations.
Trigger fires for the wrong events
Trigger fires for the wrong events
Edit the trigger condition to be more specific. Instead of “all meetings,” try “meetings with external attendees” or “meetings with more than 2 attendees.” The agent uses the condition text to match events.
Meeting prep arrives too early or too late
Meeting prep arrives too early or too late
Edit the trigger timing in Settings > Automations. Adjust the “minutes before” value. For back-to-back meetings, 5 minutes works better than 10.
How Scheduling Works
Calendar triggers use AWS EventBridge with timezone-aware scheduling. When you create a trigger, Slashy identifies matching future events and schedules invocations. As events are added, rescheduled, or deleted, invocations update automatically. When a trigger fires, the agent receives full event context — title, description, attendees with RSVP status, meeting link, and your action instruction.Email Triggers
Automate actions on incoming email
Scheduled Reminders
Schedule the agent for future tasks
Agent Autonomy
What the agent can and cannot do