Changelog
Follow up on the latest improvements and updates.
RSS
new
Ad Manager
LinkedIn ad campaign templates via Template Library
👀 What’s New?
- Users can now create LinkedIn campaigns using templatesdirectly inside Ad Manager.
- Ability to upload existing LinkedIn campaigns as templatesto the Template Library.
- LinkedIn campaigns are now included under the Ad Manager tab in Template Libraryalongside Google and Meta.
- Objective-based filteringnow also supports LinkedIn campaign objectives for better template discovery.
👷 How It Works:
- LinkedIn Support in Template Library
- Navigate to Template Library (Agency View) > Ad Manager Tab.
- All templates (default, agency-created, shared) now include LinkedIn campaign templates.
- The “Objectives” filterdynamically reflects LinkedIn-supported objectives (e.g., Lead Generation, Website Visits).

- Create LinkedIn Campaigns Using Templates
- In Ad Manager, click on“Create Campaign” dropdown.
- Select “Ad Manager Templates”.
- Browse and select a LinkedIn template.
- Previewtemplate details > ClickContinue.
- A new LinkedIn campaign is created with pre-filled configurations(targeting, creatives, budget, etc.).

- Upload LinkedIn Campaigns as Templates
- From the campaign listing page, select an existing LinkedIn campaign.
- Click on ellipsis (⋮) > “Upload to Template Library”.
- Add Template Name + Category.
- Click Upload> Template issaved as Draft.
- Users can edit, save, or publishthe template for reuse across accounts.

🌟 Why It Matters:
- Cross-Platform Consistency– Extends template-based workflow to LinkedIn, making Ad Manager truly multi-platform.
- Faster Campaign Launches– Reduces manual effort by reusing proven LinkedIn campaign structures.
- Scalable for Agencies– Enables easy sharing of high-performing LinkedIn strategies across locations.
- Improved Efficiency– Eliminates repetitive setup and accelerates campaign deployment.
📝 Notes:
- Templates now support Google, Meta, and LinkedIn campaignswithin a unified experience.
- Objective filters will continue to expand as more LinkedIn objectives are supported.
- Existing Template Library workflows remain unchanged for backward compatibility.
improved
fixed
Conversations
Conversations: Marketplace App Source Now Visible in Messages
Overview:
You can now easily identify which Marketplace App sent a message in Conversations, directly from the message details.
👀
What’s New?
- Previously, there was no clear way to know which app sent a message. This often led to confusion and made troubleshooting difficult. With this update, you get complete transparency into message origin, making it easier to debug issues, manage integrations, and stay in control.
- Messages sent via Marketplace Apps or custom providers now display the App name and App ID
- Open any conversation, click on a message to view its details, If the message was sent via an OAuth-connected Marketplace App, you’ll see the app’s name and ID.

new
Email System
Conversations
Improved Email Failure Experience in Conversations
We’ve made updates to help you better understand and troubleshoot failed email messages—without interrupting your workflow.
What’s new
- Failed emails now display clearer, user-friendly error messages
- Error links open in a new tab so you can review details without losing your place
Why this matters
- Quickly understand why an email didn’t send
- Prevents disruption by opening error details in a new tab—so you don’t lose your current view or context
These improvements are designed to make debugging faster and your workflow smoother.

improved
Snapshot
Personalised Snapshot Imports & Enhanced UI
We’ve revamped the snapshot import experience to make it faster, clearer, and more intuitive—giving you greater control right from the start.
What’s New
- Custom Snapshot Naming:Rename snapshots during import instead of relying on default names.
- Improved Error Messaging:Get clear, actionable messages for issues like expired or invalid share links.
- Real-Time Import Status:Imported snapshots now appear instantly in your list with a “greyed out” state while processing, and automatically become active once complete.
- Asset Protection Indicator:A new shield icon highlights asset-protected snapshots for quick identification.
- Enhanced UI & Performance:Cleaner design with a smoother, faster overall experience.



