Skip to content

[Bug Report: Upsert Errors and Documentation Update] #37

Open
@i-am-rad

Description

@i-am-rad

🐛 Describe the Bug

A clear and concise description of what the bug is.

To produce this:

  1. Create a contact with just a phone number
  2. Create another contact with just an email address
  3. Perform an upsert with both the email and phone
  4. It returns the email address contact id. It does not attempt to add the phone due to duplicate contact settings.

📍 API Endpoint

Which API endpoint does this relate to?

https://marketplace.gohighlevel.com/docs/ghl/contacts/upsert-contact

✅ Expected Behavior

What should have happened?

Upsert should return an error if it cannot add data. It may be successful in upserting other data but it silently doesnt inform you of something critical like a failure to have the phone and email on a contact. But you should inform us if a duplicate is detected and the contactId of the duplicate. There are backend checks happening since it fails to push the phone into the contact with email address.

💻 Screenshots or Code Samples

Paste relevant markdown/code samples or screenshots.

🧠 Additional Context

Any other helpful information?

Documentation should clearly state:

"Upsert must have email or phone number. If email is provided it is the primary and follows the setting in the Highlevel subaccount. If upserting an email and phone and a duplicate is detected then we will upsert the contact based on preference sin the subaccount but it will not merge the contact."

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug-documentation-errorsImprovements or additions to documentation of the Highlevel API

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions