> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashduty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Actions

> Learn about custom action use cases and configuration methods

## Use Cases

Custom actions are essentially Webhook calls. You can add custom actions for incidents in different channels and manually trigger them in incident details to achieve quick troubleshooting or information sync.

<CardGroup cols={2}>
  <Card title="Restart Host" icon="rotate">
    When host memory or CPU is maxed out, trigger host restart script for quick restart
  </Card>

  <Card title="Information Enrichment" icon="layer-plus">
    When incidents occur, callback your service to retrieve Tracing, Logging, topology info based on alert details, and actively call Flashduty Open API to update incident information
  </Card>

  <Card title="Rollback Changes" icon="rotate-left">
    When incidents occur, if confirmed to be caused by changes, directly trigger callback to your deployment platform to start rollback process
  </Card>

  <Card title="Update Status Page" icon="globe">
    When confirmed that incidents affect production services, trigger external Status Page update to promptly notify your customers or partners
  </Card>
</CardGroup>

## Configure Custom Actions

<Steps>
  <Step title="Enter Integration Center">
    Login to console, go to **Integration Center => Webhook**.
  </Step>

  <Step title="Add Integration">
    Click to add **Custom Actions** integration.
  </Step>

  <Step title="Configure Information">
    Configure the following:

    | Field          | Description                                                                 |
    | :------------- | :-------------------------------------------------------------------------- |
    | Action Name    | This name appears as a button in incident details                           |
    | Channels       | Can configure multiple, but each channel allows at most five custom actions |
    | Endpoint       | HTTP(s) address triggered when clicking custom action button                |
    | Custom Headers | Custom headers included when requesting the Endpoint                        |
  </Step>

  <Step title="Save">
    Save to complete configuration.
  </Step>
</Steps>

After creation, you can see the action button under \[Incident Details - More Actions] in the corresponding channel. Click the button and system shows operation result. If successful, system writes an operation record.

## Related Topics

<CardGroup cols={2}>
  <Card title="Webhook Basics" icon="webhook" href="/en/on-call/integration/webhooks/incident-webhook">
    Learn how to implement Webhook interfaces
  </Card>

  <Card title="Custom Actions Integration" icon="code" href="/en/on-call/integration/webhooks/custom-actions">
    View detailed custom action Webhook configuration
  </Card>
</CardGroup>