I am helping a client pass data into ManyChat via their API integration. All API Calls were integrated using the documentation at this link
This it the current flow we have set up:
-
Creating a Contact with their platform's built-in fields (createSubscriber API call)
-
Adding a "Tag" to that contact using the Contact ID generated in Step 1 (addTagByName API call)
-
Updating custom fields using the Contact ID generated in Step 1 (setCustomFieldByName API Call)
The above process works as anticipated with new email records. But where we run into a bit of an issue is with duplicate emails that already exist in the ManyChat account. In Step 1, if we try to create a contact using an email that is already in the account, it spits back an HTTP 400 error saying that the Email Already Exists. This prevents us from being able run steps 2 and 3 on that email record.
If we were either able to get an API response in step 1 for duplicate emails that indicates the Contact ID for that pre-existing email and/or use the email address (instead of Contact ID) to update the tag/custom fields in Steps 2/3 we would have a work-around. But under the current settings it doesn’t appear we have any options. Does anyone with more familiarity with the ManyChat API have ideas of what we could do to deal with duplicate email records?
