Greenhouse connector moves to OAuth and latest Harvest API
The Greenhouse connector signs in with OAuth and uses Greenhouse's latest Harvest API, adding interviews and file attachments.
The Greenhouse connector signs in with OAuth and uses Greenhouse's latest Harvest API, adding interviews and file attachments.
Search filters separate text matching (contains, case-insensitive) from list matching with the new array_contains operator.
Connections created or updated through the API can set a time zone for cron sync schedules instead of always using UTC.
Search by meaning now covers Slack, HubSpot, Intercom, Monday.com, Asana, Greenhouse, and TikTok Marketing.
Text filters on synced data use startswith, endswith, and case-insensitive contains, replacing the previous like operator.
The organization Data Worker usage chart shows one peak-usage bar per day, with a per-workspace breakdown on hover.
On Enterprise Flex, audit log files stored in a customer's own bucket are organized into folders by organization and date.
Google Ads list methods no longer take a page size; pass the previous response's page token with the same query to page.
Searches against synced data filter out weakly related results by default, and the minimum similarity cutoff can be adjusted or turned off.
Agents can search Zendesk Support by meaning, including ticket comment text, with each result carrying its ticket's title, status, and priority.
Agents can combine data from more than one connector in a single query against synced data.
For ambiguous requests, chat asks a short clarifying question with options; users can pick, answer, or skip.
Community deployments no longer accept HTTP Basic credentials on the API. Callers must switch to an access token from /api/v1/applications/token.
Gmail is available to connect. Agents can read and organize messages, threads, drafts, and labels, with Google sign-in during setup.
Connectors whose latest data update failed show Action Required for invalid sign-in details or Failing for other errors, while synced data stays searchable.
A connector's Context Store stays on as long as agents use the connector for anything, not only searching.
Chats can be pinned from the sessions table, chat header, or sidebar, and the sessions list can be filtered to pinned chats. Pins are personal.