Connects to the tools your team already runs on
Actualcast plugs into HubSpot, your calendar, and your meeting platform. It reads your deals, records external calls on Zoom, Google Meet, and Teams, and writes back only the facts a rep has confirmed. Every connection uses the narrowest permissions that do the job, and every token is encrypted at rest.
How connecting works
Setup takes a few minutes and happens once. You sign in, authorize HubSpot and your meeting platform, and pick which calendars Actualcast watches. There is nothing to install on a rep's laptop and no browser extension to roll out. From then on, the bot joins the calls you have chosen and the updates land in the review queue.
Sign in with Google
Each person on your team signs in with their Google account. There is no separate password to set, store, or reset.
Authorize HubSpot
An admin connects HubSpot through its standard OAuth screen. You approve a short list of permissions and can disconnect at any time, either from HubSpot or from Actualcast.
Connect your meeting platform
Link Zoom, Google Meet, or Teams so the bot can join and record. Connect one or all three, depending on where your calls happen.
Choose which calendars to watch
Point Actualcast at the calendars whose external meetings you want recorded. Internal-only calendars stay untouched.
Reads your deals, writes only what a rep confirmed
HubSpot is where your pipeline lives, so it is where Actualcast reads from and writes to. It reads your open deals to build the review queue and the deal inspection view. It writes nothing on its own: only the facts a rep has confirmed are sent back, and they land in the places your team already looks.
Reads open deals and their fields
Actualcast pulls deal names, stages, amounts, close dates, owners, and associated contacts, so it can match calls to deals and flag hygiene problems.
Writes a note with the quote
Each confirmed fact becomes a HubSpot note that includes the exact transcript quote and its timestamp, so anyone reading the deal can see where the update came from.
Creates a task for the next step
When a call sets up a next step, Actualcast writes it as a task on the deal so it does not get lost between reviews.
Updates close date and amount
Confirmed changes to close date and amount are written to the deal properties, so the pipeline review runs on current numbers.
Runs on the narrowest scopes
The HubSpot connection asks only for the permissions it needs to read deals and write these updates. It does not touch anything else in your portal.
Recording that joins the calls that matter
A bot joins your external meetings, records them, and hands back a transcript with speaker turns and timestamps. It works the same way across Zoom, Google Meet, and Teams, so it does not matter which one a given call uses. Recording is on for external meetings by default, and every meeting has an off switch.
Works across all three platforms
The bot joins Zoom, Google Meet, and Teams calls and records them the same way, through Recall.ai. Your reps do not change how they run a call.
External by default
By default the bot joins meetings that include people outside your company, the calls where deal facts come up. Internal meetings are left alone.
A per-meeting off switch
Any meeting can be excluded before it starts, so a sensitive or personal call is never recorded. The default is easy to override, one meeting at a time.
Transcribed with speaker turns and timestamps
Every call becomes a transcript that labels who said what and when. That is what lets each extracted fact carry the exact quote behind it.
Sign in with Google, connect your calendar
Your team signs in with Google, so there is no new password to create or reset. The same connection lets Actualcast read your calendar to know which external meetings are coming up and which deal each one belongs to.
One sign-in for the whole team
Everyone uses their existing Google account. Removing someone's access is as simple as removing them in your Google admin.
Calendar read for scheduling the bot
Actualcast reads event times, titles, and attendees so the bot knows when to join and which meetings are external.
You choose the calendars
Only the calendars you connect are watched, and you can change or remove them whenever you want.
How your connections are protected
Every connection is built to hold the least access it can and to keep your call content out of places it does not belong. The rules below are enforced in the code, not just described on this page.
Least access, always
Each integration requests the narrowest set of permissions that lets it do its job, and nothing more.
Tokens encrypted at rest
The OAuth tokens for HubSpot, Google, and your meeting platform are encrypted at rest with AES-256-GCM. They are decrypted only at the point of use, when Actualcast reads your deals or sends a confirmed write, and never written to a log.
Transcript content stays out of logs
What was said on your calls never appears in application logs.
An audit row for every write
Every write to HubSpot creates an audit log entry, so there is a record of what was written, from which fact, and when.
Audio deleted on a schedule
Recordings are deleted after a retention window that defaults to 180 days, and you can ask for an organization's recordings and transcripts to be deleted at any time.
Disconnect whenever you want
You can revoke any connection from Actualcast or from the provider, and confirmed data already in HubSpot stays where it is.
Connect your stack, keep your CRM current
Request early access. Setup is a few minutes, once, and every connection runs on the narrowest permissions with encrypted tokens.