Create Google contact error 400

[sampaht]

Your Workflow URL

https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjYwNTY1MDYzMDA0MzY1MjZkNTUzMDUxMzEi_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

create google contact action get this response:
error code:
400
error message:
Invalid JSON payload received. Unknown name "": Root element must be a message.
error status:
INVALID_ARGUMENT

 

[Preeti Paryani]

Hello @sampaht,

Could you please try performing the action by selecting a gender from the dropdown under the Gender field and confirm if it works?

 

[sampaht]

change it to drop down still make it error 400

 

[anushkasahu]

Hello @sampaht,

After carefully reviewing your workflow, we found that the error was caused by the date and month input fields. Specifically, Google Contacts does not accept a leading zero in the month field.

We have added two Text Formatter steps to remove the leading zero before sending the data.

After this adjustment, everything is working perfectly.
Please test it on your end and let us know if it works as expected. Also, we would really appreciate it if you could rate our support agent using the link in the signature below.

 

[anushkasahu]

Hello @sampaht,

After carefully reviewing your workflow, we found that the error was caused by the date and month input fields. Specifically, Google Contacts does not accept a leading zero in the month field.

We have added two Text Formatter steps to remove the leading zero before sending the data.

After this adjustment, everything is working perfectly.
Please test it on your end and let us know if it works as expected. Also, we would really appreciate it if you could rate our support agent using the link in the signature below.

 

[sampaht]

Thanks. Now it is working. Even with gender from event0.

 

[anushkasahu]

Thanks for the update and for filling the feedback form. For now, we are closing this thread and if you encounter any issue in future, please feel free to reach out to us.

 

[sampaht]

I created follow up workflow https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjYwNTY1MDYzMTA0MzQ1MjY1NTUzNjUxMzEi_pc
But I cannot test the update google contact.
The format is same, content sent from this workflow and follow up workflow is same. One to create contact, and one to update contact.

1. There is possibility contact will have more than 1 phone number, and more than 1 email address. How to translate it to update google contact action?
2. Where is field [salutation]?
3. How to update custom fields if it is not always exist? I have 2 custom field, UID and gender (as a custom field, not Google standard field). Gender is not always sent, may be blank. If blank do not update gender.

 

[ArshilAhmad]

I created follow up workflow https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjYwNTY1MDYzMTA0MzQ1MjY1NTUzNjUxMzEi_pc
But I cannot test the update google contact.
The format is same, content sent from this workflow and follow up workflow is same. One to create contact, and one to update contact.

1. There is possibility contact will have more than 1 phone number, and more than 1 email address. How to translate it to update google contact action?

If there are two or more email addresses or phone numbers, you need to pass them in a comma-separated format, as shown in the help text.

2. Where is field [salutation]?

Are you referring to the 'Prefix' field being missing in the 'Update Contact' action step?

3. How to update custom fields if it is not always exist? I have 2 custom field, UID and gender (as a custom field, not Google standard field). Gender is not always sent, may be blank. If blank do not update gender.

You can map values to both fields. If data is provided during automation, the fields will be updated; otherwise, they will remain unchanged.

You might want to check this workflow if you are looking to create/update contact in Google Contacts.

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
Pabbly.com
Rate your support

 

[sampaht]

Hi, this workflow run well in test.
But in real use, it get errors at google contact action. can you check history:
IjU3NjUwNTZiMDYzZTA0MzA1MjZiNTUzNDUxMzc1MTY0NTQzNTBmMzki_pc
IjU3NjUwNTZiMDYzZTA0MzM1MjY4NTUzYzUxMzc1MTY2NTQzNDBmMzci_pc
IjU3NjUwNTZiMDYzZTA0MzM1MjY4NTUzYzUxM2E1MTYyNTQzNjBmMzUi_pc
IjU3NjUwNTZiMDYzZTA0MzM1MjY4NTUzZDUxMzM1MTZhNTQzODBmMzIi_pc
IjU3NjUwNTZiMDYzZjA0MzU1MjZhNTUzMjUxMzc1MTYyNTQzOTBmMzIi_pc

 

[sampaht]

Same issue happens in this workflow

Pabbly Connect

connect.pabbly.com

only test workflow runs well, but real use case failed. Please check the history too.

 

[Preeti Paryani]

Hello @sampaht,

Thank you for sharing the workflow details.

For the workflow where you are creating the contact, please try recreating it in the Classic Builder and let us know how it performs there.

Regarding the workflow where you are updating the contact, please delete the “Update Contact” step once and add it again. Then check the workflow history to see if it runs properly. If the issue persists, try creating the same workflow in the Classic Builder as well and let us know how it goes — or simply inform us so we can look into it further.

 

[sampaht]

hi @Preeti Paryani,
recreating it in classic builder have same issue. When running save and send request, google contact create the contact. But when receiving actual data it have error 400.
classic builder workflow_id=IjU3NjYwNTY0MDYzNDA0MzE1MjY4NTUzMDUxMzMi_pc

 

[ArshilAhmad]

During setup, you mapped the key 'Phone Nos 2 Name' in the Custom Field.

However, during automation, you are not receiving this key, which is why nothing is being mapped to the Google Contacts action step, resulting in the issue.

 

[sampaht]

However, during automation, you are not receiving this key

Thank you! This is the reason.

Are you referring to the 'Prefix' field being missing in the 'Update Contact' action step?

yes, i cannot find it in update google contact action.

 

[Preeti Paryani]

yes, i cannot find it in update google contact action.

Currently, the Update Contact action doesn't have the specific field. We have escalated the request to add it within the action. We will get back to you once we receive any updates on the developments.

 

[sampaht]

How to make it work 2 ways, But not triggering infinite loop?

If webhook source send data, update/create google contact.
If google contact updated, update webhook source with API action.

 

[Preeti Paryani]

Hello @sampaht,

Could you please let us know the trigger source/application from where the data is being captured in the trigger? This will help us assist you more effectively.

If your goal is to first search for a contact and then create or update it based on the search result, you can follow this approach:

1. Add a Router after the “Search Contact” action.
2. In one route, set the condition if the Contact ID from the Search Contact action exists, then Update Contact.
3. In the second route, set the condition if the Contact ID does not exist, then Create Contact.
4. After these routes, you can use the Data Forwarder: Return Data to Source action to send the data back to the webhook source.

This setup will ensure the process runs both ways without causing an infinite loop.

 

[sampaht]

As you read from previous conversation in this thread, I end up with creating 2 webhook trigger.
1 is triggered when I [create] a contact from other app. Thus leading to create google contact action
the other is triggered when I [save] a contact from other app. Thus leading to update google contact action.

It appears that the [save] trigger is always triggered, both from [create] (because after contact is <created>, it is <saved> to database). I plan to delete the [create] trigger using solution you offer below.

f your goal is to first search for a contact and then create or update it based on the search result, you can follow this approach:

1. Add a Router after the “Search Contact” action.
2. In one route, set the condition if the Contact ID from the Search Contact action exists, then Update Contact.
3. In the second route, set the condition if the Contact ID does not exist, then Create Contact.
4. After these routes, you can use the Data Forwarder: Return Data to Source action to send the data back to the webhook source.

The problem is, I want to be able to update contact from google contact (from web, android/ios device), and send it back to my app.
If I create "when google contact created/updated then create/update contact in my app" workflow, it will create infinite loop.