The CRM update agent closes the loop between a sales conversation and your CRM record. After a meeting with a prospect, you supply the transcript and the client’s name. The agent searches the web for recent news about the client, asks the LLM to extract structured CRM-ready data from the transcript, and writes a row to your Google Sheet. It captures everything a sales manager needs to track an opportunity: what was discussed, what the client needs, objections raised, budget signals, urgency, next steps, and estimated deal value.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/vrashmanyu605-eng/Agentic_Sales-Markerting/llms.txt
Use this file to discover all available pages before exploring further.
State inputs
The full text of the meeting transcript. The LLM analyzes this to extract all CRM fields.
The name of the client company. Used to search for recent news and written to the Google Sheet as the row identifier.
The Google Sheets spreadsheet ID. If not provided, the agent skips the sheet write and logs a warning. The spreadsheet ID is the long alphanumeric string in the sheet’s URL.
The cell range to write to. Defaults to
"Sheet1!A1" if not provided. Use standard A1 notation (e.g., "CRM!A2") to target a specific sheet and starting cell.State outputs
A JSON string containing the full extracted CRM data. See output schema for all fields. This is stored in state regardless of whether the Google Sheet write succeeds.
What it does
Search for recent client news
The agent constructs the query
"recent news {client_name} company" and calls web_search. Fresh news about funding rounds, leadership changes, acquisitions, or product launches can reveal new buying signals or objections not mentioned in the transcript.Extract CRM data with the LLM
The agent sends
client_name, meeting_transcript, and client_news to the LLM. The LLM extracts seven structured fields: meeting summary, client requirements, objections, budget signals, urgency level, next steps, and estimated opportunity value.Write to Google Sheets
The agent parses the LLM’s JSON response and builds a single-row array with five columns:
client_name, meeting_summary, client_requirements, opportunity_value, and next_steps. If spreadsheet_id is present in state, the agent calls update_google_sheet to append the row. If the ID is missing, the agent logs a warning and skips the write.Tools used
web_search
Fetches recent news about the client company to supplement transcript analysis with current context.
google_sheets
Writes the extracted CRM row to the specified Google Sheet using the Sheets API.
Google Sheet columns
The agent writes exactly one row per invocation. The columns written are, in order:| Column | Source field | Description |
|---|---|---|
| A | client_name | The client company name from state |
| B | meeting_summary | LLM-generated summary of the meeting |
| C | client_requirements | Requirements extracted from the transcript |
| D | opportunity_value | Estimated deal value or revenue opportunity |
| E | next_steps | Agreed follow-up actions from the meeting |
Output schema
The LLM is prompted to return structured JSON only. The expected structure is:objections and budget_signals are not written to Google Sheets by default, but they are available in the crm_update state field for use in follow-up outreach or internal review.