Automatically Starting Autopilot on All Incoming Requests

If you'd rather not assign Autopilot to each request individually, you can turn on an automation that does it for you. Once active, every new privacy request — across all rights — is automatically assigned to Autopilot the moment it comes in. See Autopilot Overview for how Autopilot processes a request once it's assigned.

Setting up the automation

Go to Settings > Automations > Marketplace.
Find Start Autopilot On New DSR Requests and select it.
Click Configure (or Reconfigure if it's already been set up before).

[📷 Screenshot: Marketplace tab showing the "Start Autopilot On New DSR Requests" tile — insert here]

Review the setup details, including the webhook ID the automation will use to listen for new requests. In most cases you can leave this as-is.
Read the confirmation note carefully before finishing: the automation will invoke every automated integration (API or email-based) in each ticket's workflow, and it won't run on workflows that include manual integrations.
Click Finish.

Once it's active, a green indicator appears on the automation's tile in the Marketplace, confirming it's running.

What the automation does

This automation listens for new incoming requests and triggers Autopilot on each one as it arrives, across all privacy rights — you don't need to configure it separately per right. It also manages its own subscription to your request notifications automatically, so there's no separate webhook setup required on your end.

Any ticket that doesn't meet Autopilot's eligibility requirements — for example, one whose workflow includes a manual task — is skipped by the automation and stays in your queue for manual handling, just as it would if you tried to assign Autopilot to it directly.

Turning it off

You can deactivate the automation from the same Marketplace tile at any time. Doing so stops new requests from being automatically assigned to Autopilot going forward; it doesn't affect requests that are already running on Autopilot.