> ## Documentation Index
> Fetch the complete documentation index at: https://composio-preview.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating triggers

> Activate a trigger for a user so events start flowing

A trigger watches for one event (like `GITHUB_COMMIT_EVENT`) on one user's connected account. Create one, and events start flowing to your [subscription or webhook URL](https://composio-preview.mintlify.site/docs/setting-up-triggers/subscribing-to-events.md). For the bigger picture, see [Triggers](https://composio-preview.mintlify.site/docs/triggers.md).

The user needs a [connected account](https://composio-preview.mintlify.site/docs/authentication) for the toolkit you want to monitor. See [Authentication](https://composio-preview.mintlify.site/docs/authentication) if you haven't set that up.

## Inspect the trigger type

To connect trigger setup to a working agent, follow [Run an agent when an email arrives](https://composio-preview.mintlify.site/examples/email-triggered-agent.md).

Each trigger type declares the config it needs. Check it before you create, so you pass the right fields.

> [tab] Python
>
> ```python theme={null}
> from composio import Composio
>
> composio = Composio()
>
> trigger_type = composio.triggers.get_type("GITHUB_COMMIT_EVENT")
> print(trigger_type.config)
> # {"properties": {"owner": {...}, "repo": {...}}, "required": ["owner", "repo"]}
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
>
> const composio = new Composio();
>
> const triggerType = await composio.triggers.getType('GITHUB_COMMIT_EVENT');
> console.log(triggerType.config);
> // {"properties": {"owner": {...}, "repo": {...}}, "required": ["owner", "repo"]}
> ```

> [tab] API
>
> ```bash theme={null}
> curl -X GET https://backend.composio.dev/api/v3.1/triggers_types/GITHUB_COMMIT_EVENT \
>   -H "x-api-key: $COMPOSIO_API_KEY" | jq '.config'
> ```

## Create the trigger

Pass the user, the trigger slug, and the config the type requires.

> [tab] Python
>
> ```python theme={null}
> from composio import Composio
>
> composio = Composio()
> user_id = "user-id-123435"
>
> # The user needs a connected account for this toolkit before this runs.
> # Set it up first. See /docs/authentication.
> trigger = composio.triggers.create(
>     slug="GITHUB_COMMIT_EVENT",
>     user_id=user_id,
>     trigger_config={"owner": "your-repo-owner", "repo": "your-repo-name"},
> )
> print(f"Trigger created: {trigger.trigger_id}")
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
>
> const composio = new Composio();
> const userId = 'user-id-123435';
>
> // The user needs a connected account for this toolkit before this runs.
> // Set it up first. See /docs/authentication.
> const trigger = await composio.triggers.create(userId, 'GITHUB_COMMIT_EVENT', {
>   triggerConfig: { owner: 'your-repo-owner', repo: 'your-repo-name' },
> });
> console.log(`Trigger created: ${trigger.triggerId}`);
> ```

> [tab] API
>
> ```bash theme={null}
> curl -X POST https://backend.composio.dev/api/v3.1/trigger_instances/GITHUB_COMMIT_EVENT/upsert \
>   -H "x-api-key: $COMPOSIO_API_KEY" \
>   -H "Content-Type: application/json" \
>   -d '{"user_id": "user-id-123435", "trigger_config": {"owner": "your-repo-owner", "repo": "your-repo-name"}}'
> ```

You only pass a `user_id`. Composio resolves that user's connected account for the toolkit automatically.

### Targeting a specific connected account

If a user has more than one connected account for the toolkit, Composio uses the first active connection for the user and the trigger's toolkit. Pass a connected account ID to pick exactly which account the trigger watches.

> [tab] Python
>
> ```python theme={null}
> # The SDK overload omits the supported user_id + connected_account_id combination.
> trigger = composio.triggers.create(  # type: ignore[call-overload]
>     slug="GITHUB_COMMIT_EVENT",
>     user_id=user_id,
>     connected_account_id="ca_def456",
>     trigger_config={"owner": "your-repo-owner", "repo": "your-repo-name"},
> )
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
> const composio = new Composio();
> const userId = 'user-id-123435';
> const trigger = await composio.triggers.create(userId, 'GITHUB_COMMIT_EVENT', {
>   connectedAccountId: 'ca_def456',
>   triggerConfig: { owner: 'your-repo-owner', repo: 'your-repo-name' },
> });
> ```

> [tab] API
>
> ```bash theme={null}
> curl -X POST https://backend.composio.dev/api/v3.1/trigger_instances/GITHUB_COMMIT_EVENT/upsert \
>   -H "x-api-key: $COMPOSIO_API_KEY" \
>   -H "Content-Type: application/json" \
>   -d '{"user_id": "user-id-123435", "connected_account_id": "ca_def456", "trigger_config": {"owner": "your-repo-owner", "repo": "your-repo-name"}}'
> ```

Trigger instances default to the `'latest'` toolkit version. If you parse payloads against a fixed schema, [pin a version](https://composio-preview.mintlify.site/docs/tools-direct/toolkit-versioning.md#choosing-between-latest-and-a-pinned-version) at SDK initialization.

The trigger instance is created. Next, [receive its events](https://composio-preview.mintlify.site/docs/setting-up-triggers/subscribing-to-events.md) and test with a new matching event in the provider. If nothing arrives, follow [Troubleshooting triggers](https://composio-preview.mintlify.site/docs/setting-up-triggers/troubleshooting.md).

## Next

> [card] [Receiving events](https://composio-preview.mintlify.site/docs/setting-up-triggers/subscribing-to-events.md)
>
> Get trigger events locally with the SDK or in production over your webhook URL
