PowerDMARC Now Integrates with Autotask

PowerDMARC now connects natively with Autotask, the Datto/Kaseya PSA platform. MSSPs can link their Autotask instance to PowerDMARC in minutes, mapping customers, syncing billable domain counts to Contract Services in real time, and routing DMARC alerts straight into their service desk as tickets.

The integration joins the growing list of PowerDMARC integrations built specifically for partner workflows.

What Is Autotask?

Autotask is Kaseya’s professional services automation platform, widely used by MSPs and MSSPs to run ticketing, contracts, billing, and client management from one system. If you’re already standardized on Autotask, this integration is built to slot into the workflows your team runs there instead of asking them to learn a new tool.

What the PowerDMARC-Autotask Integration Does

The integration covers three areas: customer mapping, billing sync, and alert-to-ticket automation. Here’s what you can expect from it.

Secure connection

You connect using your own Autotask API User credentials, generated inside your Autotask account. Access stays scoped to your instance, and PowerDMARC automatically detects your Autotask zone during setup, so there’s no webserver URL to look up.

Customer mapping

Link each PowerDMARC account to its corresponding Autotask Company. Once mapped, the platforms stay aligned, so your customer lists don’t drift apart across the two systems.

Billing sync

PowerDMARC tracks active billable domains for every mapped customer and updates the linked Autotask Contract Service automatically.

For partners managing dozens or hundreds of customers, this removes the month-end routine of pulling domain counts from PowerDMARC, comparing them against the last cycle, and adjusting Contract Services one by one. Autotask logs every change as a Contract Service Adjustment, so there’s a full audit trail without anyone touching a spreadsheet.

Billing sync is optional. If you’d rather use the integration only for alert-to-ticket automation, you can turn it off during setup and skip the Contracts and Services mapping entirely.

Alert-to-ticket

Choose which DMARC alert types should create tickets in Autotask, including DNS record changes, failure-volume threshold breaches, and forensic reports. When a mapped alert fires, a ticket lands in the queue you’ve configured, with the alert details attached and ready for your team to act on.

This matters because DMARC alerts sitting in a shared inbox tend to get triaged late or missed during busy periods. Routing them into the queue your analysts already work from means SLAs apply, and nothing sits unread.

How to Set Up the PowerDMARC-Autotask Integration

Setup happens in two parts: a one-time configuration inside Autotask to create an API User, followed by a three-step wizard inside PowerDMARC.

Step 1: Prepare your Autotask account

Before connecting to PowerDMARC, create a dedicated API User in Autotask under Admin → Resources (Users) → New API User, with the Security Level set to API User (system). This user doesn’t consume a paid resource license. On the Security tab, assign a Tracking Identifier (select PowerDMARC from the Vendor list if it’s available, or choose Custom).

Copy the three values you’ll need for PowerDMARC:

• Username, the API User’s email address
• Secret, the API password (shown only once, so store it securely)
• API Integration Code, the Tracking Identifier

If you plan to use billing sync, make sure each customer you want to map already has an active Contract with at least one Service attached in Autotask. PowerDMARC will use these to track billable domain counts, and will flag any Company that’s missing one during mapping.

Step 2: Connect Autotask to PowerDMARC

In PowerDMARC, go to Integrations → Autotask and click Connect to Autotask to launch the wizard.

On Step 1: Connection, enter your Username, Secret, and API Integration Code, then click Connect & Continue. PowerDMARC verifies your credentials and detects your Autotask zone automatically.

Step 3: Map customers and enable billing sync

On Step 2: Customer Mapping, decide whether PowerDMARC should manage billing in Autotask. With billing sync on, map each PowerDMARC account to its Autotask Company, Contract, and Service.

With it off, you only need to map the Company, and PowerDMARC handles ticket automation without touching domain counts.

Step 4: Map alerts to tickets

On Step 3: Alert-to-Ticket Mapping, choose which DMARC alert types should create tickets for each customer, along with the Ticket Category, Queue, and (optionally) Location and End User. Tickets are only created when a live alert fires, not when this step is completed.

Click Submit to Autotask to finish. You can update any of these configurations later from Integrations → Autotask.

For step-by-step instructions with screenshots, refer to the full Autotask setup guide.

Who Can Use It?

The Autotask integration is available to MSSP accounts that have the Autotask Integration toggle enabled in account settings. Users also need the Access Autotask Integration permission on their role, granted by default to MSSP Owner and MSSP Admin roles and extendable to custom roles.

It’s a fit for any partner already running Autotask as their PSA, whether you’re delivering DMARC as a standalone managed service or as part of a broader security practice.

If you’re an MSP or MSSP using Autotask and the toggle isn’t yet enabled on your account, reach out to your PowerDMARC account manager. Not yet a partner? Learn more about the PowerDMARC MSP and MSSP program.

Get Started

If you’re already on Autotask, you can connect it to PowerDMARC and stop reconciling domains by hand from the next billing cycle. Start a free trial or contact our team to enable the integration on your account.