HubSpot

The HubSpot connection lets a ThunderPhone agent use selected CRM actions while speaking with a caller. An attached agent can search and read contacts and companies. With write permission enabled, it can also create or update contacts and add notes. This supports call flows where the CRM should provide context or receive a structured record of what the caller confirmed.

The connection does not turn every call into an automatic CRM update. Tools are available to the agent during the conversation, and the agent decides when to use them based on its prompt and the caller's request.

What the HubSpot connection does

HubSpot is a native app connection under Connections → Apps. An administrator or owner authorizes an account and controls the connection's operation permissions. Search and read access starts enabled. Creating or updating contacts and adding notes starts off until you explicitly enable write access.

Disabled operations are not offered to the agent on calls. That distinction allows one agent to look up approved context without being able to change CRM data, while another can record qualified details after the caller confirms them. You can connect multiple accounts and attach the appropriate one to each agent.

An effective prompt tells the agent when to search, which fields may be updated, what must be confirmed aloud, and when to stop and route the call to a person. It should also specify how to behave when no record is found or more than one record could match.

Typical call flows

Recognize an existing contact. In a lead qualification call, the agent can search for a contact and read available context before asking the next approved question. It should not assume that a partial match identifies the caller; ambiguous results require more confirmation or a human review.

Record a new or updated lead. After collecting and confirming the permitted details, an agent with write access can create or update a contact. This is the practical form of a CRM integration: structured information moves between the call and the system the team uses to continue the relationship.

Add a call note. The agent can add a concise note containing the confirmed request or outcome. The prompt should separate caller-provided facts from interpretation and avoid copying unnecessary sensitive information into the CRM.

Prepare a callback. In a speed-to-lead callback, the agent can search for existing context and update the contact when write access is allowed. A CRM write records information; it does not guarantee that a salesperson accepted or completed the follow-up.

Setup outline

1. Open Connections → Apps in ThunderPhone, choose HubSpot, and complete the account authorization flow.
2. Open the saved connection and review the operation toggles. Enable write access only if the agent needs to create or update contacts or add notes.
3. Open the agent in the builder and attach the HubSpot connection under Connected apps.
4. Update the prompt with lookup keys, writable fields, caller-confirmation rules, note format, and escalation conditions.
5. Test an exact match, no match, ambiguous matches, a permitted write, a denied write, and a provider error before deploying the agent configuration.
6. Review real call outcomes and CRM records together so prompt changes are based on both sides of the workflow.

Operating limits

The HubSpot tools expose contact, company, and note operations documented in the connection; they do not establish your data policy or sales process. Keep write permissions narrow, confirm critical values, and use human handoff for ownership disputes, sensitive changes, or requests outside the approved fields.

For intake design, see lead qualification. If you need a guaranteed event stream for your own backend after calls, use a separate webhook workflow rather than assuming a conversational CRM tool runs on every call.