Benefits
- Better Organization:Name and manage snapshots your way from day one.
- Clear Guidance:Quickly understand and resolve import issues.
- Faster Onboarding:Seamless flow from import to usage with improved visibility.
Try importing a snapshot using a share link to explore the new flow and custom naming experience.
new
Snapshot
Chat Widget
Chat Widget – Snapshot Support
🚀 Summary:
Chat Widget configurations can now be included in Snapshots, allowing agencies to replicate widget setups across sub-accounts with proper handling of account-specific dependencies like WhatsApp numbers, Voice AI agents, and integrations.
✨ What's New?
- Chat Widget support in Snapshots
- Replicate chat widgets (Email/SMS, Live Chat, WhatsApp, Facebook, Instagram, Voice AI, All-in-One) across sub-accounts.
- Smart dependency handling
- WhatsApp numbers: mapped if available, else left empty
- Voice AI agents: auto-selected if available in target account
- Media assets: migrated dynamically
- Location-level fields (locale, country, agency details): auto-mapped
- Graceful fallback behaviour
- Widgets are created even if dependencies (WhatsApp, FB/IG, Voice AI) are missing
- Fallback state shown (e.g., widget unavailable)
- Save / Get Code actions disabled when required setup is incomplete
- Helper tooltips guide users
- Controlled custom field behaviour
- Custom fields are not auto-created during snapshot load
- Users must explicitly include them to avoid conflicts
🛠 How to Use?
- Go to Account Snapshots (Agency View)
- Create a snapshot from a source sub-account
- Include Chat Widget in snapshot assets

- Load the snapshot into a target sub-account

- Open Sites > Chat Widgets in the target sub-account, you'll see the source sub-account widgets present
- Complete any missing integrations (if required) and use it on any digital property
🌟 Why This Feature?
- Reduces onboarding time for agencies.
- Enables reuse of chat widget configurations across accounts.
- Maintains consistency in communication setup.
- Handles account-specific dependencies safely without breaking setup.
📝 Notes:
- Widgets may require manual setup if dependencies are missing.
- WhatsApp numbers, FB/IG connections, and Voice AI agents are account-specific.
- Snapshot load does not guarantee publish-ready state without required integrations.
new
E-Commerce Stores
Custom Product Details Pages Now Inherit Your Default Design
What’s New?
Creating a Custom Product Details Page (PDP) is now faster and more intuitive.
Earlier, enabling the “Create Custom Product Details Page” option would generate a blank page—forcing users to rebuild the layout from scratch.
With this update, new Custom PDPs automatically inherit the design of the existing Default Product Details Page, allowing users to start from a fully structured, production-ready layout.
- Auto-Inherited PDP Design
- Custom PDPs now copy the Default PDP layout during creation.
- Users land directly in the builder with a ready-to-edit page.
- Full Design Duplication- The following are inherited:
- Section structure & layout
- Store elements (media, title, price, variants, CTA, etc.)
- Styling (fonts, colors, spacing, borders, shadows)
- Visibility rules (desktop/mobile)
- Independent & Editable
- Custom PDPs remain fully editable and independent.
- Changes to the Default PDP do not impact existing Custom PDPs.
- Multi-Product Support
- One Custom PDP can be assigned to multiple products.
- Same inherited design applies across all selected products.
- ClickFunnels Priority Behavior
- When working within ClickFunnels flows, the “Create Custom Product Details Page” option will be hidden.
- This ensures a simplified and consistent funnel-first experience.
How to Use It?
- Go to Store Builder and create a new page.
- Enable “Create Custom Product Details Page.” (Not available in ClickFunnels flows)
- Select product(s) to assign.
- A Custom PDP will be created with inherited design.
- Customize and publish.
Key Points to Note:
- Default PDP remains unchanged after Custom PDP creation.
- Inheritance is a one-time copy (no live sync).
- Existing Custom PDPs are unaffected.
- No more blank Custom PDPs—start with a complete layout.
- Fully supported in builder preview (desktop & mobile).
Images:



