Aident logoAident logo centerAident Loadout
Use CasesPricingDocs
ENStart Now
AppsSentry ToolsSentry Create Project Rule For Alerts
Sentry Tools

Sentry Create Project Rule For Alerts

Creates a Sentry project alert rule by defining conditions, actions, and optional filters using specific JSON structures (detailed in parameter descriptions) to automate responses to event patterns for an existing organization and project.

Write actionRisk level 2 of 5API key connection
Use Sentry Create Project Rule For Alerts

Pricing and limits

Aident logo

Product

Aident LoadoutAident Playbook EditorOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • namestring
    Required
    Descriptive name for the alert rule.
  • ownerstring
    Owner ID (e.g., 'team:ID', 'user:ID').
  • actionsarray
    Required
    List of action objects executed when conditions (and filters) are met. Each object must specify an ID (action type) and parameters. See examples for required JSON structures: **Send a notification to Suggested Assignees** - `fallthroughType` - Who the notification should be sent…
  • filtersarray
    Optional list of filter objects for additional criteria after conditions are met. Each object must specify an ID (filter type) and parameters. See examples for required JSON structures: **The issue is `comparison_type` than `value` `time`** - `comparison_type` - One of `older` o…
  • frequencyinteger
    Required
    Action performance interval in minutes (5-43200) once conditions are met.
  • conditionsarray
    Required
    List of condition objects defining rule triggers. Each object must specify an ID (condition type) and parameters. See examples for required JSON structures: **A new issue is created** json { "id": "sentry.rules.conditions.first_seen_event.FirstSeenEventCondition" } **The issue c…
  • actionMatchstring
    Required
    Logic for condition evaluation: 'all' (all conditions must match) or 'any' (any condition can match). NOTE: 'none' is deprecated and no longer supported.
  • environmentstring
    Sentry environment name for event filtering (e.g., 'production'). If omitted, applies to all environments.
  • filterMatchstring
    Logic for filter evaluation ('all', 'any', 'none') for action execution. Required if 'filters' are specified.
  • project_id_or_slugstring
    Required
    Unique identifier (ID or slug) of the Sentry project for the rule.
  • organization_id_or_slugstring
    Required
    Unique identifier (ID or slug) of the Sentry organization.

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.