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

Tenali for Salesforce

Tenali reads Salesforce live and writes meeting outcomes back to it. Connects via standard OAuth with the user's own login — no managed package, no admin project, no sandbox cycle.

Reads

Broader than the HubSpot side. Tenali queries Salesforce directly, so it is not confined to a fixed list of objects:

  • Reads across standard and custom objects the connected user's licence permits, with schema introspection.
  • Opportunity enumeration carries the account name on each result.
  • Nothing is synced or cached — every lookup goes to Salesforce at the moment you ask.
  • Available in web-app chat and in a Slack DM. Not in Slack channels, and not in the in-call overlay.
  • Reads work as soon as you connect; they are not gated behind write-back.

Two limits worth stating: enumeration cannot page past a 2,000-row ceiling (Tenali says so rather than silently truncating), and pipeline has no Salesforce analogue — a pipeline filter is reported as unsupported rather than ignored.

Writes

The Push to Salesforce button

On a meeting summary, updates exactly three fields on the one Opportunity you select: Description, Next Step, and Close Date (only when a date can be inferred). It replaces rather than appends. Unlike the HubSpot dialog, it cannot create records inline.

Chat write-back

  • Update an opportunity — Name, Stage, Type, Amount, Close Date, Next Step, Description. Priority is HubSpot-only and has no Salesforce equivalent.
  • Log the meeting as a completed Task with Type "Meeting", which lands in Activity History. It is not a calendar Event and not a Note — the HubSpot path creates a Note, which is a different artifact.
  • Create a follow-up task as a Task with Status "Not Started", Type "Other". No owner is set, so it lands under the connected user.
  • Add or update a contact, matched by exact email, writing Email, First Name, Last Name and Title, and linking to an Account. When creating a brand-new contact with no surname found, Tenali falls back to the email prefix because Salesforce requires a last name — it never overwrites a real surname on update. Contacts cannot be linked to an Opportunity.

Tenali cannot create Accounts or Opportunities in Salesforce by any path — agentic, dialog or API. That capability is HubSpot-only. Tenali says so rather than failing silently.

How much applies without approval

  • Additive (logging the meeting, a follow-up task, a new contact, filling an empty field) applies on its own under the default posture in the web app.
  • Forecast (stage, amount, close date, or overwriting existing text) waits on a review card showing before and after.
  • Saying "just do it" lets forecast changes through; "ask me first" gates everything.

Immovable regardless of phrasing: moving an opportunity into any closed stage (detected on the stage label), and any change where Tenali isn't confident it matched the right record.

In Slack, nothing applies automatically — every change waits on an approve-or-discard card acting on the whole batch.

Undo

Stronger on Salesforce than on HubSpot: records Tenali created are genuinely deleted, including logged meeting Tasks — where HubSpot can only mark a note reverted and complete a task.

Limits:

  • A field that was blank before Tenali filled it stays populated — undo cannot restore it to empty.
  • An update to a contact that already existed cannot be reversed; only records Tenali created are removed.
  • Covers the current conversation, your own changes, and the 25 most recent applied changes.
  • Does not cover the one-click Push to Salesforce button.

Setup and limits

  • Each person connects their own Salesforce login. Tenali acts as that user, constrained by their sharing rules and field-level security, and everything written is attributed to them.
  • One CRM at a time — Salesforce or HubSpot, never both.
  • Write-back is off by default and switched on per workspace by Tenali. Reads work immediately.
  • Salesforce write results carry no clickable record link (HubSpot's do).
  • Tenali never changes a record's owner, and never writes custom fields, custom objects, leads, quotes or cases.

Related