name: tp-salesforce-crm-manager
description: |
Salesforce CRM management via Composio for Twin Peaks Wealth advisors. Use for any Salesforce interaction: creating/searching/updating/deleting accounts, contacts, leads, and tasks, geographic client queries, or running SOQL. Trigger on "Salesforce", "CRM", "leads", "contacts", "accounts", "tasks", "SOQL", "pipeline", "create a lead", "my tasks", "find contact", "update contact", "clients near", "what's on my plate", or any CRM read/write request. Contains exact tool slugs and parameter schemas for reliable execution.

Twin Peaks Salesforce CRM Manager

This skill enables reliable Salesforce CRM operations for Twin Peaks Wealth advisors through Composio's MCP integration. It provides full CRUD operations across four Salesforce objects — Accounts, Contacts, Leads, and Tasks — plus geographic client queries and raw SOQL access.

Every tool slug, parameter schema, and execution pattern is documented here so you never need to guess or search — just execute.

Setup & Connection

MCP Server Config: mcp-config-5-gpex

All Salesforce tools in this skill are routed through the Composio MCP server registered as mcp-config-5-gpex. This is the preconfigured Composio instance that holds the Salesforce OAuth connection for Twin Peaks.

Before first use

1. Verify the Salesforce connection is active by calling COMPOSIO_CHECK_ACTIVE_CONNECTION with toolkit: "salesforce" through the mcp-config-5-gpex server
2. If no active connection exists, call COMPOSIO_MANAGE_CONNECTIONS with toolkits: ["salesforce"] and guide the user through the OAuth flow
3. Once connected, note the connected_account_id and user_id from the connection details — you'll need them for owner-scoped queries

How to execute tools

All Salesforce tools are called through the mcp-config-5-gpex Composio MCP server using COMPOSIO_MULTI_EXECUTE_TOOL (parallel/batch) or COMPOSIO_EXECUTE_TOOL (single):

Tool: mcp__mcp-config-5-gpex__COMPOSIO_MULTI_EXECUTE_TOOL
Parameters:
  sync_response_to_workbench: false
  tools: [{ tool_slug: "<SLUG>", arguments: { ... } }]
  memory: { "salesforce": ["<connection details you've gathered>"] }
  current_step: "<STEP_NAME>"
  thought: "<one-line rationale>"

Important: Always prefix Composio tool calls with mcp__mcp-config-5-gpex__ to route through the correct MCP server. For example:
- mcp__mcp-config-5-gpex__COMPOSIO_MULTI_EXECUTE_TOOL
- mcp__mcp-config-5-gpex__COMPOSIO_EXECUTE_TOOL
- mcp__mcp-config-5-gpex__COMPOSIO_SEARCH_TOOLS
- mcp__mcp-config-5-gpex__COMPOSIO_MANAGE_CONNECTIONS
- mcp__mcp-config-5-gpex__COMPOSIO_CHECK_ACTIVE_CONNECTION

Quick Reference: All Tool Slugs

Accounts

Contacts

Leads

Tasks

Other

Accounts

Create an account

Tool: SALESFORCE_CREATE_ACCOUNT

Example:

{
  "Name": "Test 1",
  "Type": "Prospect",
  "BillingCity": "San Francisco",
  "BillingState": "CA"
}

Response: New Account ID at response.data.id.

Search accounts

Tool: SALESFORCE_SEARCH_ACCOUNTS

Get a single account

Tool: SALESFORCE_GET_ACCOUNT

Update an account

Tool: SALESFORCE_UPDATE_ACCOUNT

Only include fields you want to change — omitted fields are left untouched.

Delete an account

Tool: SALESFORCE_DELETE_ACCOUNT

Warning: Deleting an account may cascade-delete or orphan related contacts, tasks, and opportunities. Always confirm with the advisor before deleting.

Contacts

Create a contact

Tool: SALESFORCE_CREATE_CONTACT

If the advisor mentions an account name, resolve the Account ID first with SALESFORCE_SEARCH_ACCOUNTS, then pass it as AccountId.

Example:

{
  "LastName": "Kumar",
  "FirstName": "Priya",
  "AccountId": "001dL00001xrytEQAQ",
  "Email": "[email protected]",
  "Phone": "(650) 555-9876",
  "Title": "Managing Partner"
}

Search contacts

Tool: SALESFORCE_SEARCH_CONTACTS

Example — list all contacts for an account:

{
  "account_name": "Kumar Family Trust"
}

Get a single contact

Tool: SALESFORCE_GET_CONTACT

Update a contact

Tool: SALESFORCE_UPDATE_CONTACT

Only include fields you want to change. If the advisor refers to a contact by name, resolve the ID first with SALESFORCE_SEARCH_CONTACTS.

Delete a contact

Tool: SALESFORCE_DELETE_CONTACT

Always confirm with the advisor before deleting a contact.

Leads

Create a lead

Tool: SALESFORCE_CREATE_LEAD

Always check for duplicates first with SALESFORCE_SEARCH_LEADS using email or name. If a match exists, inform the advisor and offer to update instead.

Example:

{
  "LastName": "Chen",
  "FirstName": "Sarah",
  "Company": "Anthropic",
  "Email": "[email protected]",
  "Title": "Senior Engineer",
  "City": "San Francisco",
  "State": "CA",
  "Status": "New",
  "LeadSource": "Partner Referral",
  "Rating": "Hot"
}

Response: New Lead ID at response.data.id.

Search leads

Tool: SALESFORCE_SEARCH_LEADS

Get a single lead

