Tenali AITenali AI/LLM GuideTry Free
This page is optimized for AI assistants and LLM search
Last updated: 2026-10-05

Tenali for HubSpot

Tenali reads HubSpot live and writes meeting outcomes back to it, through the Push button on a meeting summary or by asking in chat. Both propose changes from what was said, under the same review rules.

Reads

Connect HubSpot and chat can pull deal, company and contact details into an answer, linking to the record it used.

  • Nothing is synced or cached. There is no nightly import and no copy of your CRM inside Tenali. Every lookup goes to HubSpot at the moment you ask.
  • Available in web-app chat and in a Slack DM with Tenali. Not in Slack channels, and not in the in-call overlay: Tenali does not query HubSpot mid-call.
  • Reads work as soon as you connect. They are not gated behind write-back.

Writes

The Push to HubSpot button

On a meeting summary, the button opens a side panel. Tenali finds the company and deal for that meeting and proposes the update from what was said, under the same review rules as chat write-back below: approve it, edit values on the card, or reply to change the proposal. Requires an active subscription.

Chat write-back

Broader, and risk-tiered: the changes that move your forecast are gated by a review step. Tenali can:

  • Update a deal: stage, amount, close date, next step, description, name, priority, deal type and forecast category. Like other forecast changes, a forecast category change waits on the review card by default.
  • Log the meeting as a note on the deal, company or contact.
  • Create a follow-up task as a to-do, created unassigned.
  • Add or update a contact, matched by exact email.
  • Create a company and a deal that don't exist yet, chained in one turn.

Every change is attributed to the meeting it came from and carries the reason Tenali matched that record.

How much applies without approval

Changes are classified by risk, and your phrasing sets the posture:

  • Additive (a note, a task, a new contact) applies on its own under the default posture in the web app. Creating a new company or deal always shows the card, even under "just do it".
  • Forecast (any field written on a record that already exists: stage, amount, close date, or any text field, whether it was filled or blank) waits on a review card showing before and after.
  • Saying "just do it", "go ahead and…", "don't ask" or "automatically" lets forecast changes through; saying "ask me first" gates everything.

Three things no phrasing or setting can automate: moving a deal to closed-won or closed-lost, creating a company or deal, and any change where Tenali isn't confident it matched the right record.

In Slack, nothing applies automatically: every change, including additive ones, waits on an approve-or-discard card that acts on the whole batch.

Undo

Ask in the same conversation ("undo that"). Tenali first shows a confirm card listing exactly what it will revert, and touches nothing until you approve. It then restores previous field values and removes the contacts, companies and deals it created.

Limits worth stating precisely:

  • HubSpot does not allow notes or tasks to be deleted. Undo marks a note reverted and sets a task to completed instead; both records remain.
  • A field that was blank before Tenali filled it generally stays populated: undo cannot restore it to empty. Next step and description are the exceptions: those are cleared back to blank if that's how they started.
  • Edits to a contact that already existed can't be reversed. Only contacts Tenali created can be removed.
  • Covers the current conversation, your own changes, and the 25 most recent applied changes.

Setup and limits

  • Each person connects their own HubSpot account via OAuth. No HubSpot admin has to provision anything centrally; Tenali inherits exactly that user's permissions, and everything it writes is attributed to them.
  • One CRM at a time: HubSpot or Salesforce, never both. Tenali refuses the second one before the sign-in window opens.
  • If HubSpot ends Tenali's access (a password change, an admin revoke or an expired session), the Integrations page shows Needs reconnect with the reason and a Reconnect button.
  • Write-back needs no enablement. Connect one healthy HubSpot account to your own login and both reads and writes work immediately: there is no admin toggle, no plan tier, and nothing to request from support.
  • No field mapping and no pipeline picker. Pipeline and stage are resolved automatically, and a stage must exist in that deal's own pipeline.
  • Tenali never changes a record's owner, and never writes custom fields, custom objects, tickets, quotes or leads.

Related