Asana DateTime CSV Preflight

What does Asana DateTime CSV Preflight do?

Validate a supplied CSV of task IDs, custom-field IDs and local date-times, then produce a UTC preview with explicit timezone offsets. This data-processing Actor helps operators prepare date-time values for Asana custom fields. It does not connect to Asana, import tasks, update fields or produce executable API requests.

Why check date-times before a migration?

A date-only value, a daylight-saving gap and a repeated local clock time need different handling. This preflight rejects invalid or ambiguous inputs instead of silently choosing a timezone. Exact IDs remain strings, identical duplicates are marked, conflicting duplicates reject the batch, and free-text notes are omitted from results.

This is a preparation step, not a replacement for the native importer or an authenticated migration tool. Asana's community has documented date-time CSV import limitations; check its current capabilities before planning a migration. This Actor cannot establish whether an ID exists, belongs to a project, identifies a writable date field, or has the required permissions and plan. Its UTC output is not a tenant-tested write payload.

How to use the preflight

1. Run Demo to inspect five synthetic rows. The identifiers are invented.
2. Select Check and supply your authorized CSV plus the project GID. Both are required for custom input; sample rows are never mixed into your file.
3. Read the dataset and final RECEIPT. Every result remains executable: false.
4. Verify actual Asana metadata, permissions and current field values in your chosen migration workflow before changing anything.

CSV headers are task_gid,custom_field_gid,local_datetime,timezone, with optional offset,note. Use one custom-field GID per run. A local timestamp must include whole seconds, such as 2026-12-01T12:00:00; timezone must be an IANA name such as Europe/Berlin, or UTC. An optional offset is Z or +/-HH:MM. Repeated daylight-saving times require a matching explicit offset; nonexistent local times are rejected even with an offset. Date-only and fractional-second input are unsupported.

Limits are 1,000 CSV rows, 1,000,000 CSV bytes, 4,096 characters per cell and a 2,000,000-byte total JSON input. Invalid rows reject the entire batch before any result is charged. See the Input tab for the form. No password, API token, proxy or external AI service is needed.

What data does the Actor return?

Field	Meaning
row	Original one-based CSV data-row number
task_gid, custom_field_gid	Supplied exact identifiers, not verified against Asana
proposed_date_time	Normalized UTC instant ending in Z
local_with_offset, timezone	Local value with resolved offset and supplied timezone
status	UTC preview requiring live verification, or identical-input duplicate
executable	Always false
inputKind	Synthetic demonstration or supplied CSV

Download the dataset as JSON, CSV, Excel or other formats supported by Apify. RECEIPT is a JSON object with delivered rows, input-row count and budgetLimited. STATE records completion and acknowledged pushes. An interrupted push may have committed before acknowledgement, so its count is a lower bound, not exact dataset reconciliation. ERROR uses safe error types and row codes without echoing arbitrary exception messages or notes.

How much does it cost?

The result fee is $2 per 1,000 delivered date-time rows ($0.002 per row). Five demonstration rows cost up to $0.01 in result fees. Identical-input duplicate rows are still delivered rows and are charged. Rejected batches produce no result fee; normal platform usage may still apply according to the run's pricing details. A demonstration is not a free trial or a live Asana acceptance test.

API and CLI callers must set maxTotalChargeUsd explicitly for each run. A configured default of $0.01 does not guarantee that every launch method forwards that cap. Inspect the actual run options. This cap governs event charges, not an independent guarantee about every platform cost. Use 128 MB and a short timeout for small files.

When the cap cannot cover the whole file, the Actor stops at the affordable row boundary and writes a BUDGET_LIMITED partial receipt. Dataset and receipt contain only delivered rows; uncharged row contents are not included in reports. Zero budget produces zero rows. Always check deliveredRows, inputRows, budgetLimited and final STATE.completed before treating a run as finished.

FAQ and support

Will this fix or import my Asana CSV?

It validates supported fields and returns UTC previews. It does not change Asana or emit an import-ready native CSV. Do not upload the output as though it were an accepted Asana import template.

Which timezone rules are used?

The release pins the tzdata package to 2026.6. Results follow that database; later timezone-law changes may require an Actor update. A missing timezone is an error, never an implicit UTC fallback.

Can I submit credentials or sensitive notes?

No credentials are needed. Supply only data you are authorized to process, and omit unnecessary personal information. Notes are discarded, but the submitted INPUT is still stored by the platform under its normal run-storage rules. Use the Issues tab for reproducible problems with synthetic examples and the API tab for programmatic access.