BROSH AI CRM

Search CRM records with optional filtering, sorting, and pagination. Standard sales opportunities are stored in opportunities with type="Opportunity". Quotes and invoices are also stored in the opportunities table as types/subtypes, and quote/invoice lines are stored in opportunity_products. In opportunities, common fields include name, stage, amount, type, account, contact, owner, close_date, created_date, last_modified_date, currency, tax, discount, and sub_total. Type values are Opportunity, Quote, Invoice. Stage values include Prospecting, Qualification, Needs Analysis, Value Proposition, Id. Decision Makers, Perception Analysis, Proposal/Price Quote, Negotiation/Review, Closed Won, Closed Lost. In contacts, common fields include name, first_name, last_name, email, phone, mobile_phone, account, owner, type, country, town, title, department, industry, linkedin, email_opt_out, address, created_date, and last_modified_date. Contact type values are typically lead/customer (and some views may include contact). In accounts, common fields include id, name, phone, website, address, country, owner, type, industry, company_size, headquarters, founded, linkedin, created_date, last_modified_date, last_modified_by, created_by, number_of_contacts-exp, and number_of_users-exp. Account type values include Lead, Account, and Competitor. In products, common fields include name, productcode, description, price, list_price, currency, link, created_date, and last_modified_date. Product currency values include USD, EUR, GBP, AED, AUD, BRL, ILS, HKD, JPY, NZD, PLN, QAR, and RUB. In templates, common fields include id, name, subject, description, type, sub_type, sub_title, body, created_date, last_modified_date, and last_modified_by. Template type values include email, web + pdf, web + pdf + sign, and web form. Template sub_type values may include Marketing, Finance, Sales, Sales & Finance, and All. Activity stores emails, e-signatures on documents, tasks, and events linked to multiple related objects, and is also used for project tasks. In activity, core fields include name (subject), type, status, owner, person, account, opportunities, project, start_date, end_date, progress, last_modified_date, last_modified_by, created_date, ticket, campaign, template, from, to, cc, message_status, message_additional_info, file, and created_by. For activity-contact relationships, use the person field (not contact). In tickets, common fields include name (subject), description, contact, email, status, priority, origin, owner, account, created_date, last_modified_date, and last_modified_by. Ticket status values include New, In Work, Closed. Ticket priority values include High, Medium, Low. Ticket origin values include Phone, Web, Call. Use filter.search for free-text on the name field, filter.where for field-level conditions (plain value or {operator, value}), and sort for ordering results. Example: find opportunities where type="Opportunity" sorted by last_modified_date DESC, or filter opportunities by type="Quote" / type="Invoice", or query activity by related object/project fields, or query tickets by status/priority/origin/contact/account.

brosh_find

Send emails using BROSH CRM email engine. Supports template lookup by templateid, sender lookup by fromEmailSet, and direct template payloads. Before sending, MCP clients must query the email_settings table first to resolve the sender ID (fromEmailSet) and sender record (fromEmailSets). This tool requires explicit two-step confirmation: first call returns a preview + confirmationToken; second call must include confirm=true and the token. The upstream API validates sender permissions and required email content. Example: send a campaign email to filtered contact rows using a template and approved sender. Tip: if you process one row at a time, template.body can contain the exact AI-generated personalized message for that recipient, without parameters to replace.

brosh_send_email

Send emails one-by-one with a custom message per row. Before sending, MCP clients must query the email_settings table first to resolve the sender ID (fromEmailSet) and sender record (fromEmailSets). This tool requires explicit two-step confirmation: first call returns a preview + confirmationToken; second call must include confirm=true and the token. Each row can include message/body and subject, and MCP will call BROSH sendEmail per recipient. Use this when AI generates a unique message for each contact/account. Tip: this method processes one row at a time, and template.body can contain the exact AI-generated personalized message for that recipient, without parameters to replace.

brosh_send_message_single

Update one or more CRM records. Each object must include an "id" field. Schema is table-aware and includes common updatable fields per table to improve first-call accuracy. Example: update missing fields after AI enrichment.

brosh_update