Question 1

Does Ana support Attio custom objects?

Accepted Answer

Yes. Attio lets you define arbitrary objects and attributes, and the TextQL connector discovers them automatically. Ana can query any object type you have configured in Attio, filter by any attribute, and join those records with data from your warehouse in the same question.

Question 2

Can I use a scoped API key?

Accepted Answer

Yes, and we recommend it. Create a dedicated Attio API key for TextQL with only the scopes you need. The key is stored encrypted in our credential vault and injected at request time. You can rotate it at any time from the TextQL admin console without changing any Ana prompts.

Question 3

How is the Attio domain whitelisted?

Accepted Answer

An admin adds api.attio.com to the allowlist in the TextQL admin console. Ana's sandbox is blocked from reaching any domain that is not explicitly whitelisted, which eliminates data exfiltration risk and enforces a clear audit boundary around outbound traffic.

Question 4

Does Ana see the API token?

Accepted Answer

No. The token lives in TextQL's credential vault and is injected by our egress proxy at the network layer. Ana's Python code makes requests through a helper that substitutes the token just before the HTTP call leaves the sandbox, so the raw value is never visible.

Question 5

Is Attio data logged?

Accepted Answer

Every API call Ana makes is captured in an audit log with timestamp, endpoint, and the user who initiated the question. Response payloads can optionally be logged for debugging but are redacted by default to protect sensitive CRM data.