1. What product or connector is this request for?

ClickUp Native Connector (Destination: Snowflake / Cloud Data Warehouses)

2. What problem are you trying to solve?

Right now, the native ClickUp connector completely excludes two massive categories of data:

1. Archived Tasks: Any historical or completed task that gets archived in ClickUp is permanently hidden from the sync destination.

2. Custom Task Types: The workspace-wide endpoint used by the native connector silently defaults to standard tasks (custom_items[]=0), filtering out all custom-defined blueprints (like Projects, Components, or Milestones) that organizations use to track specialized data.

This creates severe data integrity blind spots in our data warehouse. Historical data is lost, and hours tracked against historical or custom workflows cannot be audited or visualized in our BI tools.

3. What is the business impact?

Without this feature, we are forced to build, host, and maintain a custom sidecar integration via the Fivetran Connector SDK just to capture basic task properties that the native connector misses. If a task moves from "Active" to "Archived" in ClickUp, it essentially vanishes from our downstream production dashboards, breaking operational performance reports.

4. Technical Feasibility & Proof of Concept

While Fivetran previously noted data integrity limitations with ClickUp's endpoints, we have successfully developed and validated a stable workaround using the Fivetran Connector SDK and ClickUp's v2 API that eliminates these limitations.

The native connector can successfully implement this by updating its data extraction logic to:

• Discover Custom Blueprints First: Call /api/v2/team/{team_id}/custom_item at the start of the sync to map all custom task IDs active in the workspace.

• Bypass the Default Filter: Explicitly append these custom task IDs (along with 0 for standard tasks and 1 for milestones) as an array in the query string (&custom_items[]=0&custom_items[]=1&custom_items[]={custom_id}) when hitting the team task endpoint. This forces the ClickUp API to return all task formats.

• Execute Targeted Archive Sweeps: Loop through both archived=false and archived=true query parameters.

• Utilize Fine-Grained Paging/Time-Chunking: To bypass ClickUp’s undocumented 1,000-record deep pagination ceiling on the workspace endpoint, requests can be chunked into smaller increments using date_updated_gt and date_updated_lt parameters, allowing data to stream reliably line-by-line without causing memory walls or hitting API rate limits.

5. Proposed Solution

We request that Fivetran updates the native ClickUp connector to include these query parameters natively, or provides a configuration toggle in the Fivetran UI setup wizard (e.g., "Include Archived Tasks" and "Include Custom Task Types") to allow users to opt-in to complete workspace data replication.