Overview:
Building stable, future-proof integrations just got easier. We’ve introduced API Versioning for our public documentation, enabling developers to reliably access and work with specific API versions without worrying about unexpected breaking changes.
What’s New
- Versioned API Documentation: Each API version now has dedicated documentation for precise reference
- Version Switcher: Easily toggle between API versions directly within the documentation
- Backward Compatibility: Older API versions remain accessible and fully documented
Why This Matters
- Enables predictable and stable integrations without breaking changes
- Provides smoother upgrade paths to newer API versions
- Improves developer experience with clear, version-specific references
- Builds confidence for teams managing long-running production systems
Key Highlights
- No impact on existing integrations
- Simplifies API adoption and version migration
- Lays the foundation for structured API evolution and deprecation
- Enhances transparency through version-level visibility
Impact
- Improved reliability and stability for API consumers
- Reduced risk of integration failures during updates
- Faster development and debugging with clear documentation
- Stronger developer ecosystem and long-term scalability
How to Use
Open API documentation → Select the desired version from the version switcher → Reference endpoints and schemas for that version → Build with confidence
Next Step
We are working on the next milestone — v3 of our APIs, which will introduce enhanced capabilities, improved performance, and new endpoints for advanced use cases.
Preview
Select version by switching via toggle at top of the API documentation:

Nudge highlighting user that they are in older version:

new
App Marketplace
Conversation AI
Voice AI
Marketplace App Update: AI Agent Modules Now Support App Versioning
Overview
We’ve expanded app update versioning to include AI Agent modules, including Conversation AI and Voice AI templates.
Earlier, app versioning supported the release flow for app updates, but AI Agent module changes were not fully tied to app versions. With this update, AI Agent template changes are now version-controlled, making releases safer, clearer, and easier to manage.
What’s new
- AI Agent template changes must now be made through the app versioning flow.
- Developers can no longer edit AI Agent templates directly on a Live version.
- To make changes, developers should go to Manage → Versions, clone the Live version as a Draft, make updates in the Draft, and publish the new version.
Versioning behavior
- Updates to an existing Conversation AI or Voice AI template are treated as a Minor version update by default.
- This includes changes to agent details, descriptions, use cases, supported channels, actions, template configuration, template link updates, or disabling/enabling an existing template link.
- A Major version is required when AI Agent templates are added for the first time to an existing Live app.
- For example, if a Live app did not previously include Conversation AI or Voice AI templates, and the developer adds one or both in a Draft version, the update must be published as a Major version.
Why this matters
This update gives developers better control over how AI Agent changes are released and gives users more visibility into what changed before updating an installed app.
AI Agent updates are now easier to track, review, and adopt through Marketplace release notes and version updates.
What' next
- We are in the process of expanding app versioning to other Marketplace modules as well.
In case of any further questions, please reach out to marketplace@gohighlevel.com
new
Automations
Mistral AI: Workflow Actions
Overview
AI is most useful when it sits inside the rest of your automation, not as a separate manual step. The Mistral AI integration lets your workflows call Mistral language models, generate embeddings for semantic search, and analyze images — using your own Mistral API key, with the response available as a workflow variable for any later step.
This means workflows can reply to a customer in their own language, look up the closest match in a knowledge base, or pull structured data out of an uploaded receipt — without sending the contact off to a third-party tool.
About the Integration
Mistral AI is a French AI lab that builds open-weight and frontier language models. The integration ships three actions:
- Create Chat Completion — text generation across the Mistral Large, Medium, Small, Ministral and Magistral families.
- Create Embeddings — turn any text into a 1024-dimension vector for semantic search, classification or clustering.
- Analyze Image (Vision) — send an image plus a prompt to a vision-capable Mistral model and receive a structured natural-language answer.
All three actions are premium actions
Key Benefits of Mistral AI in Workflows
- Strong multilingual coverage — Mistral models are trained natively on 40+ languages, with particular strength in European languages. Useful when your contact list is not English-first.
- Native image understanding — receipts, IDs, charts, screenshots and product photos can be read inside a workflow without integrating a separate OCR vendor.
- Reasoning models on demand — for multi-step logic problems, choose Magistral and let the model think through the steps before answering.
How to Set Up Mistral AI
Before any Mistral AI action can run, the integration has to be connected. The connection allows your workflows to securely call Mistral using your API key.
Connect via the Workflow Builder (recommended)
- Open Automation → Workflows and pick (or create) a workflow.
- In the builder, click Add to insert a new step.
- Open the Apps tab and search for Mistral AI.
- Select any Mistral AI action — Create Chat Completion, Create Embeddings, or Analyze Image.
- Click Connect Now on the action card.
- Paste your Mistral API key. To generate one: log in to console.mistral.ai, open API Keys, click Create new key, give it a recognizable name, then copy the key.
- Click Save to complete the connection.
Connect via Settings (alternative path)
- Go to Settings → Integrations.
- Locate Mistral AI in the integrations list and click Connect.
- Paste your Mistral API key and click Save.


