@devries-cameron20 / composio Mirror · read-only / commits / 7086db7c9
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 22, 09:30 UTC

docs: update creating-triggers page with new video and step-by-step dashboard flow

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Sushmithamallesh committed Feb 10, 2026 at 05:56 UTC 7086db7c984820b0bdfbc5564dee2422906f2c7f
3 files changed +13 -14
docs/content/docs/setting-up-triggers/creating-triggers.mdx
+13 -14
@@ -18,18 +18,22 @@ You can create triggers using the [SDK](#using-the-sdk) or the Composio [dashboa
18
19 Before creating a trigger, inspect the trigger type to see what configuration it requires. Then create the trigger with the required config.
20
21 +<Callout>
22 +When you pass a `user_id`, the SDK automatically finds the user's connected account for the relevant toolkit. If the user has multiple connected accounts for the same toolkit, it uses the most recently created one. You can also pass a `connected_account_id`/`connectedAccountId` directly if you need more control.
23 +</Callout>
24 +
25 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
26 <Tab value="Python">
27 ```python
28 from composio import Composio
29
26 -composio = Composio(api_key="your-api-key")
30 +composio = Composio()
31 user_id = "user-id-123435"
32
33 # Check what configuration is required
34 trigger_type = composio.triggers.get_type("GITHUB_COMMIT_EVENT")
35 print(trigger_type.config)
32 -# Returns: {"properties": {...}, "required": ["owner", "repo"], ...}
36 +# Returns: {"properties": {"owner": {...}, "repo": {...}}, "required": ["owner", "repo"]}
37
38 # Create trigger with the required config
39 trigger = composio.triggers.create(
@@ -44,7 +48,7 @@ print(f"Trigger created: {trigger.trigger_id}")
48 ```typescript
49 import { Composio } from '@composio/core';
50
47 -const composio = new Composio({apiKey: "your-api-key"});
51 +const composio = new Composio();
52 const userId = 'user-id-123435';
53
54 // Check what configuration is required
@@ -74,15 +78,10 @@ The trigger instance uses the toolkit version configured during Composio initial
78
79 ## Using the dashboard
80
77 -Navigate to [Auth Configs](https://platform.composio.dev?next_page=%2Fauth-configs), select an auth config, and click "Add Trigger". Switch to the "Active Triggers" tab to find the trigger ID.
78 -
79 -<Video src="/videos/enabling-triggers.mp4" poster="/images/enabling-triggers-poster.png" caption="Creating a trigger from the dashboard" />
80 -
81 -Some triggers require additional configuration. The dashboard prompts you for any required fields during setup.
81 +1. Navigate to [Auth Configs](https://platform.composio.dev?next_page=%2Fauth-configs) and select the auth config for the relevant toolkit
82 +2. Navigate to **Active Triggers** and click **Create Trigger**
83 +3. Select the connected account for which you want to create a trigger
84 +4. Choose a trigger type and fill in the required configuration
85 +5. Click **Create Trigger**
86
83 -<Figure
84 - src="/images/trigger-config.png"
85 - alt="Trigger configuration example"
86 - caption="Example: Gmail trigger configuration"
87 - size="sm"
88 -/>
87 +<Video src="/videos/triggers-creation.mp4" caption="Creating a GitHub Star Added trigger from the dashboard" />
docs/public/videos/enabling-triggers.mp4
Binary files a/docs/public/videos/enabling-triggers.mp4 and /dev/null differ
docs/public/videos/triggers-creation.mp4
Binary files /dev/null and b/docs/public/videos/triggers-creation.mp4 differ