Google Calendar appointments to Monday.com CRM

[qtc]

Hi!

I'm stuck with the last step of my workflow https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY4MDYzZjA0Mzc1MjZhNTUzMjUxMzYi_pc

Could you please advise me?

Workflow logic:​

New leads comes in from Google Calendar appointment → ALL coming into Group 2 of monday.com CRM

Name of Group 1: New web leads from Brevo
Name of Group 2: Appointments Booked

2 Routers:

• If phone number exists in Group 1 → Move that existing lead from Group 1 to Group 2 (no need to create new row).
• If phone number does NOT exist in Group 1 → Create a new lead in Group 2.

Thank you!!

 

[Preeti Paryani]

Hello @qtc,

Upon reviewing your workflow, it appears to be set up correctly. However, could you please clarify the specific challenge you're facing with the last step of the workflow?

This will help us assist you more effectively. Looking forward to your response.

 

[qtc]

Dear Preethi,

I received this email from Pabbly:

This email is to notify you that for the workflow "Google Calendar to Monday.com Apt Sync - Clients" , a recent task was not executed due to following error -​

Task History ID: IjU3NjUwNTY5MDYzZjA0MzM1MjZhNTUzMTUxMzE1MTZiNTQzOTBmMzQi_pc
Step Name: Monday.com > Move an Item to Group
Connection Name: Monday.com #1
Task Error Detail:

{
"errors > 0 > message": "Failed to lock item id for graphql mutation",
"errors > 0 > locations > 0 > line": 1,
"errors > 0 > locations > 0 > column": 73,
"errors > 0 > path > 0": "move_item_to_group",
"errors > 0 > extensions > code": "TooManyConcurrentRequestsException",
"errors > 0 > extensions > status_code": 429,
"errors > 0 > extensions > error_data > item_id": 2017635756,
"errors > 0 > extensions > error_data > tag": "graphql_item_locking_service",
"extensions > request_id": "bc8caa41-0006-9714-aeb0-58a93c2e3e10",
"status_code": 429,
"error_data > item_id": 2017635756,
"error_data > tag": "graphql_item_locking_service",
"error_code": "TooManyConcurrentRequestsException",
"error_message": "Failed to lock item id for graphql mutation",
"account_id": 29609172
}

 

[Preeti Paryani]

Hello @qtc,

Upon reviewing the task history, we couldn't identify any specific error associated with it. However, we have escalated the concern to the relevant team to further investigate and understand the reason behind the error notification.

We’ll keep you updated as soon as we receive more information.