List of Actions
- Create Chat Completion - Send a prompt (and optional system prompt) to a Mistral language model and receive a generated text response.
- Create Embeddings - Convert input text into a 1024-dimension vector for semantic search, RAG, classification or clustering.
- Analyze Image (Vision) - Send an image URL and a prompt to a vision-capable Mistral model and receive a natural-language answer about the image.

List of Triggers
There are no Mistral AI triggers in this iteration. Mistral AI is currently action-only — workflows can call Mistral models from any step, but cannot be initiated by a Mistral event. Trigger support may be added in a later release.
Example: Setting Up an Action (Create Chat Completion)
This walkthrough creates an automated multilingual reply. The workflow listens for an inbound message, asks Mistral to draft a friendly response in the contact’s language, and sends it back over email.
Step 1: Add the action
Open or create a workflow. Click Add to insert a step.
- In the right panel, switch to the Apps tab.
- Find Mistral AI and click to expand its actions.
- Choose Create Chat Completion.
Step 2: Configure the action
- The configuration panel exposes the standard prompt + model fields:
- Action Name — Give the step a meaningful label such as ‘Draft Multilingual Reply’.
- System Prompt (optional) — Lock down the AI’s persona. Example: ‘You are a friendly support agent. Always reply in the contact’s preferred language. Keep responses under 80 words.’
- Prompt (required) — Provide the actual instruction with workflow variables inline. Example: ‘Reply to this message from {{contact.first_name}}: {{trigger.message_body}}. Their preferred language is {{contact.language}}.’
- Model (required) — Select a Mistral model. Use Mistral Large for highest-quality multilingual output; switch to Mistral Small or Ministral for faster, cheaper runs.
- Optional tuning — Adjust temperature for creativity, max tokens for length, and other supported parameters as exposed by the action.
Step 3: Save and use the output
- Click Save Action. The generated response is exposed as a workflow output variable that can be inserted into a Send Email step, written to a custom field, or evaluated by a conditional.
Example: Setting Up Analyze Image (Vision)
This example pulls structured data out of an uploaded receipt and writes it to the contact record.
- Add a step and select the Analyze Image (Vision) action under Mistral AI.
- Set the Action Name to ‘Parse Receipt Image’.
- In the Image URL field, insert the workflow variable that holds the uploaded image — for example, the file URL from a Form Submission step or a Media Storage entry.
- Set the System Prompt to: ‘You are a receipt parser. Always respond with valid JSON only.’
- Set the Prompt to: ‘Extract vendor_name, total_amount, currency and purchase_date from this receipt. Return a JSON object with exactly those four keys.’
- Choose a vision-capable model from the dropdown.
- Run Test Action with a sample receipt URL to confirm the JSON shape, then save.
- In subsequent steps, parse the JSON output and use the parsed values to update contact custom fields, create an Opportunity, or send an internal Slack notification.
Common Use Cases
- Multilingual customer reply generation
Inbound message → Mistral AI Create Chat Completion → Send Email/SMS
- Trigger when a contact replies in any supported language (native French, English, Spanish, German, Italian, Portuguese, with broad coverage of Dutch, Japanese, Korean, Chinese, Arabic, and more)
- Use Mistral Large for high-quality, native multilingual responses
- Maintain brand tone via the System Prompt and personalize using contact variables
2. Semantic FAQ matching for inbound questions
Inbound email/customer replied → Create Embeddings → Vector lookup → Send templated reply
- Embed the inbound question and compare against pre-embedded FAQ entries to reply with the closest match
- Handles paraphrased questions out of the box without brittle keyword matching
- Use the same embedding action one time as a setup step to index your FAQ content
3. Receipt and document extraction from images
Inbound webhook -> Image upload (form / inbound MMS) → Analyze Image (Vision) → Update contact Create opportunity
- Send a receipt, ID, or photo to Pixtral Large with a structured prompt (e.g. "return JSON with vendor, date, total")
- Auto-populate custom fields without manual data entry
- Works for damage photos, IDs, business cards, and any image-based intake flow
Frequently Asked Questions
Q: What is Mistral AI?
Mistral AI is an AI lab that develops open-weight and frontier language and vision models. The integration gives Workflows direct, governed access to those models using your own API key.
Q: Which Mistral models are available in the model dropdown?
Models from the Mistral Large, Medium, Small, Ministral and Magistral families. The list is refreshed periodically as Mistral retires legacy versions and ships new ones.
Q: Do I need a separate Mistral account?
Yes. Bring your own API key from console.mistral.ai. Inference is billed by Mistral directly based on your account tier and chosen model.
Q: Are Mistral AI actions premium workflow actions?
Yes. All three actions consume premium action credits at the standard automation rate, in addition to Mistral usage charges.
Q: Can I use workflow variables inside prompts?
Yes. Both the System Prompt and the Prompt accept inline variables — contact fields, custom fields, trigger payload values, and the outputs of earlier workflow steps.
Q: Where is the AI-generated response stored?
It is exposed as a workflow output variable on the action. Use it in messages, write it to custom fields, or pass it to downstream steps. It is not persisted as a separate record by default.
Q: What happens if Mistral returns an error or times out?
The action surfaces the error to the workflow execution log, and the workflow continues based on its configured branching. Always test the action before publishing, and add a fallback branch if reliability matters.
Q: Can the generated response be used in SMS or email messages?
Yes. The output variable can be inserted into Send SMS, Send Email, internal notifications, and any other messaging action.
Q: What is the embedding output dimension?
1024 dimensions. The vector is suitable for direct use with major vector databases. Pass it to a webhook action that writes to your vector store.
Q: What image formats does Analyze Image accept?
Standard PNG and JPEG via direct URL, including images stored in Media Storage that are referenced by file URL. Images are processed at native resolution by the underlying vision model.
Q: Are these actions production-ready?
All three actions are released as Beta. They are safe to use in live workflows; expect incremental UX changes — for example, additional models added to the dropdown — as the integration moves out of Beta.
new
Agency Settings and Billings
🔐 Support Access Controls
We’ve added the ability for agencies to enable temporary support access to their accounts from within the platform.
What’s Included
New Support Access section under:
Agency View → Settings → Company → Advanced Settings
Users can:
Enable support access
Define a time-bound duration
Extend or revoke access anytime
Why This Was Built
This is a security and compliance-driven update to ensure:
- Access is explicitly user-approved
- Access is time-limited and auditable
- Better alignment with compliance requirements around data access
Help article :
Load More
→