Snakk.ai for HubSpot — Setup Guide#
Connect Snakk.ai to HubSpot and start making AI-powered phone calls directly from your CRM. This guide covers installation, setup, and how to use Snakk.ai in both CRM cards and workflows.
Prerequisites#
A HubSpot account (any plan)
A Snakk.ai account with an active API key
At least one AI agent configured in Snakk.ai (for "Existing Agent" mode)
Step 1: Install the app#
3.
Select the HubSpot account you want to connect
4.
Review the requested permissions and click Authorize
5.
You'll see a confirmation page — the app is now installed
Step 2: Connect your API key#
Your Snakk.ai API key links your HubSpot account to your Snakk.ai agents and calling minutes.Where to find your API key#
Enter it in HubSpot#
Option A — From a contact record:1.
Open any contact in HubSpot
2.
Find the Snakk.ai card in the right sidebar
3.
Paste your API key and click Connect
Option B — From app settings:1.
In HubSpot, go to Settings → Connected Apps → Snakk.ai
2.
Paste your API key and click Connect
Your API key is encrypted with AES-256-GCM and stored securely. It is never exposed to the browser after setup.
Making calls from CRM#
Once connected, you can call contacts directly from their record in HubSpot.1.
Open a contact that has a phone number
2.
In the Snakk.ai card, select Existing Agent mode
3.
Pick an agent from the dropdown
5.
The AI agent calls the contact immediately
Using a dynamic agent#
For one-off calls with custom instructions:1.
Select Dynamic Agent mode
2.
Write the instructions for the AI agent (what to say, how to behave)
3.
Optionally set a greeting message, voice, and language
4.
Select an outbound caller ID number
5.
Click Call with Dynamic Agent
Automating calls with workflows#
Snakk.ai integrates with HubSpot Workflows so you can trigger AI calls automatically.Setting up a workflow action#
1.
In HubSpot, go to Automation → Workflows
2.
Create a new workflow or edit an existing one (must be Contact-based)
3.
Add an action and search for Make AI Call with Snakk.ai
Set Agent Mode to "Existing Agent"
Select your agent from the AI Agent dropdown
Map Phone Number to the contact's phone property
Set Agent Mode to "Dynamic Agent"
Write the Agent Instructions
Choose a Voice, Language, and optional Greeting Message
Enter the Outbound Caller ID
Map Phone Number to the contact's phone property
Workflow output fields#
The Snakk.ai action returns these values for use in subsequent workflow steps:| Field | Description |
|---|
| Call ID | Unique identifier for the call |
| Call Status | SUCCESS or FAILED |
| Error Message | Details if the call failed (empty on success) |
Example workflows#
Lead qualification: When a form is submitted → Call the contact with a qualification agent
Appointment reminders: 1 hour before a meeting → Call the contact with a reminder agent
Deal follow-up: When a deal moves to "Closed Won" → Call with a thank-you message
Re-engagement: Contact hasn't been active in 30 days → Call with a check-in agent
Managing your connection#
Switch API key#
1.
Open the Snakk.ai card on any contact, or go to Settings → Connected Apps → Snakk.ai
2.
Click Disconnect / Switch API key
3.
Enter your new key and click Connect
Disconnect#
1.
Click Disconnect / Switch API key
2.
Your stored key is permanently deleted
Troubleshooting#
| Problem | Solution |
|---|
| "No API key found" | Enter your API key in the Snakk.ai card or app settings |
| "Invalid API key" | Verify the key in your Snakk.ai dashboard under Settings → API |
| "Contact has no phone number" | Add a phone number to the contact record |
| "Missing Agent ID" | Select an agent from the dropdown |
| Agents not loading | Check that your API key is valid and you have agents configured in Snakk.ai |
| Workflow action fails | Check the error message in workflow history — common causes are missing phone number or expired API key |
Security#
API keys are encrypted with AES-256-GCM before storage
Keys are stored in encrypted form in a secure database (Upstash Redis)
Keys are never returned to the browser after initial setup
Each HubSpot portal has its own isolated key
Contact data is only used during the call session and is not stored permanently
Support#
Modified at 2026-03-20 13:24:28