Skip to main content
Plan requirement: This feature requires an On-call Standard or higher subscription. Learn more
Use an Alibaba Cloud DevOps (云效) AppStack webhook to sync deployment order (ChangeOrder) status updates to Flashduty On-call. Each deployment order becomes one Flashduty change, and its status follows the order from preparing to running to finished. All four order types are recorded: deploy, scale, rollback and destroy.

​
In Flashduty On-call

  1. In the Flashduty console, go to Integration Center → Change Events
  2. Select Alibaba Cloud DevOps AppStack and enter an integration name
  3. To assign changes to specific channels, add rules under the integration’s Routes that match labels such as app or environment
  4. Click Save and copy the generated Push URL

​
Configure AppStack

1

Create a webhook

  • Global webhook (applies to every application in the organization): on the AppStack home page, go to Global Settings → Webhooks and click New Webhook
  • Application webhook (applies to one application): open the application, go to Settings → Webhooks and click New Webhook
2

Enter the URL

Set URL to the full push URL of the Flashduty integration. Leave Secret Token empty: Flashduty authenticates with the integration_key in the push URL and does not check the token.
3

Select trigger events

Under Trigger Events, select Deployment Orders → Status Update. The other events (applications, environments, application orchestration, variable groups, changes, release stages) create no change even when selected, so you can leave them out.
The Test Webhook button sends a mock “new application” event. Flashduty returns success and records no change, so it only confirms that the URL is reachable. To see a change, run a real deployment.

​
What one change is

The top-level id in the request body is the ID of each delivery record, not of the order, and is not used in the identifier.

​
Status mapping

These deliveries return success and create no change:
  • Events other than deployment orders: applications (App), environments (Env), application orchestration (AppOrchestration), variable groups (VariableGroup), changes (ChangeRequest) and release stages (ReleaseStageExecution). A change is a development workflow on a code branch and a release stage is a pipeline run state; neither is a deployment. A deployment started by a pipeline is recorded through its own deployment order
The seven states above are the order states AppStack documents. Any other state returns InvalidParameter with the state value in the message; later updates of that order are not affected.

​
Change content

Labels can be used for routing and for filtering the change list: Environment names are read from the order’s jobs.

​
FAQ

No. A delivery with the same order, state and time is recorded once, and a late earlier state does not reopen an order that has already finished.
  • objectAttributes.sn is required: the order event has no order identifier; check that the delivery comes from an AppStack deployment order event
  • unknown objectAttributes.state: an order state that is not mapped yet appeared; contact us
  • time is required / invalid time: the delivery has no event time or its format is not recognized
Only deployment orders are recorded. Yunxiao pipelines (Flow) and code repositories (Codeup) have their own events, which this integration does not cover. An AppStack deploy step inside a pipeline creates a deployment order, which this integration records.
A suspended order has neither finished nor been withdrawn, so Flashduty keeps it in Processing until it succeeds, fails or is canceled.