SENTRY.IO n8n INTEGRATION: AUTOMATE SENTRY.IO WITH N8N

This action allows you to modify an existing team within your Sentry.io organization. It's particularly useful when team structures change, when you need to update team metadata, or when automating team management as part of employee onboarding/offboarding workflows.

Key parameters: Credential to connect with (required dropdown to select your configured Sentry.io account for authentication), Organization Slug Name or ID (required text field to identify the Sentry.io organization containing the team), Team Slug Name or ID (required text field to specify which team to update), Update Fields (optional section where you can dynamically add specific properties to modify).

Use cases: Renaming teams during company restructuring, updating team properties when integrating with HR systems, or batch-updating team metadata as part of compliance workflows.

This action retrieves multiple teams from a specified Sentry.io organization. It's essential for building dashboards, generating reports, or creating workflows that need to iterate over all teams in your organization.

Key parameters: Credential to connect with (required dropdown for selecting your Sentry.io authentication credentials), Organization Slug Name or ID (required text field to specify from which organization to fetch teams), Return All (optional toggle that retrieves all available teams regardless of the limit setting), Limit (optional number field, default: 100, specifying the maximum number of teams to return).

Use cases: Building a team directory sync with your internal tools, auditing team configurations across your organization, or feeding team data into reporting dashboards.

This action retrieves detailed information about a specific team within your Sentry.io organization. Use it when you need to fetch team details for conditional logic in your workflows or to display team information in other systems.

