Close – Gotchas

Close Smart Views are always dynamic saved queries; filter_criteria carries Close's structured s_query definition, falling back to the older query field for saved searches created before Close's structured-search migration. record_count, folder_id, created_by/updated_by, the favorite/default/system flags, custom_fields, and tags are not available. visibility derives from is_shared, and owner_id reflects the saved search's user_id; every saved search observed in testing (shared and private alike) had a user_id, so whether owner_id is ever genuinely null for organization-wide views has not been confirmed against a real account. The list operation only returns saved searches of type lead, contact, or opportunity; saved searches of other types (call, email, sms, meeting, note, whatsapp_message, custom_activity, form_submission) are excluded from the list but remain retrievable by id, with object_type set to the raw Close type. Close's saved-search endpoint ignores server-side offsets, so results are fetched as a single page (up to Close's undeclared server default of around 100 smart views) and paginated virtually; accounts with more than that many smart views will have the overflow silently dropped, with no field in the response indicating truncation occurred.

Close Smart Views are always dynamic saved queries; filter_criteria carries Close's structured s_query definition, falling back to the older query field for saved searches created before Close's structured-search migration. record_count, folder_id, created_by/updated_by, the favorite/default/system flags, custom_fields, and tags are not available. visibility derives from is_shared, and owner_id reflects the saved search's user_id; every saved search observed in testing (shared and private alike) had a user_id, so whether owner_id is ever genuinely null for organization-wide views has not been confirmed against a real account. A saved search of any type is retrievable by id, including types the list operation excludes (call, email, sms, meeting, note, whatsapp_message, custom_activity, form_submission), in which case object_type is set to the raw Close type.

When creating a note in Close, the content of the note should be sent in html surrounded by the tags and at least other inner element. If these tags are not sent, unify will surround the note with and

tags.

When updating a note in Close, the content of the note should be sent in html surrounded by the tags and at least other inner element. If these tags are not sent, unify will surround the note with and

tags.