Connect Clarify and work with your CRM using natural language. Retrieve, create, and update records, analyze your pipeline, and generate insights—all through conversation. Query deals, companies, people, and meetings without switching apps. Find and import new leads that match your ICP directly from the conversation. Create tasks, lists, and outbound sequences automatically. Build and configure Clarify Agents from Claude to automate your entire GTM motion. Your Clarify data is retrieved in real-time, and permissions are respected. Stop clicking through interfaces. Just ask what you need.
-> - Extract JSON object (returns JSONB): column->'key' - ->> - Extract text value (returns TEXT): column->>'key' - jsonb_array_elements(column->'items') - Iterate over JSONB arrays JSONB Column Patterns Object with nested fields (e.g., JSONB with format {first_name: string, last_name: string}): - Access nested field: column->>'first_name' - Concatenate fields: CONCAT(column->>'first_name', ' ', column->>'last_name') - Filter: column->>'first_name' ILIKE '%john%' Array of items (e.g., JSONB with format {items: string[]}): - Get first item: column->'items'->>0 - Iterate items: jsonb_array_elements(column->'items') as item - Access nested in item: (item->>'email') Important notes - Only use JSONB operators (->, ->>) on columns explicitly marked as "JSONB with format" in the schema. Regular string columns use standard SQL operators (ILIKE, =, etc.) - Always prefix columns with table names (e.g., person.name, not name) - Use ILIKE for case-insensitive matching (not LIKE) - Query timestamps using UTC/ISO 8601 format (e.g., '2025-12-22T00:00:00Z') - Results will have timestamps formatted in the user's timezone for readability - For many-to-many relationships, use INNER JOIN with join tables Time-Based Queries Use the current time from get-current-user tool or system context as reference. "Last" vs "Next" Terminology - "last meeting" = Most recent past meeting: WHERE meeting.start < NOW() ORDER BY meeting.start DESC LIMIT 1 - "next meeting" = Soonest future meeting: WHERE meeting.start > NOW() ORDER BY meeting.start ASC LIMIT 1 - "recent meetings" = Meetings in the past, not upcoming ones - "upcoming meetings" = Meetings in the future Time Period Interpretation When user mentions "Q4 2025", "last quarter", or similar: - Activity in that period: Filter by date: WHERE meeting.start >= '2025-10-01' AND meeting.start < '2026-01-01' - Content mentioning that period (e.g., "meetings where Q4 was discussed"): Search transcripts/summaries, not date filter Before Writing SQL - Review the "Available Tables and Columns" section for exact column names and types - Call get-current-user if the query involves "me", "my", or "I", if the tool is available User-Scoped Queries When querying data related to "me", "my", or "I": - Use the current user's ID to filter records - Remember: user and person are different tables - user = internal workspace members, person = external contacts - For meetings: INNER JOIN user_meeting ON meeting._id = user_meeting.meeting_id WHERE user_meeting.user_id = '<user-id>' - External meetings have attendees who are not workspace users. Check person_meeting but exclude persons whose email matches a user: EXISTS (SELECT 1 FROM person_meeting pm JOIN person p ON p._id = pm.person_id WHERE pm.meeting_id = meeting._id AND NOT EXISTS (SELECT 1 FROM "user" u WHERE u.email IN (SELECT jsonb_array_elements_text(p.email_addresses->'items')))) - Internal meetings have no truly external attendees (inverse of above) - For tasks: Filter by assignee_id: WHERE task.assignee_id = '<user-id>' - For deals: Filter by owner_id: WHERE deal.owner_id = '<user-id>' Activity Counting Activity includes: meetings, messages, tasks, and comments. To count activity: - Comments: Query comment table with entity = '<entity-type>' and owner_id = <entity>._id. Use _created_at as timestamp. - Meetings: Join through person_meeting join table. If entity relates to person via join table (e.g., person_deal) or foreign key (e.g., person.company_id), join: entity → person → person_meeting → meeting. Use meeting.start as timestamp. - Messages: Join through person_message join table. Same pattern as meetings: entity → person → person_message → message. Use message.received_at as timestamp. - Tasks: Join via foreign key task.deal_id. For deals: direct join. For companies: join deal first (via deal.company_id), then task. Use task._created_at as timestamp. Pattern: Create CTEs for each activity type, UNION ALL them, then LEFT JOIN to your entity table. Use COUNT() and MAX() for totals and last activity date. Pagination - When user asks for "more" results, use the EXACT same SQL query and only change the offset parameter - The tool will tell you the next offset value to use (e.g., "Call this tool again with offset=25 to continue")App Stats
35
Tools
0
Prompts
Apr 21, 2026
First seen
ChatGPT, Claude
Platforms
Category
CRM RecordsWorks with
Data refreshed daily
