← Back

Audit a call and log it in HubSpot

An agent with two MCP servers connected: FalaAI (transcription and audit) and HubSpot (CRM). You ask in one sentence; the agent orchestrates both tools.

FalaAI MCPEffort: 1 hour

Prerequisites

  • An MCP client with remote HTTP support (Claude Code, Cursor, VS Code or Gemini CLI).
  • A FalaAI key (fai_...) created in the dashboard.
  • A HubSpot account with access to the remote MCP server (OAuth authorized once in the browser).
  • The call audio file on your computer.

Configuration

FalaAI · .mcp.json

{
  "mcpServers": {
    "falaai": {
      "type": "http",
      "url": "https://mcp-falaai.action.tec.br/mcp",
      "headers": { "Authorization": "Bearer fai_..." }
    }
  }
}

HubSpot · remote server (OAuth)

https://mcp.hubspot.com

# Add this server in your client's MCP settings.
# On the first connection the client opens the browser to authorize the account.

Free test: ask “test the FalaAI health”. The reply brings status, version, uptime, database and API phase.

The request

"Transcribe ./calls/acme.mp3, audit the risk and log the result as a note on the Acme deal in HubSpot."

What the agent does

  1. Find the dealHubSpot MCP

    The agent locates the Acme deal and contact in the CRM.

    Input

    Company name: “Acme”

    Output

    Deal ID, primary contact and stage

  2. Transcribe the audio · transcribe_audioFalaAI MCP

    The agent reads the file, converts it to base64 and sends it to the tool.

    Input

    file_base64 (required), filename, language

    Output

    text, speaker-diarized dialog and audio events

  3. Audit the risk · risk_auditFalaAI MCP

    The diarized dialog goes straight into the audit; CRM participants can be passed as participants.

    Input

    dialog, duration_seconds, language (required); participants, call_direction, response_language (optional)

    Output

    Risk score, verdict, detections and the HTML report in the same response

  4. Log it in the CRMHubSpot MCP

    The agent creates a note on the deal with the audit summary.

    Input

    Deal ID + note text (score, verdict, detections)

    Output

    Note on the deal timeline

Result

  • Call audited and logged on the deal, no copy and paste.
  • The note carries the risk score, the verdict and the timestamped detections.
  • The same JSON feeds BI; the HTML goes to the end client.

Numbers and names above are illustrative.

Limitations

  • HubSpot requires OAuth: someone must authorize in the browser — it is not a hands-off scheduled job.
  • HubSpot custom objects are not covered by the official server.
  • HubSpot tool names vary with the server version; the agent discovers what exists.
  • Each call is a separate charge; cost follows volume.

Variations

  • Automatic ticket when the risk score crosses a threshold you set.
  • Pull the customer history before the audit and use it as note context.
  • Attach the risk_audit HTML report to the record.

Build × buy

Rather not build it? Action implements this flow in your environment, with your account and your access, and validates it with you.

Official sources: HubSpot — Remote MCP server

Open the quickstart Talk to Action
Audit a call and log it in HubSpot | FalaAI MCP