AiEngage CRM

One dashboard and its tiles. Each tile carries a runnable `config` — pass it to analytics_run to compute that tile's current numbers. Answers 'what's on my Sales dashboard' and 'what does it say now'.

The organization's saved dashboards. Use for 'what dashboards do we have', and to find the id for dashboards_get.

The asking person's meetings for a date (defaults to today). Answers 'what meetings do I have', 'am I free tomorrow'.

The current user's productivity summary — open tasks, tasks due today, today's meetings, and pinned notes. Use for 'what's on my plate today?', 'how productive is the team today?'.

One productivity widget for the person asking: my_tasks, tasks_due_today, events_today, calendar, kanban or sticky_notes. Answers 'what's due today', 'what's on my plate'.

Fetch a single contact list by id.

List static contact lists (paginated).

The asking person's in-app notifications and unread count. Answers 'anything I missed', and explains failures — quota warnings and limit alerts land here.

Fetch a single CRM record by its id, with all of its properties. Use this after objects_search / objects_list gives you an id, or when the user references a specific record id directly. Optionally look up by a unique field instead via `id_property` (e.g. 'email').

List records of a CRM object type, newest first, with cursor pagination. Use `after` (from the previous response's `paging.next.after`) to fetch the next page, and `limit` (1-100, default 10) to bound the page size. Prefer objects_search when the user is filtering by a field value. `sort` is one key like 'created_at:desc'; `properties` is a comma-separated sparse fieldset.

List every CRM object type (module) available here, including the custom modules this org built — each entry has `slug` (the value every other tool's `module` param takes), `label`, `singular` and `plural`. CALL THIS FIRST whenever a question names a module outside the eleven standard ones (contacts, companies, deals, products, quotes, invoices, payments, tasks, meetings, calls, notes). A custom module's slug is NOT its display name — 'Stores' may be `stores`, `store` or `stores-1` — so match the user's word case-insensitively against label/singular/plural and use that entry's slug. Guessing a slug wastes a turn and returns a not-found you cannot distinguish from the module truly not existing. One call covers the whole conversation.

Search / filter records of a CRM object type. This is the tool for questions like 'find the contact named Prayas', 'open deals owned by X', 'contacts created this month', 'how many companies in India'. TWO WAYS TO SEARCH — pick the right one: 1. `query` — free text. Use this whenever the user names a person, company, email or phone and you do NOT know which field holds it ('find contact named Prayas' -> query='Prayas'). It matches a case-insensitive substring across every searchable field on the module at once, so you do not have to guess between first_name / last_name / full_name. Prefer it over guessing a field. 2. `filterGroups` — structured field filters, for conditions on a KNOWN property (stage, owner, amount, date). HubSpot-style DSL: a list of groups (OR between groups, AND within a group), each with `filters` of {propertyName, operator, value|values}. The two combine: passing both ANDs them (free text AND filters). VALID OPERATORS (exact strings — anything else is rejected with INVALID_FILTER): EQ, NEQ, LT, LTE, GT, GTE, BETWEEN, IN, NOT_IN, HAS_PROPERTY, NOT_HAS_PROPERTY, CONTAINS_TOKEN, NOT_CONTAINS_TOKEN, STARTS_WITH, ENDS_WITH. Note substring match is CONTAINS_TOKEN, not CONTAINS. Put the comparison in `value` for the single-value operators; use `values` for IN / NOT_IN (any length) and BETWEEN (exactly 2 — low, high); HAS_PROPERTY / NOT_HAS_PROPERTY take neither. Call properties_list first to get exact property names. Supports `sorts` ([{propertyName, direction: ASCENDING|DESCENDING}]), `limit`, and `after`. Max 5 groups, 6 filters/group. `limit` must be between 1 and 100 (never 0). To COUNT matching records, request `limit: 100` and count the `results`; if the response includes `paging.next`, there are more than 100 — page with `after` and keep a running total, or tell the user it exceeds 100. Do not pass limit:0 to get a count — that is rejected.

The plan's limits and how much of each is consumed — contacts, seats, storage, emails, API calls. Answers 'am I near my contact limit', 'how many seats are left', and explains why an action was blocked.

List the field (property) definitions for a CRM module — each field's key/slug, label, and type. Use this to discover the exact property names to pass to objects_search filters or the `properties`/`sort` args of objects_list.

The HISTORY of one record — what changed, when, and who did it. Every other tool returns a record's CURRENT state, so this is the only way to answer 'what happened on this lead?', 'who moved it to Won and when?', 'when did we last touch this account?'. Optional `activity_type` narrows to one kind of event.

Activity-type breakdown (calls, meetings, notes, emails, WhatsApp) for a date range, plus meetings-by-user. Use for 'team activity this month'. Same range params as reports_overview.

High-level sales/CRM overview KPIs for a date range (new contacts, connected, calls, meetings, emails, WhatsApp, lead-status distribution, daily activity trend). Use for 'how are things this week/month?'. Pass `range` for the window; it defaults to current_week, so omitting it on a question about another period returns the wrong numbers. The response echoes the window it actually used under `range` — check it before quoting figures.

Sales pipeline breakdown — deal counts/amounts by stage, and deals by user — for a date range. Use for 'what's in the pipeline?', 'deals by stage'. Same range params as reports_overview.

Per-user activity table for a date range — contacts, deals, calls and meetings per person. Answers 'who is my top performer', 'compare the team'. Attributes records by who CREATED them; for attribution by OWNER (which differs for inbound calls) use analytics_group_by. LIMITATION: this is a fixed table — the only filter is the date range. It CANNOT filter by a record's fields (lead source, stage, type, tag). When the question adds such a filter — 'contacts by user excluding lead source X' — do not refuse: rebuild the table with analytics_group_by, grouping by the user field and putting the filter in `criteria`. `search` matches a USER's name/email for narrowing the roster; it does not filter records.

The reports this organization has already built and named. Prefer running one of these over reinventing an equivalent query — a saved report is the definition the business agreed on, and its numbers match what the customer sees on their own screen.

Run a saved report by id and return its numbers. Get the id from saved_reports_list. Read-only: the definition is loaded, executed and discarded.

Search across EVERY module and entity at once. Use when the user names something without saying what it is — 'find Acme', 'what do we have on [email protected]' — and you do not yet know whether it is a company, contact, deal or note. When the module IS known, objects_search is more precise. Minimum 2 characters.

Fetch a single segment by id, with its definition.

KPI counters for one segment (total members, added/removed today, last processed). Use for 'how big is segment X?'.

List audience segments (paginated). Filter with `search`, `module_slug`, `type`.

Fetch one team by id, with its members expanded to names.

List teams with their leads and member counts. Use for 'what teams do we have', 'how big is the sales team'.

Fetch one person by their user id. Use to resolve a single owner id to a name.

List the people in this CRM — names, ids, active state, team membership. Use it to turn an owner id from a record into a NAME, and to answer 'who works here', 'who is on the sales team', 'is X still active'. Records return ownership as ids, so without this any 'who owns...' answer is an unreadable hex string — never guess a name, look it up. Optional `search` matches name or email.

Telephony allowance: calls made this month, the cap, and the phone number limit. Answers 'how many calls can we still make'. For call RECORDS use objects_search on the 'calls' module, and for call breakdowns use analytics_group_by.

Which phone number rings which agent, inbound and outbound. Answers 'who picks up calls to this number'. Requires the voice configuration permission.

The organization's web forms. Use to find a form id, then webforms_stats or webforms_submissions.

Submission counts and conversion for one form. Answers 'how many leads came through the Contact Us form'. An approved submission becomes a record and loses its provenance, so this is the only way to see the form funnel.

The submissions to one form, newest first, with their status (pending / approved / rejected) and captured data.

Fetch a single workflow by id, with its definition.

List automation workflows (paginated). Filter with `search`, `status`, `module_slug`, `trigger_type`.

Execution report / stats for one workflow (sent, delivered, read, clicked, failed, rates). Use for 'how is workflow X performing?'. `channel` is 'whatsapp' (default) or 'email'; optional date range via `date_from`/`date_to`.