Users could sometimes see 2 workflows created in the target location when loading workflows from a snapshot. This happened when duplicate workflow requests were sent at the same time, causing one workflow to remain in Processing while another completed successfully.

We've added a locks to ensure that when a workflow is loaded from a snapshot only 1 workflow is created for the same origin and location. This prevents duplicate workflows and avoids extra workflows getting stuck in Processing state.

Cal.com is the open-source scheduling stack used by individuals and teams to take bookings on their own terms. The Cal.com integration brings that scheduling layer directly into the Workflow Builder so customer-facing automations can react to booking events and the other way around. Booking lifecycle triggers and four booking actions cover the most common Cal.com use cases without webhook plumbing or third-party glue.

This means a new booking on a discovery call event type becomes a personalized welcome sequence in the same workflow that ran the form, with no manual hand-off and no relay tax.

The integration ships with two halves:

All triggers and actions are flagged as premium — premium action credits apply at the standard automation rate.

Before any Cal.com trigger or action can run, the integration has to be connected. The connection allows your workflows to securely receive Cal.com webhooks and call the Cal.com API on your behalf.

Connect via the Workflow Builder (recommended)

Connect via Settings (alternative path)

All triggers are Instant — they are powered by Cal.com webhooks and fire within seconds of the underlying event.

This walkthrough wires up a workflow that fires every time a new booking is made on Cal.com — and uses the booking payload as the source of all downstream actions.

Step 1: Add the trigger

Step 2: Configure the trigger

Step 3: Test the trigger

This walkthrough programmatically books a meeting on a host’s calendar from inside a workflow — for instance, after a high-intent form submission.

Step 1: Add the action

Step 2: Connect (first time only)

Step 3: Configure the action

Step 4: Save and use the output

​

Always test before publishing. Testing locks the payload schema and gives downstream steps a real record to map against.

Test the trigger

Test the action

Use Case 1: New Booking → CRM Contact + Welcome Sequence

Goal: Turn every new booking into a fully-onboarded contact with the right context attached.

Workflow Setup:

Example: A prospect books a 30-minute discovery call. The workflow creates a contact, tags them as ‘discovery’, sends a personalized prep email, and ensures a reminder fires the day before the call.

Use Case 2: No-Show Recovery

Goal: Auto-recover no-shows without requiring a CSM to track them down.

Workflow Setup:

Example: Whenever a meeting ends, the workflow checks the booking state. If the attendee was a no-show, they get a softening message with a one-click rebook link — instead of falling through the cracks.

Use Case 3: Cancellation Retention

Goal: Treat a cancellation as the start of a save flow, not a dead end.

Workflow Setup:

Trigger: Booking Cancelled

Example: A prospect cancels their demo because of a calendar conflict. The workflow sends a friendly reschedule message with two pre-filled time options — and tags the contact for CSM follow-up if there’s no rebook within a week.

Use Case 4: Programmatic Scheduling from a Form

Goal: Eliminate the email-back-with-a-booking-link round-trip for high-intent leads.

Workflow Setup:

Example: A lead requests a same-day call via a high-intent form. The workflow books the meeting on the assigned AE’s calendar at the requested slot and confirms it instantly — no manual scheduling, no missed lead.

Use Case 5: Recording Distribution

Goal: Get Cal Video recordings to the right place automatically.

Workflow Setup:

Trigger: Recording Ready (where supported)

Example: Right after a recording finishes processing, the attendee receives a thank-you email with the recording link and an AI-generated recap — and the CRM activity log captures the same context for the rep.

Q: What is Cal.com?

Cal.com is the open-source scheduling stack used by individuals and teams to take bookings on their own terms. It supports cloud-hosted and self-hosted deployments and exposes a rich webhook surface for automation.

Q: Are Cal.com actions premium workflow actions?

Yes. All four actions are flagged as premium and consume premium action credits at the standard automation rate.

Q: How fast do triggers fire?

Cal.com sends webhooks typically within 1–3 seconds of the booking event. Workflows enroll as soon as the webhook arrives.

Q: What does the trigger payload include?

Each booking event delivers the full booking object — bookerUrl, title, startTime, endTime, additionalNotes, type, description, eventTypeId, hideCalendarNotes, attendees and organizer. Use Find New Records and Records — Select Mapping Reference to lock the schema.

Q: What does the Webhook Status indicator mean?

It reflects the live status of the underlying Cal.com webhook. ‘Active’ means events are flowing; if it goes inactive, the webhook needs reconnection in your Cal.com settings.

Q: How do I supply a timezone in Create Booking?

The Attendee Timezone field accepts IANA format strings such as America/New_York or Europe/London. If left empty, Cal.com falls back to the sub-account timezone.

