skills.rest
NangoHQ
NangoHQOFFICIAL
Explore all skills by this author →
Website𝕏@NangoHQGitHub

migrating-nango-deletion-detection

Migrate Nango syncs from legacy deletion APIs to trackDeletes workflow.

45|32|Updated Sep 23, 2024
Search Tags:#migration#checkpoint#sync#nango#deletion-detection#track-deletes
One-click install
npx skills add https://github.com/NangoHQ/integration-templates --skill migrating-nango-deletion-detection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrating-nango-deletion-detection
Source: https://github.com/NangoHQ/integration-templates/tree/main/.agents/skills/migrating-nango-deletion-detection
Command: npx skills add https://github.com/NangoHQ/integration-templates --skill migrating-nango-deletion-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates Nango syncs from legacy deletion APIs to the trackDeletes workflow. This enables automatic deletion detection across sync executions, including support for checkpoint-based full refresh scenarios.

Core Features & Use Cases

  • Automatic migration of legacy deletion logic to trackDeletesStart/trackDeletesEnd across sync lifecycles.
  • Safe handling for multi-execution refreshes to prevent false deletions.
  • Clear guidance for updating existing createSync code and ensuring proper error handling.

Quick Start

Update your syncs to call trackDeletesStart at the start of exec and trackDeletesEnd after the full dataset has been saved.

Frequently Asked Questions about migrating-nango-deletion-detection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Nango syncs from legacy deletion APIs to trackDeletes?▼

To migrate Nango syncs to trackDeletes, replace the legacy deleteRecordsFromPreviousExecutions API with trackDeletesStart at the beginning of execution and trackDeletesEnd after the full dataset is fetched and saved.

What is Nango trackDeletesStart and trackDeletesEnd used for?▼

Nango trackDeletesStart and trackDeletesEnd are workflow boundaries that enable automatic deletion detection across sync executions. trackDeletesStart initiates tracking, while trackDeletesEnd verifies deletions after the complete dataset is saved.

Why does trackDeletesEnd need to run after the full dataset is saved in Nango?▼

trackDeletesEnd must run after the full dataset is saved to safely complete deletion detection. Running it prematurely during multi-execution refreshes can cause false deletions by comparing against incomplete intermediate data.

Does Nango trackDeletes support checkpoint-based full refresh scenarios?▼

Yes, Nango trackDeletes supports checkpoint-based full refresh scenarios. The migration from legacy deletion APIs ensures automatic deletion detection works correctly across both single and multi-execution checkpoint refreshes.

What happens if I don't migrate from deleteRecordsFromPreviousExecutions in Nango?▼

Failing to migrate from deleteRecordsFromPreviousExecutions prevents your Nango syncs from using the modern trackDeletes workflow, risking unsafe deletion detection during multi-execution refreshes and false positive deletions.

Related Skills

Explore More Software Engineering Skills→
NangoHQNangoHQ
45

migrating-to-checkpoints

Migrate Nango TypeScript createSync implementations to checkpoint-based progress models.

Official
Advanced
NangoHQNangoHQ
45

building-nango-functions-locally

Build and validate Nango Functions locally in a TypeScript project.

Official
Advanced
NangoHQNangoHQ
45

migrating-to-zero-yaml

Migrate legacy nango.yaml projects to Zero YAML TypeScript scaffolding.

Official
Advanced
pypeadaypypeaday
2

drawio

Create and update architecture diagrams via a draw.io MCP server.

Community
Advanced