Tool: SALESFORCE_GET_LEAD

Update a lead

Tool: SALESFORCE_UPDATE_LEAD

Accepts the same fields as create (except allow_duplicates). Only include fields you want to change.

Delete a lead

Tool: SALESFORCE_DELETE_LEAD

Always confirm with the advisor before deleting.

Tasks

Create a task

Tool: SALESFORCE_CREATE_TASK

If the advisor mentions an account name, resolve the Account ID first with SALESFORCE_SEARCH_ACCOUNTS, then pass it as what_id. This ensures the task appears on the account's activity timeline.

Example:

{
  "subject": "Schedule Q2 portfolio review with the Kumars",
  "priority": "High",
  "activity_date": "2026-03-25",
  "what_id": "001dL00001xrytEQAQ",
  "status": "Not Started",
  "description": "Discuss rebalancing strategy and tax-loss harvesting opportunities"
}

Search tasks

Tool: SALESFORCE_SEARCH_TASKS

Example — show open tasks:

{ "is_closed": false, "assigned_to_name": "<advisor's name>" }

Update a task

Tool: SALESFORCE_UPDATE_TASK

If the advisor refers to a task by name, resolve its ID first with SALESFORCE_SEARCH_TASKS using subject.

Complete a task

Tool: SALESFORCE_COMPLETE_TASK

Sets Status to "Completed" and IsClosed to true.

Delete a task

Tool: SALESFORCE_DELETE_TASK

Always confirm with the advisor before deleting. If the advisor refers to a task by name, resolve its ID first with SALESFORCE_SEARCH_TASKS.

Geographic Client Queries

Use when a Twin Peaks advisor wants to find clients near a location — for event planning, regional outreach, or proximity-based filtering.

Step 1 — Query accounts by city/state/region

Use SALESFORCE_RUN_SOQL_QUERY:

query: "SELECT Id, Name, Phone, BillingStreet, BillingCity, BillingState, BillingPostalCode FROM Account WHERE BillingCity = 'Menlo Park' AND BillingState = 'CA'"

For broader queries, use IN with nearby cities:

query: "SELECT Id, Name, Phone, BillingStreet, BillingCity, BillingState, BillingPostalCode FROM Account WHERE BillingState = 'CA' AND BillingCity IN ('Menlo Park', 'Palo Alto', 'Redwood City', 'Mountain View', 'San Mateo', 'Sunnyvale', 'Los Altos', 'Atherton')"

Step 2 — For radius-based queries, calculate distances

When the advisor asks for "within X miles," use the Composio Remote Workbench with the haversine formula to filter by distance after pulling accounts with addresses. Use a geocoding lookup to convert city names to coordinates.

Common geographic queries

Contacts variant

Query the Contact object for people instead of accounts:

query: "SELECT Id, Name, Email, Phone, MailingCity, MailingState, Account.Name FROM Contact WHERE MailingCity = 'Menlo Park' AND MailingState = 'CA'"

Leads variant

query: "SELECT Id, Name, Email, Phone, City, State, Company FROM Lead WHERE City = 'Menlo Park' AND State = 'CA' AND IsConverted = false"

SOQL Quick Reference

• No AS keyword for aliases — use implicit: SUM(Amount) TotalSales
• FIELDS(ALL) requires LIMIT 200
• Wrap ID values in single quotes: AccountId = '001...'
• Escape apostrophes with backslash: Name = 'O\'Brien'
• Aggregate queries without GROUP BY cannot use ORDER BY or LIMIT
• IN clauses use parentheses with single-quoted values: BillingCity IN ('Menlo Park', 'Palo Alto')

Status & Priority Reference

Task Status: "Not Started" (default), "In Progress", "Completed", "Waiting on someone else", "Deferred"

Task Priority: "High", "Normal" (default), "Low"

Lead Status: "New", "Working - Contacted", "Qualified", "Closed - Converted", "Closed - Not Converted"

Lead Rating: "Hot", "Warm", "Cold"

Error Handling

• 400 INVALID_FIELD: A field name doesn't exist on the object. Remove it and retry with fewer fields.
• REQUIRED_FIELD_MISSING: You're missing a required field (e.g. LastName + Company for leads, subject for tasks, Name for accounts).
• MALFORMED_ID: An ID is not a valid 15/18-char Salesforce ID. Double-check the value.
• Duplicate rules: If create fails due to org duplicate rules, search first and decide whether to update instead.
• Pagination: If response.data.done is false, there are more records. Use nextRecordsUrl to fetch subsequent pages.

Common Patterns

Resolve an account name to ID

1. SALESFORCE_SEARCH_ACCOUNTS with name: "<partial name>"
2. Extract Id from first match
3. Pass as what_id (tasks), AccountId (contacts), etc.

Resolve a contact by name to ID

1. SALESFORCE_SEARCH_CONTACTS with name: "<partial name>"
2. Confirm with advisor if multiple matches
3. Pass Id as contact_id

Resolve a task by subject to ID

1. SALESFORCE_SEARCH_TASKS with subject: "<partial subject>"
2. Extract Id from matching record
3. Pass as task_id

Check for duplicate leads before creating

1. SALESFORCE_SEARCH_LEADS with email or name
2. If results exist, inform advisor and offer to update instead
3. If no results, proceed with SALESFORCE_CREATE_LEAD

Create an account and immediately add a task to it

1. SALESFORCE_CREATE_ACCOUNT with Name
2. Extract Id from response.data.id
3. SALESFORCE_CREATE_TASK with what_id set to the new account ID