Q: What format should I use for Start Time?

A standard date-time value. The suggested format is ‘12-21-2026 08:30 AM’; ISO-8601 strings (e.g. 2026-12-21T08:30:00) are also accepted. The interpreted timezone is the Attendee Timezone (or sub-account default if unset).

Q: Does Cancel Booking notify the attendee?

Yes. Cal.com sends its standard cancellation email, including the cancellation reason if supplied.

Q: Will Reschedule Booking re-issue calendar invites?

Yes. Cal.com cancels the original calendar event and sends an updated invite for the new time. Confirmation emails fire automatically.

Q: What happens to Meeting Ended when a booking is rescheduled?

Cal.com cancels the pending Meeting Ended webhook for the original time and re-schedules it for the new time. The trigger fires once, at the booking’s actual end.

Q: Will the workflow fire twice if a booking is rescheduled?

No. Booking Rescheduled is its own trigger; Booking Created does not re-fire on reschedule. Use the right trigger for the lifecycle event you care about.

Q: Does the integration work on self-hosted Cal.com?

Self-hosted Cal.com supports the same webhook surface, so triggers work the same way once the webhook URL is configured. Some self-hosted setups have known issues with Meeting Started / Meeting Ended — verify with a real test booking before production use.

Q: Can I use workflow variables in action fields?

Yes. Inline variables work in Attendee Name, Attendee Email, Start Time and any other field exposed by the action.

Q: What if the booking I am trying to cancel no longer exists?

Cancel Booking surfaces the error to the workflow execution log, and the workflow continues based on its branching. Use Find Booking as a guard step if downstream logic depends on the cancellation succeeding.

Q: Are these actions production-ready?

All triggers and actions are released as Beta. They are safe to use in live workflows; expect incremental UX changes — additional filters, additional fields — as the integration moves out of Beta.

We want to keep you informed about upcoming changes that may impact your messaging and calling costs inside HighLevel.

Due to recent pricing updates from our underlying carrier partner, rates for certain SMS and Voice routes will increase .

Costa Rica: $0.0874 → $0.1017

Grenada: $0.2462 → $0.2913

Kenya: $0.2336 → $0.2923

Namibia: $0.1041 → $0.1167

Zimbabwe: $0.2481 → $0.3177

Austria (Local & Mobile): $0.0100 → $0.0107

Belgium (Mobile): $0.0100 → $0.0113

Chile (Local): $0.0100 → $0.0107

Croatia (Local): $0.0100 → $0.0107

Czech Republic (Local): $0.0100 → $0.0107

Denmark (Mobile): $0.0100 → $0.0107

Finland (Mobile): $0.0100 → $0.0107

Israel (Local): $0.0100 → $0.0107

Luxembourg (Local): $0.0100 → $0.0107

Malaysia (Local): $0.0288 → $0.0318

Poland (Mobile): $0.0100 → $0.0107

Portugal (Mobile): $0.0100 → $0.0107

South Africa (Local & Mobile): $0.0100 → $0.0107

Sweden (Local): $0.0100 → $0.0107

United Kingdom (Toll-Free Local & Mobile): $0.0664 → $0.0798

Afghanistan (Mobile): $0.4150 → $0.4287

American Samoa: $0.4090 → $0.4576

Austria (Mobile): $0.2640 → $0.2730

Bermuda: $0.0529 → $0.0588

Chile: $0.0428 → $0.0475

Chile (Mobile): $0.0670 → $0.0746

Cyprus (Mobile): $0.1500 → $0.1675

Denmark: $0.0219 → $0.0240

Denmark (Mobile): $0.0508 → $0.0564

Egypt (Mobile): $0.1870 → $0.2090

Estonia (Mobile): $0.4783 → $0.5709

Estonia (Other): $0.4650 → $0.4944

Finland (Mobile): $0.4950 → $0.5172

Finland (Other - EEA): $0.1168 → $0.3037

Germany: $0.0210 → $0.0283

Greece (Mobile - EEA): $0.0696 → $0.0746

Guam: $0.0530 → $0.0589

Haiti (Mobile): $0.7858 → $0.8796

Hong Kong (Mobile): $0.0492 → $0.0546

India: $0.0497 → $0.0699

India (Mobile): $0.0405 → $0.0496

Indonesia: $0.0966 → $0.1077

Ireland: $0.0168 → $0.0483

Israel (From IL): $0.0267 → $0.0294

Luxembourg: $0.2530 → $0.2829

Moldova: $0.4420 → $0.4946

Morocco: $0.4743 → $0.5307

Namibia (Mobile): $0.1650 → $0.1843

