Question 1

Can Ana read Asana custom fields?

Accepted Answer

Yes. The connector exposes every custom field defined in your Asana projects. Ana can filter tasks by custom fields, aggregate by them, and join them with warehouse data. This is useful when your Asana setup encodes customer IDs, priorities, or feature tags as custom fields.

Question 2

Does Ana support Asana portfolios and goals?

Accepted Answer

Yes. Portfolios, goals, and status updates are all accessible through the Asana API and the TextQL connector surfaces them. Ana can roll up portfolio progress and correlate it with warehouse KPIs in a single question.

Question 3

How are Asana tokens secured?

Accepted Answer

OAuth tokens and PATs are encrypted at rest in TextQL's credential vault and injected into requests by our egress proxy. Ana's Python sandbox never sees the token value, and all token refresh activity is logged outside the sandbox.

Question 4

Which Asana plan is required?

Accepted Answer

Any Asana plan that includes API access works with TextQL. Premium, Business, and Enterprise tiers all support the endpoints the connector uses. Free plan API access is limited and some features such as custom fields require paid plans.

Question 5

Can Ana create Asana tasks?

Accepted Answer

Yes, with write scopes enabled. By default the connector is read-only. Admins can grant write scopes to let Ana create tasks, post comments, or update task status. Write operations are audit-logged separately from read calls.