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

> ## Agent Instructions
> Cognite Data Fusion (CDF) is an industrial DataOps platform. English is the canonical locale unless the reader asks for another.
> The documentation catalog is https://docs.cognite.com/llms.txt. Subgroup indexes live under https://docs.cognite.com/_llms/. Each published page has a Markdown twin at the same path with a .md suffix.
> REST APIs: calendar version 20230101 is stable. Preview versions are 20230101-beta and 20230101-alpha, for clients already on a preview API. Concept pages are under /api-reference/concepts/<version>/. Versioned requests use the Cdf-Version header. The default SDK is the Python SDK (cognite-sdk). JavaScript and TypeScript projects use the JavaScript SDK.
> Topic hubs: platform overview /cdf/index.md; data modeling /cdf/dm/index.md; data integration /cdf/integration/index.md; access /cdf/access/index.md; Cognite Toolkit /cdf/deploy/cdf_toolkit/index.md; REST quickstart /dev/quickstart.md; Python SDK /dev/sdks/python/index.md; Atlas AI /cdf/atlas_ai/concepts/index.md; Flows apps /cdf/flows/index.md; Aura UI /cdf/aura/index.md; MCP and IDE setup /dev/guides/ide_ai_integration.md.

# Actions

> Trigger and manage remote actions on an integration in Cognite Data Fusion (CDF).

Actions let you trigger remote operations on an integration, such as asking an extractor to restart or reload its configuration. CDF tracks each action's status as the extractor picks it up and completes it. You can create actions, list or retrieve their status, and cancel pending ones.

An action is a request for an integration to do something outside its normal task loop. The extractor receives pending actions in its next check-in response, runs them, and reports the outcome to CDF. This lets you manage extractors remotely without network access to the host where they run.

## Triggering and tracking actions

You create an action against a specific integration, then poll or retrieve it to see whether it is pending, running, completed, or failed. If an action is no longer needed, you can cancel it before the extractor picks it up.

<Note>
  You can cancel an action only while it is pending, running, or cancel-pending. After the extractor reports completion, the outcome is final.
</Note>

## Key operations

* **Create**: Request a remote action on an integration.
* **List and retrieve**: Check the status of actions by integration or by ID.
* **Cancel**: Stop a pending or running action before it completes.

Actions give you remote control over an extractor's behavior, complementing the passive monitoring that task history and error listing provide.