Autotask DMARC integration
Palisade integrates with Autotask on MSP accounts to import client domains, create DMARC tickets and synchronize recurring-service quantities. Map your Autotask companies to Palisade groups, choose a ticket queue, and connect each client’s billing contract.
Last verified: · Documentation and connector review
By Samuel Chenard, Palisade
Read the Autotask technical setup guideWhat data flows between Palisade and Autotask?
Autotask supplies client and configuration data. Palisade sends task updates and billing quantities through the mappings you configure.
| Data | Direction | What happens |
|---|---|---|
| Companies and contact domains | Autotask → Palisade | Import selected clients, map them to Palisade groups and discover domains from company contact email addresses. |
| Ticket and billing configuration | Autotask → Palisade | Read queues, statuses, priorities, contracts and recurring services for your mappings. |
| DMARC tasks and status updates | Palisade → Autotask | Create tickets in the selected queue and update their mapped status and priority as the Palisade task changes. |
| Contract-service units | Palisade → Autotask | Synchronize the mapped client’s billable domain count to units of the selected recurring service on its contract. |
How does Autotask client import work?
Import the Autotask companies you want to manage and map each one to a group within your Palisade MSP account. Client mapping associates the group’s domains and tickets with the correct Autotask company.
Palisade reads the emailAddress field on company contacts to discover domains. The API user needs permission to view Contacts under CRM. Review the discovered domains before onboarding a client; domains absent from contact addresses may need to be added separately.
Client mappings are managed through Palisade groups. Keep the mapping aligned with the client whose domains your team manages.
How do Autotask tickets and statuses stay connected?
Select the Autotask ticket queue and map task statuses and priorities. Configure issue and sub-issue types to match how your service desk categorizes email-authentication work.
Palisade creates a linked Autotask ticket for a task in a mapped client group and sends subsequent task status and priority updates. Keep the status mapping complete so Pending, Done and other Palisade states reach the intended Autotask workflow state.
Choose which Palisade task types create new Autotask tickets. Disabling a type stops new tickets for that type; existing tickets keep receiving updates. Re-enabling a type does not backfill tasks raised while it was disabled. Read the ticket-control rules.
The DMARC agent investigates issues and prepares fixes. Your technician reviews and approves DNS or policy changes; a PSA ticket is the place to track the work.
How are Autotask recurring-service quantities updated?
Create a recurring service for Palisade in Autotask, select it in the integration settings, and map client groups to their Autotask contracts. Palisade synchronizes billable domain counts to the selected contract service’s units.
A change from five to seven billable domains should result in seven service units for that mapped group. Autotask retains your contract rates and invoice process. Domain import and paid service activation are separate steps, so an audit inventory should not be treated as the billing quantity.
Verify both the contract mapping and the recurring service when a quantity does not update. Billing can be paused while task synchronization continues.
Which Palisade plans support Autotask?
The Autotask connector requires a Palisade MSP account. MSPs pay per client domain, with a rate that improves as your portfolio grows. Your own MSP domain is included as a free Not-For-Resale license.
Standard Free and IT-team accounts need MSP enrollment to use PSA integrations. Explore the MSP program or see how MSP pricing works.
What is required to set up Autotask?
Use a Autotask API identity with access to the clients and workflow you want to connect. Keep credentials in your team’s credential manager and enter them only in the integration’s credential form.
| Area | Required access |
|---|---|
| API user | Create an API User under Admin > Resources with the API-only security level. Generate its key and secret and select the Palisade integration tracking identifier. |
| CRM | Read companies and view Contacts so Palisade can discover domains from client contact emails. |
| Ticket workflow | Access the queue and ticket configuration; allow the connector to create and update tickets. |
| Contract billing | Read the mapped contracts and recurring service and allow updates to its contract-service units. |
1. Create the Autotask API user
In Admin > Resources, create an API User with the API-only security level. Generate and store its key and secret, and choose Palisade as the tracking identifier.
2. Activate Palisade Email
Open Admin > Extensions & Integrations > Integration Center in Autotask. Find Palisade Email and activate the integration.
3. Connect and map the client workflow
Select Autotask in Palisade Integrations and enter the API user credentials in the form’s Username and Password fields. Set the queue, statuses, priorities and issue types, then import and map your clients.
4. Map recurring-service billing
Create and select the Palisade recurring service, then map each client to its contract. Verify a client-domain import, a ticket update and a billable-domain unit change before rollout.
Follow the Autotask technical setup guide for the credential fields and configuration sequence.
What should you verify before rolling out to clients?
Start with a test client in Autotask and confirm the mapping, ticket and billing results your team will rely on.
- The Autotask API user can read the selected company’s contacts, and its expected domains appear under the correct Palisade group.
- A Palisade task reaches the chosen Autotask queue and company; a Palisade status change updates the linked ticket.
- The selected recurring service belongs to the mapped contract, and its units match the group’s billable domains.
Autotask integration FAQ
Does Palisade have an official Autotask integration listing?
Yes. Datto publishes a Palisade listing in its official integration directory. Palisade also provides an Autotask setup guide covering API-user creation, activation, ticket mapping and recurring-service billing.
What does two-way Autotask synchronization mean?
Palisade reads Autotask client and configuration data for import and mapping, then sends DMARC tickets, mapped task updates and billing quantities back to Autotask. The direction depends on the data type; it does not mean every field is mirrored both ways.
Which Palisade plan includes the Autotask connector?
The Autotask connector requires a Palisade MSP account. The MSP program uses per-client-domain pricing and includes your own MSP domain as a free Not-For-Resale license.
Why does an Autotask client import without its domains?
Autotask domain discovery uses the client’s contact email addresses. Check that the API user can view Contacts under CRM and that the client has the expected email addresses. Review the Palisade group mapping and add any missing domain separately.
Documentation and related integrations
Autotask technical documentation
Palisade in the official Datto integration directory. Datto lists Palisade as an Autotask integration and describes the connection between client onboarding, ticketing and billing.