Added support for MergedToContactID. #900
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Bump. It would be good if MergedToContactID was returned with a Contact which it currently isn't. |
|
LGTM, thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Scenario
Whenever a contact has been merged into another, we received a webhook event of an archived contact, but no additional information. We then had to perform a GET request by its 'resourceId' to get the contact.
The 'Before the addition of MergedToContactID:' screenshot below, show the payload we received when we made the GET request, but no 'MergedToContactID' was present.
The important aspect of this PR, is ensuring we received the 'MergedToContactID' value, allowing us to update our contact data with the newly updated ContactID.
Before the addition of MergedToContactID:
After the addition of MergedToContactID: