Rely.io
  • 📌What is Rely.io?
  • 💡How Rely.io works
  • 📑Getting Started Guide
    • Create an account for your organization
    • Add your first plugin
    • Import services into the Service Catalog
    • Make the Software Catalog your own
    • What's Next?
  • 🌈Basic Concepts
    • Entities
    • Blueprints
    • Property Data Types
    • Catalogs
    • Data Model
    • Plugins
    • User Blueprints vs Plugin Blueprints
    • Actions and Automations
      • Automation Rules
      • Self-Service Actions
    • Home Pages
    • Scorecards
  • 📚Guides & Tutorials
    • Enhancing Deployment Visibility through Gitlab Pipelines and Rely's API
  • 🖥️Software Catalog
    • Overview and Use Cases
    • Usage Guide
      • Creating a new Entity
      • Updating an Entity
      • Tracking Entity Changes
      • Customizing an Entity's Page
      • Customizing a Catalog
      • Creating a new Blueprint & Catalog
      • Updating a Blueprint
      • Tracking Blueprint Changes
    • Relevant Guides
    • Troubleshooting
  • 🥇Scorecards
    • Overview and Use Cases
    • Usage Guide
      • Creating a Scorecard
      • Updating a Scorecard
      • Evaluating Performance
    • Scorecard Examples
      • Production Readiness Scorecard Example
      • DORA Metrics Scorecard Example
      • Operational Maturity Example
  • 🎨Home Pages
    • Overview and Use Cases
    • Usage Guide
      • Creating a New Tab
  • ⚡Self-Service Actions
    • Overview and Use Cases
    • Usage Guide
      • Configuring your Self Service Agent
      • Managing your Actions Catalog
      • Self-Service Actions as Code
      • Running Actions
      • Tracking Action Runs
  • ↗️Plugins & Automation
    • What happens when you install a Plugin?
    • Self-Hosting Plugins using Galaxy
    • 🤖Automation Rules
      • Overview and Use Cases
      • Usage Guide
        • Creating an Automation Rule
        • Updating an Automation Rule
        • Tracking Automation Changes
        • Managing Automation Suggestion
    • 🔌Plugin Installation Guides
      • ⭐AWS
      • Bitbucket
      • ⭐Flux
      • GitHub
      • GitLab
      • ⭐Google Cloud Platform (GCP)
      • ⭐Kubernetes
      • ⭐OpsGenie
      • ⭐PagerDuty
      • ⭐Snyk
      • ⭐SonarQube
  • 🌐Public API
    • Audit Logs
    • Automations & Self-Service Actions
    • Automation Suggestions
    • Blueprints
    • Dashboards & Views
    • Entities
    • Scorecards
    • Self-Service Action Runs
    • Time Series
    • Users
    • Webhooks
  • ⚙️Invite Users
  • 🛡️Security & Compliance
    • Single Sign-On (SSO)
      • SAML with Google Workspace
      • SAML with Microsoft Entra ID
      • SAML with Okta
      • OIDC with Okta
      • OIDC with Google Workspace
  • 🏥Troubleshooting
  • ❓FAQ
Powered by GitBook
On this page
  • Automations
  • Self-Service Actions

Was this helpful?

  1. Basic Concepts

Actions and Automations

PreviousUser Blueprints vs Plugin BlueprintsNextAutomation Rules

Last updated 8 months ago

Was this helpful?

Rely.io focuses on automating and simplifying developer workflows through the use of two powerful tools:

  • Automations

  • Self-Service Actions

Automations

Data can be mapped from entities to entities via automation rules.

This mapping creates a dynamic abstraction layer, allowing data from various sources to be filtered, manipulated, standardized, and centralized according to your needs. Automation Rules serve two main purposes:

  1. Unified Entity Representation: Different tools like git providers, incident management tools, and observability platforms represent a "Service" in various ways. Automation rules and user blueprints let you aggregate these diverse perspectives into a single, cohesive "Service" entity. This entity contains only what matters most from each source and reflects your organization's operational context.

  2. Standardizing Cross-Tool Entities: For example, pull requests and merge requests from both GitHub and GitLab can be standardized into a unified format, as can issues from both Jira and Linear. This standardization enables large organizations to maintain uniformity and clarity in their Internal Developer Platform (IDP) across different team processes and toolsets.

Rely.io takes a proactive approach by offering pre-configured automation rules for common use cases, which are automatically included when you install certain plugins.

These default automation rules leverage:

These rules are designed to streamline processes and ensure seamless integration of plugin data with the most common .

Self-Service Actions

🌈
Plugin Blueprint
User Blueprint
The specific data model associated with each plugin
user blueprints
The out-of-the-box data model Rely offers when first creating your organization