SigParser

Query contacts (people) using structured filters. Good fields to select are: email_address, record_status, job_title, name_full, phone_mobile, phone_work, company_name, interactions_total (total interaction count), interactions_total_latest (date of last interaction). Common filters: - By status: {"field":"status","operator":"eq","value":["Valid"]} - By title level: {"field":"job_level","operator":"eq","value":["C-Level","Director","VP"]} - By company: {"field":"domain","operator":"eq","value":["example.com"]} - By email activity: {"field":"stat_emails_v2","operator":"gt","value":["10"]} Filter structure: outer array = OR groups, inner array = AND conditions within each group. - AND: [[{A},{B}]] — both conditions must match - OR: [[{A}],[{B}]] — either condition matches - OR of ANDs: [[{A},{B}],[{C},{D}]] — (A AND B) OR (C AND D) Operators are consistent across field types. Call the schema tool for the exact operators valid on each field. Some fields include a 'description' in the schema with usage notes for a special operator (e.g. the location fields' 'map' filter finds records within a distance of a place). - Equality: 'eq' / 'ne'. The value is an array, so multiple values act as IN: {"operator":"eq","value":["C-Level","Director","VP"]}. This works the same on status/select fields. - Numbers: 'gt' / 'lt'. For a range, combine 'gt' and 'lt' filters in the same group. - Text: 'contains', 'not_contains', 'starts_with', 'ends_with', 'contains_word', 'regex'. - Presence: 'is_null' / 'is_not_null' (has no value / has a value) — pass an empty value array. Available on most field types (text, number, date, location, ...) but not all — a status/select field, for example, always has a value; check the schema for the field. - Dates: 'after', 'before', 'last_days', 'before_days' (plus 'is_null' / 'is_not_null'). Dates use ISO 8601 format: "2026-01-15" Fields can be referenced by either their backend name (e.g. 'status') or their iPaaS API name (e.g. 'record_status') in filters, sort, and select. Use the schema tool to discover available fields. Note: response fields always use the iPaaS API name regardless of which name you pass in filters, sort, or select. When no 'select' is specified, the response returns a curated set of default fields to reduce payload size. Use 'select' to explicitly request additional fields if needed.

query_contacts

Query coworkers (internal team members whose mailboxes are connected). Good fields to select are: employment_status, name, emailaddress, title. Common filters: - By activity: {"field":"stat_emails_v2","operator":"gt","value":["100"]} Filter structure: outer array = OR groups, inner array = AND conditions within each group. - AND: [[{A},{B}]] — both conditions must match - OR: [[{A}],[{B}]] — either condition matches - OR of ANDs: [[{A},{B}],[{C},{D}]] — (A AND B) OR (C AND D) Operators are consistent across field types. Call the schema tool for the exact operators valid on each field. Some fields include a 'description' in the schema with usage notes for a special operator (e.g. the location fields' 'map' filter finds records within a distance of a place). - Equality: 'eq' / 'ne'. The value is an array, so multiple values act as IN: {"operator":"eq","value":["C-Level","Director","VP"]}. This works the same on status/select fields. - Numbers: 'gt' / 'lt'. For a range, combine 'gt' and 'lt' filters in the same group. - Text: 'contains', 'not_contains', 'starts_with', 'ends_with', 'contains_word', 'regex'. - Presence: 'is_null' / 'is_not_null' (has no value / has a value) — pass an empty value array. Available on most field types (text, number, date, location, ...) but not all — a status/select field, for example, always has a value; check the schema for the field. - Dates: 'after', 'before', 'last_days', 'before_days' (plus 'is_null' / 'is_not_null'). Dates use ISO 8601 format: "2026-01-15" Fields can be referenced by either their backend name (e.g. 'status') or their iPaaS API name (e.g. 'record_status') in filters, sort, and select. Use the schema tool to discover available fields. Note: response fields always use the iPaaS API name regardless of which name you pass in filters, sort, or select. When no 'select' is specified, the response returns a curated set of default fields to reduce payload size. Use 'select' to explicitly request additional fields if needed.

query_coworkers

Query contact job experiences (historical job records). Each record represents a job a contact has held, including company, title, start/end dates, and whether it's their current role. Use this to track career history and job changes for contacts. Good fields to select are: name, company_name, company_domain, job_title, job_type, job_start_date, job_end_date. Common filters: - Current jobs only (no end date): {"field":"job_end_date","operator":"is_null","value":[]} - By company domain: {"field":"company_domain","operator":"eq","value":["example.com"]} - By title: {"field":"job_title","operator":"contains","value":["Engineer"]} Filter structure: outer array = OR groups, inner array = AND conditions within each group. - AND: [[{A},{B}]] — both conditions must match - OR: [[{A}],[{B}]] — either condition matches - OR of ANDs: [[{A},{B}],[{C},{D}]] — (A AND B) OR (C AND D) Operators are consistent across field types. Call the schema tool for the exact operators valid on each field. Some fields include a 'description' in the schema with usage notes for a special operator (e.g. the location fields' 'map' filter finds records within a distance of a place). - Equality: 'eq' / 'ne'. The value is an array, so multiple values act as IN: {"operator":"eq","value":["C-Level","Director","VP"]}. This works the same on status/select fields. - Numbers: 'gt' / 'lt'. For a range, combine 'gt' and 'lt' filters in the same group. - Text: 'contains', 'not_contains', 'starts_with', 'ends_with', 'contains_word', 'regex'. - Presence: 'is_null' / 'is_not_null' (has no value / has a value) — pass an empty value array. Available on most field types (text, number, date, location, ...) but not all — a status/select field, for example, always has a value; check the schema for the field. - Dates: 'after', 'before', 'last_days', 'before_days' (plus 'is_null' / 'is_not_null'). Dates use ISO 8601 format: "2026-01-15" Fields can be referenced by either their backend name (e.g. 'status') or their iPaaS API name (e.g. 'record_status') in filters, sort, and select. Use the schema tool to discover available fields. Note: response fields always use the iPaaS API name regardless of which name you pass in filters, sort, or select. When no 'select' is specified, the response returns a curated set of default fields to reduce payload size. Use 'select' to explicitly request additional fields if needed.

query_job_experiences

Query coworker-to-contact relationships. Each record represents the interaction history between one coworker and one external contact, including email counts, last interaction dates, and meeting stats. Use this to find who on your team has the strongest relationship with a specific contact or company. Good fields to select are: coworker_emailaddress, coworker_name, contact_work_email, contact_name, account_name, total_interactions, emails_to, emails_from, total_meetings, latest_interaction. When filtering by an email address (contact_work_email or coworker_emailaddress), prefer the 'eq' operator over 'contains'. 'eq' uses an indexed exact match while 'contains' triggers a full table scan and is much slower — only fall back to 'contains' when the user genuinely needs partial-string matching. Default sort when omitted: total_interactions desc (strongest relationships first). Common filters: - By contact email: {"field":"contact_work_email","operator":"eq","value":["[email protected]"]} - By coworker email: {"field":"coworker_emailaddress","operator":"eq","value":["[email protected]"]} - By interaction volume: {"field":"total_interactions","operator":"gt","value":["10"]} Filter structure: outer array = OR groups, inner array = AND conditions within each group. - AND: [[{A},{B}]] — both conditions must match - OR: [[{A}],[{B}]] — either condition matches - OR of ANDs: [[{A},{B}],[{C},{D}]] — (A AND B) OR (C AND D) Operators are consistent across field types. Call the schema tool for the exact operators valid on each field. Some fields include a 'description' in the schema with usage notes for a special operator (e.g. the location fields' 'map' filter finds records within a distance of a place). - Equality: 'eq' / 'ne'. The value is an array, so multiple values act as IN: {"operator":"eq","value":["C-Level","Director","VP"]}. This works the same on status/select fields. - Numbers: 'gt' / 'lt'. For a range, combine 'gt' and 'lt' filters in the same group. - Text: 'contains', 'not_contains', 'starts_with', 'ends_with', 'contains_word', 'regex'. - Presence: 'is_null' / 'is_not_null' (has no value / has a value) — pass an empty value array. Available on most field types (text, number, date, location, ...) but not all — a status/select field, for example, always has a value; check the schema for the field. - Dates: 'after', 'before', 'last_days', 'before_days' (plus 'is_null' / 'is_not_null'). Dates use ISO 8601 format: "2026-01-15" Fields can be referenced by either their backend name (e.g. 'status') or their iPaaS API name (e.g. 'record_status') in filters, sort, and select. Use the schema tool to discover available fields. Note: response fields always use the iPaaS API name regardless of which name you pass in filters, sort, or select. When no 'select' is specified, the response returns a curated set of default fields to reduce payload size. Use 'select' to explicitly request additional fields if needed.

query_relationships