HighLevel logo
HighLevel
Create
Log in
Roadmap
Feedback
Opportunities & Pipelines
716
Changelog
Log in to your HighLevel account to give feedback

    Boards

  • Ad Reporting and Attribution

  • APIs

  • App Marketplace

  • Ad Manager

  • Automations

  • AI Employee

  • Voice AI

  • Conversation AI

  • Content AI

  • Blog

  • Bulk Actions

  • Calendar

  • Call Tracking

  • Client Portal

  • Communities

  • Company Object

  • Conversations

  • Certificates

  • Contacts

  • Custom Objects

  • CRM

  • Dashboard

  • Documents & Contracts

  • Domains

  • E-commerce Stores

  • Email Builder

  • Eliza

  • FB/ IG Messenger

  • Forms

  • Funnels

  • Google My Business

  • HL Affiliate Portal

  • Integrations

  • Invoicing

  • Phone System

  • LC Email System

  • Courses

  • Mobile App

  • Media Library

  • Agency Onboarding

  • Opportunities & Pipelines

  • Payments

  • Prospecting Tool

  • Reporting

  • Reputation Management

  • SaaS Mode

  • Smartlists

  • Snapshots

  • Social Planner

  • Sub-account Affiliate Manager

  • Surveys

  • Tasks

  • Template Library

  • Users & Permissions

  • Website

  • Whatsapp

  • Widgets

  • Wordpress

  • Listings

  • Chat Widget

  • Language - Internationalization

  • Payment Links

  • QR Codes

  • Quizzes

  • Reviews AI

  • POS and Mobile Payments

  • Reselling

  • Location Launchpad

  • HIPAA Compliance

  • Premium Support

  • Go Kollab

  • SEO

  • Marketplace new app request

  • RCS Messaging

  • Ask AI

  • Highlevel MCP

  • External Tracking

  • AI Knowledge Base

  • Agent Studio

  • Brand Board

  • Countdown Timer

Powered by Canny

Opportunities & Pipelines

Create/Update Opportunity should target the trigger opportunity
Right now, if you have an opportunity changed trigger begin a workflow, and use the Create/Update opportunity action, the workflow will not reliably modify the relevant triggering opportunity if the attached contact has multiple opportunities. It will often only modify the most recently created opportunity. An alternative solution would be to create an automation step allowing us to update opportunities by their ID. You can do this via the API but it's annoying to rely on outside apps for this.
11
·
Bug
·
complete
Opportunity Custom Fields are lost when moving opportunity to another pipeline using automation
Opportunity Custom Fields are lost (values are empty) when the opportunity is moved to a different pipeline using the workflow action 'Create Or Update Opportunity'. in addition, as a workaround, copying the values from the opportunity itself is not allowed for fields of type dropdown or number.
12
·
Bug
·
complete
Powered by Canny