Nicaragua (Mobile): $0.4200 → $0.4767

Peru: $0.0552 → $0.1651

Slovakia (Mobile): $0.1038 → $0.1158

South Africa (Mobile - Twilio ZA): $0.0450 → $0.0499

Spain (Mobile - EEA): $0.0388 → $0.0486

St. Lucia (Mobile): $0.5040 → $0.7158

Sweden (Mobile): $0.0642 → $0.0714

Switzerland: $0.0374 → $0.0419

Switzerland (Mobile): $0.2361 → $0.2516

United Kingdom (Personal): $0.4725 → $0.5577

US Virgin Islands: $0.0414 → $0.0459

These updates reflect changes from downstream carrier partners and telecom infrastructure providers to support:

Linear is the issue tracker engineering and product teams use to plan, ship and report on work. The Linear integration brings Linear directly into the Workflow Builder so customer support, sales and marketing automations can react to engineering events — and the other way around. Twelve instant triggers and thirteen actions cover the full Linear data model: issues, projects, customers, customer needs, initiatives and documents.

This means a customer-reported bug becomes a properly tagged Linear issue with full context attached — and the same customer gets notified the moment the issue ships. No webhook plumbing, no Zapier hand-off, no third-party glue.

The integration ships with two halves:

Every trigger and action is flagged as a premium workflow component — premium action credits apply at the standard automation rate.

​

Before any Linear trigger or action can run, the integration has to be connected. The connection allows your workflows to securely read from and write to your Linear workspace.

Connect via the Workflow Builder (recommended)

Connect via Settings (alternative path)

All triggers are Instant — they are powered by Linear webhooks and fire within seconds of the underlying change.

This walkthrough wires up a workflow that fires every time a new issue is created in a specific Linear team — for instance, your customer-facing engineering team — and uses the issue payload as the source of all downstream actions.

Step 1: Add the trigger

Step 2: Configure the trigger

Step 3: Test the trigger

This walkthrough turns an inbound customer form into a properly contextualized Linear issue.

Step 1: Add the action

Step 2: Connect (first time only)

Step 3: Configure the action

Step 4: Save and chain

Click Save Action. The new issue’s ID and URL are exposed as workflow output variables. Chain a Create Issue Attachment step right after to attach the CRM contact URL — this gives engineers a one-click path back to the customer context inside Linear.

Always test before publishing. Testing locks the payload schema and gives downstream steps a real record to map against.

Test the trigger

Test the action

Use Case 1: Customer-Reported Bug → Linear Issue with Context

Goal: Capture every customer-reported bug as a properly tagged, attributed Linear issue.

Workflow Setup:

Example: A user submits a bug report on the support form. The workflow finds the matching Linear customer, creates a tagged issue with the conversation context, attaches the CRM contact URL, and logs a customer need against the customer record so product can prioritize by revenue.

Use Case 2: Linear Issue Resolved → Notify the Customer

Goal: Auto-notify the original reporter the moment their bug ships.

Workflow Setup:

Example: When engineering closes a bug that originally came from a customer, the workflow detects the status change, summarizes the fix in plain language, and emails the reporter without requiring a CSM in the loop.

Use Case 3: Engineering Project Update → Customer Comms

Goal: Convert engineering project updates into customer-ready release notes or stakeholder digests.

Workflow Setup:

Example: A weekly project update posted by engineering becomes a softened, customer-facing status snippet on the corresponding opportunity record — no double-work for the project lead.

Use Case 4: CRM ↔ Linear Customer Sync

Goal: Keep customer records in lockstep across both systems so revenue-weighted prioritization actually works.

Workflow Setup:

Example: Whenever a deal closes in the CRM, the company appears as a Linear customer with the right tier and revenue tag — making every customer need that comes in afterwards automatically prioritizable.

Use Case 5: Sales Conversation → Customer Need

Goal: Turn AE call insights into structured product feedback without manual logging.

Workflow Setup:

Example: After a sales call, an AI step pulls every concrete request out of the transcript. Each becomes a customer need on the right Linear customer — product gets a clean, attributed list to triage, instead of free-text notes scattered across the CRM.

Always set the Team filter on triggers — Linear workspaces typically span many teams, and unfiltered triggers will fire for unrelated activity.

Q: What is Linear?

Linear is a modern issue tracker used by engineering and product teams to plan and ship work. It models issues, projects, customers, customer needs (feature requests) and initiatives.

Q: Which Linear plan do I need?

Most triggers and actions work on Linear’s standard plans. The Customer and Customer Need entities require Linear’s Customer Requests feature, which is gated behind specific Linear plan tiers — check Linear’s pricing for current details.

Q: Are Linear actions premium workflow actions?

