Update triggers docs (#3678)

* docs: introduce triggers list & triggers run command

* docs: add KO triggers docs

docs/en/enterprise/guides/microsoft-teams-trigger.mdx

@@ -37,16 +37,28 @@ print(result.raw)
 
 The crew parses thread metadata (subject, created time, roster) and generates an action plan for the receiving team.
 
-## Sample payloads & crews
+## Testing Locally
 
-The [Microsoft Teams examples](https://github.com/crewAIInc/crewai-enterprise-trigger-examples/tree/main/microsoft-teams) include:
+Test your Microsoft Teams trigger integration locally using the CrewAI CLI:
 
-- `chat-created.json` → chat creation payload processed by `teams-chat-created-crew.py`
+```bash
+# View all available triggers
+crewai triggers list
 
-The crew demonstrates how to extract participants, initial messages, tenant information, and compliance metadata from the Microsoft Graph webhook payload.
+# Simulate a Microsoft Teams trigger with realistic payload
+crewai triggers run microsoft_teams/teams_message_created
+```
+
+The `crewai triggers run` command will execute your crew with a complete Teams payload, allowing you to test your parsing logic before deployment.
+
+<Warning>
+  Use `crewai triggers run microsoft_teams/teams_message_created` (not `crewai run`) to simulate trigger execution during development. After deployment, your crew will automatically receive the trigger payload.
+</Warning>
 
 ## Troubleshooting
 
 - Ensure the Teams connection is active; it must be refreshed if the tenant revokes permissions
+- Test locally with `crewai triggers run microsoft_teams/teams_message_created` to see the exact payload structure
 - Confirm the webhook subscription in Microsoft 365 is still valid if payloads stop arriving
 - Review execution logs for payload shape mismatches—Graph notifications may omit fields when a chat is private or restricted
+- Remember: use `crewai triggers run` (not `crewai run`) to simulate trigger execution