Hyper AI integrates with Salesforce to sync every demo to your CRM automatically. When a demo ends, the prospect is matched by email to an existing Contact or Lead, or added as a new Lead, and the demo is logged as a completed activity on their record. You can send each qualification answer to any Lead field you choose.
Hyper AI connects through OAuth 2.0 (with PKCE). It never sees or stores your Salesforce password. You will be asked to allow these scopes when connecting your org.
Hyper AI acts as the Salesforce user who connected the integration, with that user's permissions.
Once connected, the integration runs automatically with no manual steps required. Here's the full data flow:
A Salesforce admin installs the Hyper AI app and connects it from the Integrations page in Hyper AI. There are no API keys to copy.
When a demo ends, Hyper AI looks up the prospect's email:
Map each qualification question to any writable Lead field, including custom fields. Answers are converted to the field's type, and picklist answers are matched by label or value.
Each demo is added as a completed Task, “Hyper AI demo with [agent name]”, dated on the day of the demo. It includes the summary, lead score, qualification answers, suggested next steps, and links to the recording, transcript and audio.
New Leads show up in your Lead views and reports, and the demo appears on the record's activity timeline. Your team doesn't have to export or re-enter anything.
Webinars work the same way. Registrations and attendance are logged as activities on the registrant's Contact or Lead, and a Lead is created if the registrant isn't in Salesforce yet.
Prospect details go to the standard Lead fields, each qualification answer goes to the Lead field you pick, and the demo itself is logged as a Task.
FirstName / LastNameA single name goes to Last Name. If there's no name, the part of the email before the @ is used.
EmailThe key used to match records.
CompanyRequired by Salesforce. If the prospect didn't give one, Hyper AI sends “Not provided”.
Phone
Title
For an existing Contact, the mapped answers go to the Contact field with the same API name, or failing that, the same label. This usually matches how your org maps Lead fields on conversion.
If Salesforce rejects a mapped value, for example because of a validation rule or a value that isn't in a restricted picklist, Hyper AI saves the record without that field instead of losing the whole sync.
Before you start
In Hyper AI, go to Integrations and click Connect next to Salesforce.
Log in to Salesforce as the user Hyper AI should act as, and click Allow. This user needs to be able to create and edit Leads, edit Contacts and create Tasks.
You're sent back to Hyper AI, and the card shows Connected as [your org name]. From now on, every demo syncs automatically.
Go to Advanced → Qualification Questions.
Under each question, click the Salesforce field chip next to CRM fields and pick the Lead field where the answer should go.
Fields you add in Salesforce later appear after you click Refresh fields in the picker.
email is the matching key. Your org's own rules can also block the record, for example a blocking duplicate rule, or a required custom Lead field with no default value. Duplicate rules that only show an alert don't stop the sync. If you can't tell why, contact us and we'll check the sync result for that demo.