Bob with HubSpot: keep customer work connected to the CRM

Matthew, founder of Bob · Published July 30, 2026

Short answer

Bob's purpose-built HubSpot connection can search contacts, companies, and deals, fetch a record, create a contact, update a deal, and add a note. HubSpot's CRM search API supports filters and sorting across CRM objects. Bob turns those records into useful customer work without forcing the team to copy data between Slack and the CRM.

The connection is personal. Bob acts with the HubSpot access of the person who connected it, and HubSpot permissions still control which records and properties are available.

Five useful Bob and HubSpot workflows

1. Prepare an account brief

"Brief me on Acme before today's call. Include the HubSpot company and deal, the latest Gmail thread, and open support issues."

HubSpot provides the account record while the other systems provide current evidence.

2. Find stale deals

"Find deals closing this month with no recent note or an overdue next step. Group them by owner."

This is a read-only report that can become a recurring Slack brief after the first result is verified.

3. Create a contact from the conversation

"Create a HubSpot contact for the partner in this thread with their confirmed email and company. Show me the fields first."

Bob checks the available data, prepares the record, and asks before creation.

4. Update a deal after a decision

"Prepare the Acme deal update: move it to contract review and set the next step to legal redlines. Do not change the amount."

A narrow instruction keeps the write legible. Bob asks before the record changes.

5. Add a durable note

"Turn the approved call summary into a HubSpot note and include the commitments and owners."

The CRM gets the durable outcome rather than a pasted Slack transcript.

How the connection works

1. Ask Bob in Slack to connect HubSpot.
2. Open the hosted OAuth flow and choose the intended HubSpot account.
3. Review the requested scopes and user permissions.
4. Return to Slack and retry the CRM request.

HubSpot is a personal connection in Bob. Two teammates can connect their own accounts and Bob will act with the requesting person's access rather than silently borrowing a workspace-wide identity.

Limits worth knowing

• Permissions still apply. Bob cannot access records or properties unavailable to the connected HubSpot user.
• Search needs real fields. Custom property names and pipeline stages should match the portal.
• The write set is specific. This page claims contact creation, deal update, and note creation, not arbitrary mutation of every HubSpot object.
• Writes ask by default. CRM records affect customer work and reporting, so review the proposed fields.

FAQ

What can Bob do with HubSpot?

Bob can search contacts, companies, and deals, get a record, create a contact, update a deal, and add a note.

Whose HubSpot access does Bob use?

The person who connected HubSpot. The connection is personal.

Does Bob ask before updating HubSpot?

Yes. Contact creation, deal updates, and notes ask by default.

Can Bob change every HubSpot object?

No. The current purpose-built writes described here are deliberately narrower.

Start with the account brief you already prepare

Have Bob reproduce one known account view and check every source. Then add Gmail, Google Calendar, or Google Sheets to close the gap between the CRM and the actual work.