n8n Departure Handover Checklist: Google Calendar + Asana

Make departure handovers painless: auto-build an n8n checklist from Google Calendar + Asana

This n8n workflow gathers a departing employee’s details, scans Google Calendar and Asana for any upcoming commitments after their last working day, and publishes a ready-to-use Notion checklist—then shares the results in Slack with a link to the page.

What this workflow does

• Collects input via an n8n form (leaver’s email, last working day, and optional Asana user GID).
• Checks Google Calendar: expands a configured comma-separated list of Google Calendar IDs and queries each calendar for events after the last working day that match the leaver.
• Filters for accuracy: keeps only exact attendee/organizer email matches, and labels items as either needing a new owner or likely cancellation.
• Checks Asana: resolves the leaver’s Asana user (by email or the provided GID) and fetches their open tasks in the configured Asana workspace.
• Targets only future work: keeps tasks due after the last working day (or with no due date) and categorizes them into “needs a new owner” vs “cancel candidates.”
• Creates a Notion page and appends checklist blocks in batches of 100 for a clean, scalable output.
• Notifies Slack with counts and the Notion manifest link—or posts a “clean sweep” notice when no matching commitments are found.

Use cases

• HR or Ops automates offboarding so managers immediately see which meetings and tasks must be reassigned.
• Automation engineers standardize a consistent departure handover process across teams.
• SaaS operators reduce risk of “orphaned” ownership after employee departures by proactively finding upcoming commitments.

Technical details

Built for n8n with these nodes/tech stack: if, set, code, Asana, merge, and Slack. Requires credentials for Google Calendar OAuth2, Asana (PAT), Notion, and Slack.