Zendesk Support connector FAQ
This page answers frequently asked questions about the managed Zendesk Support connector in Lakeflow Connect.
General managed connector FAQ
The answers in Managed connector FAQs apply to all managed connectors. Keep reading for Zendesk Support-specific FAQs.
Connector-specific FAQ
The answers in this section only apply to the Zendesk Support connector.
Can I limit the number of API calls the connector makes to Zendesk?
No. API call rate is managed automatically by the connector. If you are on a lower-tier Zendesk plan and are experiencing throughput issues, create a support ticket. See Get help.
What tables does the connector support?
The connector ingests data from multiple Zendesk APIs. Tables are either synced incrementally (using a cursor field) or using a full refresh. For a list of supported tables, see Supported source tables.
Fields with complex nested structures, such as custom_fields, are stored as strings for Delta Lake compatibility.
Can the connector ingest ticket attachments?
No. The article_attachments table includes a content_url field that points to each attachment file, but the connector does not download the raw file into a Unity Catalog volume. To access the files, retrieve them separately using the content_url values.
Does the connector support sideloading?
No. Sideloading allows fetching related data in a single API call (for example, macro metrics that aren't available through the primary entity endpoints).
How does the connector handle display values?
The connector ingests the raw stored values, not the display labels in the Zendesk UI. This is consistent with how other managed SaaS connectors handle enumerated fields. To resolve raw values to human-readable labels, join against the relevant Zendesk reference tables, such as custom field definitions.