Question 1

Does Ana support Pipedrive custom fields?

Accepted Answer

Yes. The connector reads your Pipedrive schema at query time so Ana can reference any custom field on deals, persons, or organizations. You can ask Ana to filter, group, and join on custom fields just as easily as on native properties.

Question 2

Which Pipedrive plan is required?

Accepted Answer

Any Pipedrive plan that provides API access works with TextQL. Advanced, Professional, Power, and Enterprise tiers all include the API endpoints the connector needs. Essential plan users should confirm API availability in their Pipedrive admin settings before configuring the connector.

Question 3

How are Pipedrive credentials stored?

Accepted Answer

OAuth tokens and API keys are encrypted at rest in TextQL's credential vault. When Ana makes a request, credentials are injected by an egress proxy at the network layer, so Ana's Python sandbox never has access to the raw values.

Question 4

Can I whitelist a specific Pipedrive subdomain?

Accepted Answer

Yes. Pipedrive API endpoints are served under your company subdomain as well as api.pipedrive.com. An admin can whitelist either or both in the TextQL admin console to precisely control which hosts Ana may contact from the sandbox.

Question 5

Is Pipedrive data audited?

Accepted Answer

Every API call Ana makes is logged with a timestamp, user identity, endpoint, and status. Admins can review the audit log in the TextQL console or stream it to their SIEM for long-term retention and alerting.