Key parameters: Credential to connect with (required dropdown to select your Sentry.io account credentials), Organization Slug Name or ID (required text field for the organization identifier), Team Slug Name or ID (required text field to specify exactly which team's details to retrieve).

Use cases: Verifying team existence before assigning projects, fetching team details to populate forms in other applications, or checking team configurations as part of audit workflows.

This action permanently removes a team from your Sentry.io organization. It's a critical action for cleanup workflows, automated offboarding processes, or reorganization scenarios where teams are being consolidated.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Organization Slug Name or ID (required text field identifying the organization), Team Slug Name or ID (required text field specifying which team to delete).

Use cases: Automating team cleanup when departments are restructured, removing test teams after QA processes, or implementing automated offboarding that includes Sentry.io cleanup.

This action creates a new team within a specified Sentry.io organization. It's fundamental for automating team provisioning, whether for new departments, client projects, or development squads.

Key parameters: Credential to connect with (required dropdown for authentication), Organization Slug Name or ID (required text field for the target organization), Name (required text field where you define the name for the new team), Additional Fields (optional section for adding extra properties to the team configuration).

Use cases: Automatically creating teams when new departments are added in your HR system, provisioning client-specific teams when new contracts are signed, or setting up teams as part of project kickoff automation.

This action modifies an existing release in Sentry.io. It's essential for keeping release metadata synchronized across your development pipeline, especially when release information needs to be updated post-deployment.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Organization Slug Name or ID (required text field for the organization), Version (required text field specifying the exact version string of the release to update), Update Fields (optional section where you can add specific properties to modify).

Use cases: Updating release status after deployment verification, adding deployment metadata from CI/CD pipelines, or synchronizing release notes from your documentation system.

This action retrieves multiple releases from your Sentry.io organization. It's perfect for building release dashboards, generating deployment reports, or creating workflows that analyze release patterns.

Key parameters: Credential to connect with (required dropdown for authentication), Organization Slug Name or ID (required text field for the target organization), Return All (optional toggle to fetch all releases regardless of limit), Limit (optional number field, default: 100, for maximum releases to return), Additional Fields (optional section for adding filters or specific query parameters).

Use cases: Building release history dashboards, generating deployment frequency reports, or auditing release patterns across projects.

This action retrieves detailed information about a specific release from Sentry.io. Use it when you need to verify release status, fetch release metadata for other systems, or implement conditional logic based on release information.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Organization Slug Name or ID (required text field for the organization), Version (required or optional text field specifying the release version to retrieve).

Use cases: Verifying release existence before deployment, fetching release details for changelog generation, or checking release status in deployment workflows.

This action permanently removes a release from Sentry.io. It's useful for cleanup operations, removing test releases, or implementing retention policies for release data.

Key parameters: Credential to connect with (required dropdown for authentication), Organization Slug Name or ID (required text field identifying the organization), Version (required text field specifying the exact version to delete).

Use cases: Cleaning up test releases after QA cycles, implementing automated retention policies, or removing incorrect releases that were created in error.

This action creates a new release in Sentry.io. It's a cornerstone action for CI/CD integration, automatically tracking deployments and associating them with the correct projects.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Organization Slug Name or ID (required text field for the target organization), Version (required text field for the unique version identifier), Project Names or IDs (required text field listing the projects to associate with this release), URL (optional text field for linking to release notes or deployment documentation), Additional Fields (optional section for extra release properties).

Use cases: Automatically creating releases from GitHub Actions or GitLab CI, tracking deployments across multiple projects simultaneously, or linking releases to external documentation systems.

This action modifies an existing Sentry.io project's configuration. It's valuable for maintaining project settings, updating project metadata, or automating project management tasks.

Key parameters: Credential to connect with (required dropdown for authentication), Organization Slug Name or ID (required text field for the organization), Project Slug Name or ID (required text field identifying the project to update), Update Fields (optional section where you can add specific properties to modify).

Use cases: Updating project configurations when requirements change, synchronizing project metadata with external systems, or batch-updating project settings across your organization.

This action retrieves multiple projects from your Sentry.io account. It's essential for building project inventories, generating cross-project reports, or creating workflows that need to operate on multiple projects.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Return All (optional toggle to fetch all projects regardless of limit), Limit (optional number field, default: 100, for maximum projects to return).

Use cases: Building a project directory for internal documentation, auditing project configurations, or feeding project data into resource management tools.

This action retrieves detailed information about a specific Sentry.io project. Use it for fetching project configurations, verifying project existence, or building conditional workflows based on project properties.

Key parameters: Credential to connect with (required dropdown for authentication), Organization Slug Name or ID (required text field for the organization), Project Slug Name or ID (required text field specifying which project to retrieve).

Use cases: Verifying project existence before creating releases, fetching project DSN for configuration purposes, or checking project settings in audit workflows.

This action permanently removes a project from Sentry.io. It's critical for cleanup operations, automated decommissioning workflows, or removing test projects after development cycles.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Organization Slug Name or ID (required text field for the organization), Project Slug Name or ID (required text field specifying the project to delete).

Use cases: Automating project cleanup when applications are decommissioned, removing test projects after QA cycles, or implementing project lifecycle management.

This action creates a new project within a Sentry.io organization and assigns it to a specific team. It's fundamental for automating project provisioning in development workflows.

Key parameters: Credential to connect with (required dropdown for authentication), Organization Slug Name or ID (required text field for the target organization), Team Slug Name or ID (required text field specifying which team will own the project), Name (required text field for the project name), Additional Fields (optional section for extra project properties).

Use cases: Automatically creating projects when new repositories are added, provisioning client-specific projects when contracts begin, or setting up projects as part of development kickoff automation.

This action modifies an existing Sentry.io organization's settings. It's useful for maintaining organization configurations, updating metadata, or implementing organization-wide policy changes.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Slug Name or ID (required text field identifying the organization to update), Update Fields (optional section where you can add specific organization properties to modify).

Use cases: Updating organization settings when policies change, synchronizing organization metadata with corporate directories, or implementing compliance-related configuration updates.

This action retrieves multiple organizations accessible to your Sentry.io account. It's useful for multi-organization setups, building organization directories, or creating workflows that span multiple organizations.

Key parameters: Credential to connect with (required dropdown for authentication), Return All (optional toggle to fetch all organizations regardless of limit), Limit (optional number field, default: 100, for maximum organizations to return), Additional Fields (optional section for filtering or query parameters).

Use cases: Building multi-organization dashboards, auditing organization configurations, or creating cross-organization reporting workflows.

This action retrieves detailed information about a specific Sentry.io organization. Use it for fetching organization settings, verifying configurations, or building workflows that need organization-level data.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Organization Slug Name or ID (required text field specifying which organization to retrieve).

Use cases: Fetching organization details for compliance reporting, verifying organization settings before making changes, or displaying organization information in dashboards.

This action creates a new Sentry.io organization. It's essential for scaling setups, white-label solutions, or automated provisioning scenarios where new organizations need to be created programmatically.

Key parameters: Credential to connect with (required dropdown for authentication), Name (required text field for the new organization's name), Agree to Terms (optional toggle to accept Sentry.io's terms of service), Additional Fields (optional section for extra organization properties).

Use cases: Provisioning organizations for new enterprise clients, setting up white-label Sentry.io instances, or automating multi-tenant environment creation.

This action modifies an existing Sentry.io issue. It's crucial for automated issue management, triage workflows, or synchronizing issue status with external systems like HubSpot or other CRM tools.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Issue ID (required text field specifying the unique identifier of the issue to update), Update Fields (optional section where you can add specific issue properties to modify such as status, assignee, priority).

Use cases: Automatically resolving issues when deployments are verified, updating issue priority based on external signals, or syncing issue status with project management tools.

This action retrieves multiple issues from a specified Sentry.io project. It's essential for building issue dashboards, generating error reports, or creating workflows that process issues in bulk.

Key parameters: Credential to connect with (required dropdown for authentication), Organization Slug Name or ID (required text field for the organization), Project Slug Name or ID (required text field for the target project), Return All (optional toggle to fetch all issues regardless of limit), Limit (optional number field, default: 100, for maximum issues to return), Additional Fields (optional section for filtering or query parameters).

Use cases: Building error dashboards in external tools, generating weekly issue reports, or creating triage workflows that process new issues automatically.

This action retrieves detailed information about a specific Sentry.io issue. Use it for fetching issue details, building conditional workflows, or displaying issue information in other systems.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Issue ID (required text field specifying the unique identifier of the issue to retrieve).

Use cases: Fetching issue details for incident reports, verifying issue status before taking action, or pulling issue data for display in custom dashboards.

This action permanently removes an issue from Sentry.io. Use it for cleanup operations, removing test issues, or implementing automated issue management policies.

Key parameters: Credential to connect with (required dropdown for authentication), Issue ID (required text field specifying the issue to delete).

Use cases: Cleaning up test issues after QA processes, implementing automated issue retention policies, or removing issues that were created in error.

This action retrieves multiple events from a specified Sentry.io project. It's fundamental for event analysis, building custom dashboards, or creating workflows that process error events in bulk.

Key parameters: Credential to connect with (required dropdown for Sentry.io authentication), Organization Slug Name or ID (required text field for the organization), Project Slug Name or ID (required text field for the target project), Full (optional toggle that retrieves full event details when enabled), Return All (optional toggle to fetch all events regardless of limit), Limit (optional number field, default: 100, for maximum events to return).

Use cases: Building real-time error monitoring dashboards, generating detailed event reports, or analyzing error patterns across your applications.

This action retrieves detailed information about a specific Sentry.io event. Use it when you need comprehensive event data for debugging, incident reports, or detailed error analysis.

Key parameters: Credential to connect with (required dropdown for authentication), Organization Slug Name or ID (required text field for the organization), Project Slug Name or ID (required text field for the project), Event ID (required text field specifying the unique identifier of the event to retrieve).

Use cases: Fetching detailed event data for incident reports, pulling event context for automated debugging workflows, or displaying event information in custom error tracking dashboards.