Update Dropdown Select Options with a workflow

[ZSinger]

Is there a way to update the list of dropdown select values via a workflow? 

Use case: We have a list of channel partners we are managing through target accounts. If a specific team owns a company and adds them to their target accounts, then I would like the company name to be added as an option to a separate 'referral source' property. This way we can mangage and attribute referrals back to a constrained set of companies. 

I know I am able to set or append the value of the property, but don't see a way to append the list of constrained values for the dropdown. Is there a way to do this?

[DigitalImpact]

@ZSinger  My team just implemeted this exact scenario for a client using custom code in a workflow. It only took an hour or so to code. Let me know if you still have a need for this and I can have my team help out.

[karstenkoehler · Accepted solution]

Hi @ZSinger,

This is not possible in standard workflows, it would require custom code actions (available in Operations Hub Professional or Enterprise) based on the HubSpot CRM API endpoint.

Best regards!

[jTinker-rein]

Im Halfway through a workflow and I am so dissapointed by this. I do not know how to code, and due monday I need to load 20 listings into the system and a seperate spreadsheet. I'm using zapier to acomplish both at once. At least that was the goal. 

However, listings do not work with forms, with zapier, or anything besides intering them by hand. So my best chance was to create a deal with a trigger moving it over into a listing... But I cannot do that either without being able to edit drop downs. This should for sure be included. The fields I'm equating are the same just might have a different selection coming. 

[karien]

Hi Karsten, the goal is to update/patch/ADD a dropdown "option" to an already existing dropdown field/property, not to update the value of a record.....

example my dropdown = option A, option B
now add option C to the dropdown field via custom code

[karien]

Create a property

POST/crm/v3/properties/{objectType}

DELETE
/crm/v3/properties/{objectType}/{propertyName}
Archive a property
Move a property identified by {propertyName} to the recycling bin.

Hi Karsten, do you think the route will be first delete te property and then re-create it? problem is, this wont work, right? because this property will have values already? UPdate/patch wont work, because it seems it can only replace a current property value, not add it?