# Sentry Your Toolhouse AI Worker can connect to Sentry using 207 specialized tools. ## Auth Connection This service requires an auth connection to use its tools. You can set this up in your Toolhouse dashboard under [Auth Connections](https://toolhouse.app/auth-connections?authkit_slugs=sentry). ## Tools (207) ### `Sentry Access Project Information` Integration name: **SENTRY\_ACCESS\_PROJECT\_INFORMATION** Retrieves detailed information for a Sentry project, given its existing organization and project ID or slug. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------ | :------: | ----------------- | ------------------------------------------------------------------- | | `project_id_or_slug` | string | ✅ | `"sentry-python"` | ID or slug of the Sentry project. | | `organization_id_or_slug` | string | ✅ | `"sentry-sdks"` | ID or slug of the Sentry organization to which the project belongs. | ### `Sentry Add A Symbol Source To A Project` Integration name: **SENTRY\_ADD\_A\_SYMBOL\_SOURCE\_TO\_A\_PROJECT** Tool to add a custom symbol source to a Sentry project. Use when configuring symbol sources for crash symbolication. #### Parameters | Parameter | Type | Required | Example | Description | | ---------------------------- | ------- | :------: | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | `id` | string | | `"custom-symbol-source-1"` | Internal ID of the source. Must be distinct and cannot start with 'sentry:'. UUID generated if not provided. | | `url` | string | | `"https://symbols.example.com"` | Source URL. Required for HTTP sources. | | `name` | string | ✅ | `"Test Symbol Server"` | Human-readable name of the source. | | `type` | string | ✅ | `"http"` | Source type. Options: 'http' (SymbolServer HTTP), 'gcs' (Google Cloud Storage), 's3' (Amazon S3). | | `bucket` | string | | `"my-symbols-bucket"` | Bucket name. Required for S3 and GCS sources. | | `prefix` | string | | `"symbols/"` | S3 or GCS prefix path. | | `region` | string | | `"us-east-1"` | AWS region enumeration for S3 sources. | | `password` | string | | `"securepassword"` | Password for HTTP authentication. | | `username` | string | | `"symboluser"` | Username for HTTP authentication. | | `access_key` | string | | `"AKIA_EXAMPLE_KEY_ID_000"` | AWS Access Key. Required for S3 sources. | | `secret_key` | string | | `"wJalrXUtnFEMI/EXAMPLE/SECRET/KEY"` | AWS Secret Access Key. Required for S3 sources. | | `private_key` | string | | `"-----BEGIN PRIVATE KEY-----\\n...\n-----END PRIVATE KEY-----"` | GCS private key. Required for GCS sources. | | `client_email` | string | | `"service-account@project.iam.gserviceaccount.com"` | GCS email for authentication. Required for GCS sources. | | `layout__type` | string | ✅ | `"native"` | Layout type specifying the directory structure for symbols. Required for HTTP, GCS, and S3 sources. | | `layout__casing` | string | ✅ | `"default"` | Filename casing convention for symbols. Required for HTTP, GCS, and S3 sources. | | `filters__filetypes` | array | | `["pe","pdb"]` | List of file types to filter. | | `project_id_or_slug` | string | ✅ | `"my-project"` | The ID or slug of the project. | | `filters__path_patterns` | array | | `["**/*.pdb"]` | Glob patterns for debug/code file paths. | | `organization_id_or_slug` | string | ✅ | `"my-organization"` | The ID or slug of the organization. | | `filters__requires_checksum` | boolean | | `false` | Whether source requires debug checksum. Default: false. | ### `Sentry Add Organization Member Via Email` Integration name: **SENTRY\_ADD\_ORGANIZATION\_MEMBER\_VIA\_EMAIL** Invites a new member (or re-invites an existing non-accepted member) to a Sentry organization via email, allowing specification of organization and team roles. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `email` | string | ✅ | `"user@example.com"` | The email address of the user to invite or add to the organization. | | `orgRole` | string | | `"member"` | Primary organization-level role. `billing`: Manages payment/compliance. `member`: Views events/data. `manager`: Manages teams, projects, membership. `owner`: Unrestricted access. `admin`: Edits global integrations, manages projects/teams. Note: The `admin` role may have plan-specific restrictions; consider `manager` or `teamRoles`. | | `reinvite` | boolean | | `true` | If `True`, resends an invitation to a user previously invited but who has not yet accepted. | | `teamRoles` | array | | — | List of team-specific role assignments. Common roles: `contributor` (views/acts on issues, may add members per org settings) and `admin` (full team/project management). | | `sendInvite` | boolean | | `true` | If `True`, an invitation email is sent to the user. Set to `False` to add the member without an email notification. | | `organization_id_or_slug` | string | ✅ | `"my-org-slug"` | The unique identifier (ID or slug) of the Sentry organization to which the member will be added. | ### `Sentry Add Remove User Email By Id` Integration name: **SENTRY\_ADD\_REMOVE\_USER\_EMAIL\_BY\_ID** Adds or removes a secondary email for an existing Sentry user, determined by whether the email already exists for that user. #### Parameters | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------------ | | `email` | string | ✅ | `"new.user@example.com"` | The email address to be added to or removed from the user's Sentry account. Ensure this is a valid email format. | | `user_id` | string | ✅ | `"12345"` | The unique identifier of the Sentry user (e.g., numeric ID or 'self') for whom the email address is being managed. | ### `Sentry Add Team Member In Organization` Integration name: **SENTRY\_ADD\_TEAM\_MEMBER\_IN\_ORGANIZATION** Adds an existing member of an organization to one of its teams; the member must already belong to the organization, and the team must also belong to that organization. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------ | :------: | ---------------------- | ------------------------------------------------------------------------------------------------------------ | | `member_id` | string | ✅ | `"1001"` | ID of the existing organization member to be added to the team. | | `team_id_or_slug` | string | ✅ | `"backend-developers"` | The ID or slug of the team to which the member will be added. Slugs are typically lowercase and use hyphens. | | `organization_id_or_slug` | string | ✅ | `"my-awesome-org"` | The ID or slug of the organization. Slugs are typically lowercase and use hyphens. | ### `Sentry Add Team To Project` Integration name: **SENTRY\_ADD\_TEAM\_TO\_PROJECT** Grants a Sentry team access to a Sentry project within the specified Sentry organization. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------ | :------: | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | | `team_id_or_slug` | string | ✅ | `"my-team-slug"` | The unique identifier (ID) or human-readable slug for the Sentry team that will be granted access to the project. | | `project_id_or_slug` | string | ✅ | `"my-project-slug"` | The unique identifier (ID) or human-readable slug of the Sentry project. Access will be granted to this project. | | `organization_id_or_slug` | string | ✅ | `"my-organization-slug"` | The unique identifier (ID) or human-readable slug of the Sentry organization. This organization contains both the project and the team. | ### `Sentry Bulk Mutate An Organizations Issues` Integration name: **SENTRY\_BULK\_MUTATE\_AN\_ORGANIZATIONS\_ISSUES** Bulk mutate various attributes on issues within an organization. Use when you need to update status, priority, assignment, or other attributes for multiple issues at once. Maximum of 1000 issues can be mutated, with a 100 issue limit per request. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | array | | `[6942006846,6942006836]` | Issue IDs to mutate. For non-status updates, this parameter is required. For status updates, it can be omitted to update all matching issues. | | `sort` | string | | `"date"` | Sort order for issues. Defaults to 'date'. | | `inbox` | boolean | | — | Mark issue as reviewed in inbox. | | `limit` | integer | | `10` | Maximum number of issues to affect. Default: 100, Maximum: 100. | | `merge` | boolean | | — | Merge issues together. Requires multiple issue IDs. | | `query` | string | | `"is:unresolved"` | Search query for filtering issues. Defaults to 'is:unresolved' if not specified. Only used when issue IDs are not provided. | | `status` | string | | `"resolved"` | New status for the issues. | | `viewId` | string | | `"all-issues"` | View ID to apply view's query and filters. Only used when issue IDs are not provided. | | `discard` | boolean | | — | Discard the issues. | | `hasSeen` | boolean | | — | Mark the issue as seen. | | `project` | array | | `[1,2,3]` | Project IDs to filter issues by. Use -1 to include all available projects. | | `isPublic` | boolean | | — | Make the issue public or private. | | `priority` | string | | `"low"` | Priority level for the issue. | | `substatus` | string | | `"archived_until_escalating"` | Issue substatus. | | `assignedTo` | string | | `"user:12345"` | User or team to assign the issue to. Formats: \, user:\, , , team:\. | | `environment` | array | | `["production"]` | Environment names to filter issues by. Used to narrow down which issues to mutate. | | `isBookmarked` | boolean | | — | Bookmark or unbookmark the issue. | | `isSubscribed` | boolean | | — | Subscribe or unsubscribe from issue notifications. | | `statusDetails` | object | | — | Status details schema for issue resolution. | | `organization_id_or_slug` | string | ✅ | `"composio"` | The ID or slug of the organization containing the issues to mutate. | ### `Sentry Bulk Remove An Organizations Issues` Integration name: **SENTRY\_BULK\_REMOVE\_AN\_ORGANIZATIONS\_ISSUES** Permanently removes issues from an organization. If IDs are provided, queries and filtering are ignored. Maximum of 1000 issues can be removed at once. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | array | | `[6942006848]` | The list of issue IDs to be removed. If provided, queries and filtering will be ignored. If not provided, it will attempt to remove the first 1000 issues matching the query and filters. | | `sort` | string | | `"date"` | Sort order for issues. Accepts: date, freq, inbox, new, trends, user. Defaults to date if not specified. | | `limit` | integer | | `10` | The maximum number of issues to affect. The maximum allowed value is 100. | | `query` | string | | `"is:unresolved"` | An optional search query for filtering issues. A default query will apply if no view/query is set. Only used if issue IDs are not provided. | | `viewId` | string | | `"all-issues"` | The ID of the view to use. If no query is present, the view's query and filters will be applied. Only used if issue IDs are not provided. | | `project` | array | | `[1,2,3]` | The IDs of projects to filter by. Use -1 to include all available projects. | | `environment` | array | | `["production"]` | The name of environments to filter by. Used to narrow down which issues to remove based on the environment. | | `organization_id_or_slug` | string | ✅ | `"my-organization"` | The unique identifier (ID) or human-readable slug of the Sentry organization from which issues will be removed. | ### `Sentry Create An Alert For An Organization` Integration name: **SENTRY\_CREATE\_AN\_ALERT\_FOR\_AN\_ORGANIZATION** Creates a workflow alert for a Sentry organization using the New Monitors and Alerts system. Use when you need to set up automated alerting for issues based on trigger conditions and filters. Note: This endpoint is currently in beta and may change. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | `"Test Alert from API"` | The name of the alert. | | `config` | object | ✅ | — | Configuration for the alert, typically includes 'frequency' in minutes. Valid frequency values: 0 (0 min), 5 (5 min), 10 (10 min), 30 (30 min), 60 (1 hour), 180 (3 hours), 720 (12 hours), 1440 (24 hours). | | `enabled` | boolean | | — | Whether the alert is enabled or disabled. | | `triggers` | object | ✅ | — | The conditions on which the alert will trigger. Must include 'logicType' (one of 'any-short', 'all', or 'none') and 'conditions' array. Available trigger conditions: 'first\_seen\_event' (new issue created), 'issue\_resolved\_trigger' (issue resolved), 'reappeared\_event' (issue reappears), 'regression\_event' (issue regression). Each condition should have 'type', 'comparison' (true), and 'conditionResult' (true). | | `environment` | string | | `"production"` | The name of the environment for the alert to evaluate in. | | `actionFilters` | array | ✅ | — | The filters to run before the action will fire and the action(s) to fire. Each filter has 'logicType' ('any-short', 'all', or 'none'), 'conditions' array, and 'actions' array. Conditions can filter by: level, age\_comparison, assigned\_to, issue\_category, issue\_occurrences, issue\_priority, event\_frequency, tagged\_event, event\_attribute, latest\_release, and more. Actions define what happens when conditions match: email, slack, discord, msteams, pagerduty, opsgenie, jira, github, vsts notifications, or ticket creation. | | `organization_id_or_slug` | string | ✅ | `"my-organization"` | The ID or slug of the organization the resource belongs to. | ### `Sentry Create Dashboard With Widgets` Integration name: **SENTRY\_CREATE\_DASHBOARD\_WITH\_WIDGETS** Creates a Sentry dashboard with widgets for an organization; `organization_id_or_slug` and specified `project` IDs must be valid, and `start`/`end` datetimes (if absolute range) must form a logical ISO 8601 range. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | `id` | string | | — | Optional client-specified unique dashboard identifier; Sentry generates one if omitted. | | `end` | string | | `"2023-01-31T23:59:59Z"` | Absolute end datetime (ISO 8601) for time range; 'start' must also be set for custom absolute range. | | `utc` | boolean | | — | If true, time range is UTC; otherwise, defaults to user's local time or organization settings. | | `start` | string | | `"2023-01-01T00:00:00Z"` | Absolute start datetime (ISO 8601) for time range; 'end' must also be set for custom absolute range. | | `title` | string | ✅ | `"My Application Overview"` | Title for the new dashboard. | | `period` | string | | `"14d"` | Default relative time range (e.g., '24h', '7d', 'auto'); 'auto' is often 14 days. Overridden if 'start' and 'end' are provided. | | `filters` | object | | — | Additional key-value filters (Sentry search syntax for keys) for the dashboard. | | `widgets` | array | | — | List of widget configurations defining appearance, data queries, and layout. | | `projects` | array | | `"[123, 456]"` | Project IDs to scope dashboard data; if empty/null, may apply to all accessible projects based on org settings. | | `environment` | array | | `"['production', 'dev']"` | Environment names (e.g., 'production') to filter data; if empty/null, all environments included. | | `organization_id_or_slug` | string | ✅ | `"my-org-slug"` | ID or slug of the Sentry organization where the dashboard will be created. | ### `Sentry Create External User For Organization` Integration name: **SENTRY\_CREATE\_EXTERNAL\_USER\_FOR\_ORGANIZATION** Links a Sentry user to an external identity provider's user within a Sentry organization; the Sentry user must be an organization member, an active integration for the provider must be configured, and `external_id` is typically required for the external user. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | integer | ✅ | `734` | The unique numeric identifier for the external actor linkage being created. Its specific use may depend on the integration or Sentry's internal handling. | | `user_id` | integer | ✅ | `101` | The numeric ID of the Sentry user to be linked with the external identity. | | `provider` | string | ✅ | `"github"` | The external identity provider. Allowed values: `github`, `github_enterprise`, `slack`, `gitlab`, `msteams`, `custom_scm`. | | `external_id` | string | | `"U123ABC456"` | The user's unique identifier on the external provider's platform (e.g., GitHub user ID, Slack member ID). This ID is specific to the selected `provider`. | | `external_name` | string | ✅ | `"octocat"` | The display name of the user as known on the external provider's platform (e.g., GitHub username, Slack display name). | | `integration_id` | integer | ✅ | `1` | The numeric ID of the Sentry integration that corresponds to the specified provider and is configured for the organization. | | `organization_id_or_slug` | string | ✅ | `"my-sentry-org"` | The unique identifier (ID or slug) of the Sentry organization where the external user linkage will be created. | ### `Sentry Create Organization Alert Rule` Integration name: **SENTRY\_CREATE\_ORGANIZATION\_ALERT\_RULE** Creates a Sentry metric alert rule for an organization, mandating a 'critical' trigger, typically for a single project, where actions may require Sentry integrations. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | `"High Error Rate Notification"` | The name for the alert rule. Maximum length of 256 characters. | | `owner` | string | | `"team:12345"` | The ID of the Sentry team or user that owns this alert rule. Can be a numeric ID or a string in the format 'team:\' or 'user:\'. | | `query` | string | ✅ | `"http.status_code:500"` | An event search query to filter events for the alert. For example, to include only transactions with status code 400, use `http.status_code:400`. Use an empty string for no filter. | | `dataset` | string | | `"transactions"` | The Sentry dataset this query will execute on. Valid values include `events`, `transactions`, `metrics`, `sessions`, and `generic-metrics`. Defaults to `events` if not specified. Refer to Sentry's \[Metric Alert Rule Types] documentation for valid configurations. | | `projects` | array | ✅ | `["my-project-slug"]` | A list of project slugs to filter by. For metric alerts, this list is typically limited to containing a single project slug. | | `triggers` | array | ✅ | `"[{\"label\": \"critical\", \"alertThreshold\": 50, \"actions\": [{\"type\": \"slack\", \"targetType\": \"specific\", \"targetIdentifier\": \"#get-crit\", \"inputChannelId\": \"2454362\", \"integrationId\": 653532}]}, {\"label\": \"warning\", \"alertThreshold\": 25, \"actions\": []}]"` | List of trigger configurations. Each trigger must specify `label` ('critical' or 'warning'; 'critical' is mandatory), `alertThreshold` (numeric value to trigger), and `actions`. Each action specifies `type` (e.g., 'email', 'slack', 'msteams', 'pagerduty', 'sentry\_app', 'sentry\_notification', 'opsgenie'), `targetType` (must be lowercase, valid values: 'user', 'team', 'specific', 'sentry\_app'), `targetIdentifier` (ID/name, format varies by type e.g., email string, PagerDuty integer). Optional action fields include `inputChannelId` (Slack-specific), `integrationId` (usually required, except for 'email'/'sentry\_app'), `sentryAppId` (if action `type` is 'sentry\_app'), and `priority` (e.g., PagerDuty 'critical', Opsgenie 'P1'). | | `aggregate` | string | ✅ | `"count"` | The aggregate function used in this alert rule. Valid functions include `count`, `count_unique`, `percentage`, `avg`, `apdex`, `failure_rate`, `p50`, `p75`, `p95`, `p99`, `p100`, and `percentile`. Refer to Sentry's \[Metric Alert Rule Types] documentation for valid configurations based on dataset and query type. | | `queryType` | integer | | `"0"` | The type of query. If no value is provided, `queryType` defaults based on the specified `dataset`. Supported values: `0` (Error events: event.type:error), `1` (Transaction events: event.type:transaction), `2` (None: for datasets like metrics that don't use this). See Sentry's \[Metric Alert Rule Types] for valid configurations. | | `eventTypes` | array | | `["error"]` | A list of event types this alert will relate to. Valid values are `default` (for events captured via Capture Message), `error`, and `transaction`. | | `timeWindow` | integer | ✅ | `"60"` | The time period in minutes to aggregate over. Supported values: `1` (1 minute), `5` (5 minutes), `10` (10 minutes), `15` (15 minutes), `30` (30 minutes), `60` (1 hour), `120` (2 hours), `240` (4 hours), `1440` (24 hours). | | `environment` | string | | `"production"` | The name of the environment to filter by. If None or omitted, the alert rule applies to all environments. | | `monitorType` | integer | | `"0"` | Integer representing the monitor type. This determines if the alert rule is actively monitored or monitored based on a specific activation condition. Consult Sentry documentation for specific values and their meanings. | | `thresholdType` | integer | ✅ | `"0"` | The comparison operator for the critical and warning thresholds. `0` for 'Above' and `1` for 'Below'. The resolved threshold uses the opposite operator. For percentage change thresholds, `0` means 'Higher than' and `1` means 'Lower than'. | | `comparisonDelta` | integer | | `"60"` | Optional. The time delta in minutes for the comparison period. Required when using a percentage change threshold (e.g., 'X% higher/lower compared to `comparisonDelta` minutes ago'). Cannot be used for Crash Free Session Rate or Crash Free User Rate alerts. | | `resolveThreshold` | integer | | `"40"` | Optional. The numeric value the metric must reach to resolve an active alert. If not provided, it's automatically set based on the lowest severity trigger's `alertThreshold` and `thresholdType`. For example, if an alert triggers 'Above' 50, it might resolve 'Below' 50. If `thresholdType` is `0` (Above), `resolveThreshold` must typically be less than or equal to the critical threshold; if `thresholdType` is `1` (Below), it must be greater than or equal. | | `activationCondition` | integer | | `"1"` | Optional integer. Represents a trigger condition for when to start monitoring the alert rule, typically used when `monitorType` indicates conditional monitoring. Consult Sentry documentation for specific values. | | `organization_id_or_slug` | string | ✅ | `"my-org-slug"` | The ID or slug of the organization to which this alert rule belongs. | ### `Sentry Create Organization Monitor` Integration name: **SENTRY\_CREATE\_ORGANIZATION\_MONITOR** Creates a new monitor (type 'cron\_job') within a Sentry organization to track scheduled tasks, allowing configuration of its name, slug (which must be unique if provided), status, owner, and muting preferences for incidents. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | ✅ | `"Daily Report Generation"` | The human-readable name for the monitor. This name is used in notifications and the Sentry UI. | | `slug` | string | | `"daily-report-job"` | A unique identifier for the monitor within the organization. If not provided, Sentry will generate one. It must match the pattern `^[a-z][a-z0-9_\-]*$`. Changing this slug after creation requires updating any instrumented check-in calls. | | `owner` | string | | `"user:51234"` | The Sentry actor ID (team or user) to be designated as the owner of this monitor. Format: 'user:{user\_id}' or 'team:{team\_id}'. If not provided, the monitor will be unassigned. | | `config` | object | ✅ | — | The configuration for the monitor including schedule type, schedule, and timing settings. This is a required field. | | `status` | string | | `"active"` | The initial status of the monitor. 'active' monitors accept check-ins and contribute to quotas, while 'disabled' monitors do not. Allowed values: 'active', 'disabled'. Note: Monitors are typically created with 'disabled' status by default and must be activated separately. | | `project` | string | ✅ | `"my-project"` | The project slug to associate the monitor to. This is a required field. | | `is_muted` | boolean | | `true` | A boolean flag to control incident creation for this monitor. If true, monitor incidents (alerts) will be suppressed. Defaults to false if not provided. | | `organization_id_or_slug` | string | ✅ | `"my-org-slug"` | The identifier (ID or slug) of the Sentry organization to which this monitor will belong. | ### `Sentry Create Organization Team` Integration name: **SENTRY\_CREATE\_ORGANIZATION\_TEAM** Creates a new team in a Sentry organization, requiring either a 'slug' or 'name' to define the team. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------ | :------: | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | | — | Optional. The display name for the new team. If not supplied, it's auto-generated from the `slug` (if `slug` is provided). At least one of `name` or `slug` is required to create a team. | | `slug` | string | | `"platform-team"` | Optional. A unique, URL-friendly identifier for the new team. If not supplied, it's auto-generated from the `name` (if `name` is provided). Must adhere to the pattern: `^[a-z][a-z0-9_\-]*$`. | | `organization_id_or_slug` | string | ✅ | — | The unique identifier (ID) or human-readable slug of the Sentry organization where the new team will be created. This organization must already exist. | ### `Sentry Create Project Key With Optional Rate Limiting` Integration name: **SENTRY\_CREATE\_PROJECT\_KEY\_WITH\_OPTIONAL\_RATE\_LIMITING** Creates a new client key (DSN) for an existing Sentry project, with optional custom rate limit configuration. #### Parameters | Parameter | Type | Required | Example | Description | | ------------------------- | ------- | :------: | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | | `"Frontend Key"` | An optional descriptive name for the client key. If not provided, Sentry will generate a default name. | | `rateLimit__count` | integer | | `1000` | The maximum number of events that can be accepted for this key within the specified `rateLimit_window`. If omitted, no custom rate limit will be applied to this key. | | `rateLimit__window` | integer | | `60` | The time window in seconds for the `rateLimit_count`. For example, if `rateLimit_count` is 1000 and `rateLimit_window` is 3600, the key will accept up to 1000 events per hour. If omitted, no custom rate limit will be applied to this key. | | `project_id_or_slug` | string | ✅ | `"my-project-slug"` | The unique identifier (ID) or human-readable slug for the Sentry project for which the client key will be created. | | `organization_id_or_slug` | string | ✅ | `"my-org-slug"` | The unique identifier (ID) or human-readable slug of the Sentry organization to which the project belongs. | *** The remaining tool entries continue in the same format. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.toolhouse.ai/toolhouse/integrations/sentry.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.