Define the Hubspot Additional field "Properties"

Hello dear community,

i am again working on the topic of mailchimp to hubspot via n8n and am currently trying to transfer the mailchimp interest groups to hubspot. The idea is to show the mailchimp group memberships in Hubspot.

This means that if a user’s group membership changes, the user’s “property” in Hubspot will change as well. (mono directional)

Since a direct synchronization is not “possible” I thought I would simply check the specific “property” under “additional fields” one after the other. Afterwards it can be defined as “true” or “false”. For example you can enter something in the additional field “City” but not in the properties. In addition, you can only select one property, which requires such a “more complicated” structure. Where do I have my mistake?


Here is the Workflow I’m working on, doe’s it make sense at all in that way? Or do you have a better suggestion to realize this worfklow? As always many thanks in advance!

{
  "nodes": [
    {
      "parameters": {
        "operation": "get",
        "list": "97bcdb1e43",
        "email": "={{$node[\"Mailchimp Trigger\"].json[\"data[email]\"]}}",
        "options": {}
      },
      "name": "Mailchimp",
      "type": "n8n-nodes-base.mailchimp",
      "typeVersion": 1,
      "position": [
        760,
        240
      ],
      "credentials": {
        "mailchimpApi": "Mailchimp API Key"
      }
    },
    {
      "parameters": {
        "conditions": {
          "string": [
            {
              "value1": "={{$node[\"Mailchimp\"].json[\"interests\"][\"8b51df2dfb\"]}}",
              "value2": "true"
            }
          ]
        }
      },
      "name": "IF 8b51df2dfb",
      "type": "n8n-nodes-base.if",
      "typeVersion": 1,
      "position": [
        950,
        240
      ]
    },
    {
      "parameters": {
        "conditions": {
          "string": [
            {
              "value1": "={{$node[\"Mailchimp\"].json[\"interests\"][\"fabdc0b7cc\"]}}",
              "operation": "contains",
              "value2": "true"
            }
          ]
        }
      },
      "name": "IF fabdc0b7cc",
      "type": "n8n-nodes-base.if",
      "typeVersion": 1,
      "position": [
        1350,
        260
      ]
    }
  ],
  "connections": {
    "Mailchimp": {
      "main": [
        [
          {
            "node": "IF 8b51df2dfb",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "IF 8b51df2dfb": {
      "main": [
        null,
        [
          {
            "node": "IF fabdc0b7cc",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  }
}

@Hueseyin Not sure if I understood well. I think you are confusing properties with custom fields. The property ‘property’ defines which fields will be returned after the operation is executed. I guess it’s not the best name, but it’s how Hubspot calls it. I think I sent a commit that updates that name to fields.

The fields description says the following:

It is used to include specific company properties in the results.
By default, the results will only include company ID and will not include the values for any properties for your companys.
Including this parameter will include the data for the specified property in the results.

To solve this, you have to create a custom field on Hubspot like this https://knowledge.hubspot.com/crm-setup/manage-your-properties, but sadly on the n8n side, there is no way yet to set custom fields. I will add this to my TODO list.

What you can do in the meantime is change the name of a property you do not use, for example, company_size to something like ‘interest_group’ and set in n8n as company_size. So within Hubspot, you will see the right label ‘interest_group’ with he value you set in n8n as company_size.

Hope that helps, if not simple get back to me.

Hey @RicardoE105, thanks for your answer.

That was exactly what I did. I created custom fields in Hubspot with the required " contact property".

They also appear in n8n, but unfortunately it was not possible to (re)define custom Property or set a value for them in n8n. Anyway, your last suggestion seems to be a temporary workaround and will work for a small demand for sure.

Thanks again.

yes, will let you know when a proper solution is added.

1 Like

@Hueseyin Just added this. Will let you know when is released.

2 Likes

Just got released with [email protected]