Question 1

Does Polytomic sync Asana incrementally?

Accepted Answer

No, and this is the most important thing to know before you schedule it. Every execution performs a full paginated scan of the selected objects. Asana exposes a modified timestamp on some objects, but it is not used as an incremental cursor and there is no webhook based capture in the connector, so each ETL run re-reads the data rather than fetching a delta. Practically, that means picking a schedule that matches how fresh you need the data rather than running it every few minutes, and scoping the connection to the projects you actually report on.

Question 2

Can I sync only certain Asana projects?

Accepted Answer

Yes, and it is worth doing given that reads are full scans. Selecting projects on the connection scopes projects, tasks, sections, stories, and project status updates to just those projects, which can cut sync time dramatically in a large workspace. Note that the selection does not scope workspace level objects, portfolios, goals, or their status updates; those are still read across everything the authorizing user can see.

Question 3

How are Asana custom fields handled?

Accepted Answer

Tasks, projects, and portfolios expose custom fields as a generic array, and projects and portfolios additionally expose their custom field settings. The values arrive as nested Asana payloads rather than being expanded into individually typed columns, and there is no separate custom field definition table. So a custom field called Priority does not become its own column automatically; you extract it from the nested structure in your data warehouse, which is straightforward once but worth planning for in your models.

Question 4

Can I get the change history behind a task?

Accepted Answer

Yes, through stories. Stories are Asana's record of comments and field changes on a task, and syncing them lets you reconstruct when something moved stage, who commented, and how long it sat. Worth knowing that stories are fetched per task, so Polytomic lists a project's tasks and then requests stories for each one. That fan out makes stories one of the more API intensive objects, which is another reason to scope the connection to the projects you actually need.

Question 5

Can Polytomic write data back into Asana?

Accepted Answer

Not currently. Asana is a source only connector, so Polytomic runs ETL out of Asana into your data warehouse, databases, and SaaS tools, but does not create or update Asana tasks. If your goal is getting delivery data somewhere it can be joined and reported on, that direction is the one that matters. For reverse ETL into operational tools, the same platform writes to Salesforce, HubSpot, and many other destinations from the models you build on that data.

Asana

Perfect pairings

Beyond tasks and projects

Scope by project

Task activity history

Example workflows

What you can sync

From Asana

To your destinations

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Asana in minutes

More integrations beyond Asana