Skip to main content
Five independent settings determine whether the action deletes past or future entries and pending or completed entries.
This action permanently deletes calendar scheduled entries and cannot be undone. Test it first.
This action supports ConnectWise and Autotask. In Autotask it removes the ticket’s service calls, which also clears the technicians attached to them. Delete resource entries is ConnectWise only, because Autotask has no technician assignment that exists without a service call.

Quick Start

1

Choose your trigger

Use Ticket Update when status changes to “Resolved” or “Cancelled”
2

Filter carefully

Use ticket filters to target only tickets that need schedule cleanup
3

Configure deletion scope

Choose which types of entries to delete using the five configuration options
4

Test first

Test on a few non-critical tickets before running on important data

Configuration options

You can choose which schedule entries to delete with five independent settings: In Autotask, the four past/future settings apply to the ticket’s service calls. Removing a service call also removes every technician attached to it, so a call shared by two technicians disappears once. A service call that is booked on more than one ticket is kept, not deleted, because removing it would take the visit off the other tickets too; the run reports it as kept. Cancelled service calls are ignored.

Default Behavior

By default, the action deletes all pending (not completed) calendar entries: both past and future. It preserves completed work history.

Resource Entries (ConnectWise Only)

In ConnectWise, you can add resources to a ticket without scheduling a specific time slot. These “resource entries” appear in the Schedule section but don’t have calendar dates. Enable the Delete resource entries option to remove not completed resource assignments from the ticket.

Full Cleanup Mode

Enable all five options to remove every schedule entry from the ticket, including resource assignments. Use this when completely closing out cancelled tickets.

Ticket Selection

The action processes tickets based on your workflow trigger and any filters you’ve configured. Use precise filters to avoid affecting the wrong tickets.

What you’ll get

After the action runs, you’ll see:
  • Executions: Confirmation of which scheduled entries were deleted
  • Clean Calendar: Removed appointments no longer appear in technician calendars
  • Updated Tickets: Tickets no longer have the deleted scheduled work attached

Example workflows

  1. Trigger: Ticket status changes to “Resolved”
  2. Filter: Only tickets with scheduled work
  3. Delete Schedule Entries: Use default settings to remove pending scheduled work
  4. Result: Resolved tickets no longer have pending appointments, but completed work history is preserved
  1. Trigger: Ticket status changes to “Cancelled”
  2. Filter: Tickets tagged with “Project” or “Maintenance”
  3. Delete Schedule Entries: Enable all five deletion options
  4. Result: Cancelled tickets are completely cleaned up with no schedule entries or resource assignments remaining
  1. Trigger: Scheduled workflow runs weekly
  2. Filter: Tickets older than 30 days with status “Closed”
  3. Delete Schedule Entries: Enable only “Delete past pending entries”
  4. Result: Old closed tickets no longer have incomplete past appointments cluttering calendars
  1. Trigger: Ticket status changes to “Resolved”
  2. Filter: ConnectWise tickets only
  3. Delete Schedule Entries: Enable “Delete resource entries” along with default pending entries
  4. Result: Resolved tickets have both scheduled appointments and unscheduled resource assignments removed