APM Event System
APM broadcasts real-time events as tool calls that MCP servers can implement, enabling reactive workflows and automation. Events are the nervous system of APM's automation capabilities.
- Something happens in APM - User creates a task, action is approved, etc.
- APM broadcasts a tool call - All connected MCP servers receive a tool call for the event.
- Clients react - Perform actions based on the event
Task Events
| Event | Triggered When | Event Data | Implemented |
|---|
apm_task_created | New task created | Full task object with all properties | Yes |
apm_task_updated | Task modified | Updated task + changed_fields array | No |
apm_task_started | Status → in_progress | Task object + started_by user | No |
apm_task_completed | Status → complete | Task object + completion_notes | No |
apm_task_assigned | Assignee changed | Task + previous_assignee, new_assignee | No |
apm_task_deleted | Task removed | Task ID + deletion metadata | No |
Action Events
| Event | Triggered When | Event Data | Implemented |
|---|
apm_action_created | New action needs attention | Full action object | No |
apm_action_updated | Action modified | Updated action + changes | No |
apm_action_approved | Action approved | Action + resolution_notes, approved_by | No |
apm_action_rejected | Action rejected | Action + resolution_notes, rejected_by | No |
apm_action_expired | Action auto-expired | Action + expiration reason | No |
Project Events
| Event | Triggered When | Event Data | Implemented |
|---|
apm_project_created | New project created | Full project object | No |
apm_project_updated | Project settings changed | Project + changed fields | No |
apm_project_member_added | User joined project | Project ID + user info | No |
apm_project_member_removed | User left project | Project ID + user info | No |
apm_project_archived | Project archived | Project ID + archive metadata | No |