Yes. All Linear triggers and actions are flagged as premium and consume premium action credits at the standard automation rate.

Q: Are these triggers Instant or polled?

All twelve triggers are Instant. They are powered by Linear webhooks, so the workflow fires within seconds of the change.

Q: Can I filter triggers by team?

Yes. Triggers like New Issue, Updated Issue and New Issue Comment expose a Team filter. Add more granular filters with the Add filters control.

Q: Does Update Issue overwrite fields I do not set?

No. Update Issue is a partial-update action — only fields you explicitly set are sent. Unrelated values stay as they are in Linear.

Q: Can I use workflow variables in action fields?

Yes. Inline variables work in title, description, labels, priority, project and assignee fields, and resolve per execution.

Q: What happens if the issue I am trying to update no longer exists?

The action surfaces an error to the workflow execution log, and the workflow continues based on its branching. Add a fallback branch if downstream steps depend on the update succeeding.

Q: How do I attach a CRM record URL to a Linear issue?

Chain Create Issue → Create Issue Attachment, passing the issue ID from the first step. The attached URL becomes a two-way linked attachment inside Linear.

Q: Can the workflow create a Linear customer if one does not exist?

Yes. Use Find Customer first; if the lookup returns nothing, branch to Create Customer, then proceed to Create Customer Need.

Q: Can I disconnect Linear without breaking my workflows?

Disconnecting will pause every workflow that depends on Linear triggers or actions. The workflows themselves remain intact and resume as soon as the integration is reconnected.

Q: Are these actions production-ready?

All triggers and actions are released as Beta. They are safe to use in live workflows; expect incremental UX changes — additional filters, additional fields — as the integration moves out of Beta.

We've made the Chat Widget compliance check smarter — it now detects upfront when the Lead Connector chat widget isn't live on a user's website and prompts them to fix it before submitting.

Deleting a blog post no longer removes it permanently, Restore Blog Post brings the post back with its original content and status, For long-term cleanup, users can choose Delete Forever from the Deleted filter.

Updated Behaviour:

A dedicated “Deleted” filter now lets users:

This update helps users:

Delete a Post

Visual Edits is a new in-canvas editing mode that lets you change how your site looks - colors, fonts, spacing, images, icons, and more directly by clicking on any element in the live preview. No need to describe what you want to AI; just point and adjust.

Visual edits are applied instantly without any LLM calls, so changes are near-instant and don't consume any of your token usage.

Click any element in the preview to open the Visual Edits panel. Controls adapt to what you selected — text, button, image, icon, or layout element.

Double-click any text element to edit it directly in the preview. Press Escape or click outside when done.

Click any Lucide icon to open a searchable library of 1,600+ icons. Pick one and it swaps instantly, no reload needed.

Your project's theme colors appear alongside the full Tailwind palette. Click a swatch to apply.

Margin and padding side by side, with a toggle to link or unlink all four sides.

Select an image to get a Layout dropdown: Fill, Contain, Cover, or Scale down.

Select a Lucide icon to resize width and height, snaps to Tailwind classes or accepts custom values.

Select multiple elements at once and describe what you want changed across all of them in a single prompt. Great for applying consistent styling or making coordinated updates across several components.

Color swaps, spacing tweaks, icon changes, inline text edits — none of these hit the AI. Changes apply instantly and don't count against your token usage. LLM is only invoked when you explicitly send a prompt.

Changes are previewed live. Hit Save to apply to your code, or Discard to throw them away.

More coming soon!

We have enhanced the App Approval experience to make Marketplace app management faster, simpler, and more accessible for agencies.

Previously, users had to navigate from All Apps to Approved/Dis-approved Apps to manage approvals. With this update, approval management is now surfaced upfront with dedicated Approved/Disapproved views and new auto-approve controls.

Go to: App Marketplace → Settings → Manage App Permissions

From there, you can:

We’re bringing even more platforms into one unified inbox. ✨

With this update, Comment Management now supports Bluesky, allowing you to view and reply to comments directly from Social Planner.

No more switching tools,manage Bluesky conversations alongside your other social channels in one place.

:

The Schema Markup module now supports 7 additional schema types in the manual creation flow — bringing total parent-level support from 12 to 19. Users will find these new types in the "Add Schema Markup" or "Edit Schema Markup" popup alongside existing ones. Select a type, fill in the fields via Form view or JSON view, and hit Validate & Save. No workflow changes required.

: Offer · Review · Aggregate Rating · Recipe · ImageObject · Service · Course

This applies to the manual flow only. The AI-assisted flow already supports all Schema.org types.

: Websites & Funnel Pages

Existing schema markups are unaffected. New types simply appear as additional dropdown options.