HubSpot
CSV workflow available Read-only connector in developmentExport a filtered Contacts view, rename the supported columns, and import a small calling list. No HubSpot account is connected to DialBreeze.
CSV and outbound webhooks
No wall of logos. Leads come in by CSV, outcomes can go out through a signed webhook your team configures, and calls use your loaded calling credit.
A CSV workflow is not a native integration. No provider account is connected, and no OAuth connection is approved or available.
CSV import and admin contact export are available today. The outbound call.disposition webhook export needs a Jetstream seat in the workspace: an admin on a Jetstream seat sets up and reads the export; delivery covers the workspace's dispositions, including Breeze callers, whenever the workspace has at least one Jetstream seat. Neither path is bidirectional contact sync, a real-time CRM mirror or automatic follow-up.
These are independent instructions for working with provider exports and webhooks. DialBreeze is not affiliated with or endorsed by these providers. Read-only connector work is in development, not released; it has no promised launch date.
Export a filtered Contacts view, rename the supported columns, and import a small calling list. No HubSpot account is connected to DialBreeze.
Use a People list-view export, not a deal report. Keep the person ID in a separate reconciliation sheet; map one phone per contact.
Prepare an eligible contact CSV with the supported DialBreeze headers. Check your export permissions in Follow Up Boss; no native connector is available.
Export contacts as CSV and review which phone belongs in the calling list. A file transfer does not carry over HighLevel automations or opportunities.
Have your Salesforce administrator prepare an authorized contact CSV and retain Salesforce record IDs outside the DialBreeze import. No Salesforce app or OAuth connection is available.
Use a contact file prepared by your CRM administrator, with one selected phone per row. CRM assignments, workflows and call history are not transferred by this contact CSV.
No dedicated DialBreeze app. A verified receiver can hand off disposition events to your Zap. Catch Raw Hook exposes body and headers, but receiving a request is not signature verification.
No dedicated DialBreeze app. Build and maintain your own scenario behind a receiver that verifies the signature. A webhook acceptance response is not proof that a CRM update succeeded.
This page explains data handoffs. Dialer alternatives and comparisons are separate evaluations, not evidence of an integration.
first_name, last_name, phone and optional email, address, city, state, zip, tags. Choose one callable phone per person and preserve the country code.See the actual list and import workflow. For a mapped example: HubSpot or Pipedrive.
An admin on a Jetstream seat sets up and reads the export, and delivery covers the workspace's dispositions, including Breeze callers, whenever the workspace has at least one Jetstream seat. That admin sets one endpoint and a shared secret in workspace settings. When an operator saves an outcome, DialBreeze POSTs the event, signs it with HMAC-SHA256 over the timestamp and body, and attempts delivery up to three times, with a five-second timeout per attempt.
X-DialBreeze-SignatureVerify the exact raw request body before parsing JSON or acting on it. A timestamp window limits stale requests but does not deduplicate retries: design duplicate detection and record downstream failures separately. A provider catch URL may acknowledge a request before later steps finish. Use a verification gateway if your automation cannot validate the raw body and headers.
import crypto from "node:crypto"; // Receiver sketch. Also deduplicate events and audit downstream results. export function verify(rawBody, timestamp, signature, secret) { if (!/^\d{10}$/.test(timestamp ?? "")) return false; if (Math.abs(Date.now() / 1000 - Number(timestamp)) > 300) return false; if (!/^sha256=[a-f0-9]{64}$/i.test(signature ?? "")) return false; const expected = crypto.createHmac("sha256", secret) .update(`${timestamp}|${rawBody}`).digest(); const given = Buffer.from(signature.slice(7), "hex"); return crypto.timingSafeEqual(given, expected); } POST https://your-endpoint.example/dialbreeze Content-Type: application/json X-DialBreeze-Event: call.disposition X-DialBreeze-Timestamp: 1790000000 X-DialBreeze-Signature: sha256=<hex HMAC of "timestamp|body"> { "event": "call.disposition", "sentAt": "2026-09-28T15:04:05.000Z", "data": { "leadId": "…", "phone": "+12025550101", "disposition": "APPOINTMENT_SET", "status": "…", "notes": "Pricing review Thursday 4 PM", "callId": "…", "durationSeconds": 290, "agentName": "Jordan Vale" } } The real lists screen with sample data: 150 fictional leads across three lists, and the CSV upload control.
Lists and importNeed a specific handoff? Email us with the workflow you need, not API keys, passwords or customer exports.
Import a small eligible CSV to check the columns before a larger file. You can check out without contacting us. For integration questions, describe the workflow only; do not email credentials. Pick your plan and seats, check out, set your password. Load calling credit and start dialing.