Error code 6831 : "Input Parameter Missing" when trying to PUT via Invoke

Error code 6831 : "Input Parameter Missing" when trying to PUT via Invoke

I'm creating some custom script in Zoho Flow to associate the Zoho Projects Client Company. I've got the find piece of the code working but I want to update the found record with the CRM ID

Here is my code
  1. string ZP_getClientID(string varClientName, string varCRMID)
    response = invokeurl
        url :""
        type :GET
        connection:"MY CONNECTION"
    // Change the response to a map to extract specific information
    varClients = response.get("clients");
    // iterate the list of clients to match the CRM Account ID
    for each  varRecord in varClients
        clientanme = varRecord.getJSON("name");
        if(clientanme = varClientName)
                 primaryclientid = varRecord.get("id");
    //Update the CRM ID in projects
    crmInfo = Map();
    updateresponse = invokeurl
        url :""
        type :POST
        connection:"MY CONNECTION"
    info updateresponse;
    return primaryclientid;
Where the record I am trying to update looks like this :

  1. {
  2.     "clients": [
  3.         {
  4.             "crm_account_id": "",
  5.             "name": "My Customer Name",
  6.             "id": 91102000005162221
  7.         }
  8.     ]
  9. }
I'm just getting error
   error : {
      code : 6831,
      message : "Input Parameter Missing"

      • Sticky Posts

      • Project Management via Emails in Zoho Projects

        We write mails to communicate. In Zoho Projects, we can write mails to collaborate. Yes, Zoho Projects supports Email based project management. The mails that you send turn into tasks, bugs, project comments, forum replies, etc. The following are some of the frequently asked questions that might be of some help to you. What are the pre-requisites to manage my projects through Emails? You need to have a personal / business mail ID that is registered and confirmed with To learn more
      • Four types of task dependencies

        "Nothing is particularly hard if you divide it into small jobs."                                                                                                                  - Henry Ford Projects, small or large, are driven by simple work units called tasks. Monitoring standalone tasks might look simple but as the workflow becomes elaborate, tasks may start relying on one another. In project management, this relationship between tasks is termed as "Task Dependencies". Dependency between tasks arise
      • Task and Project numbering

        Zoho Projects now generates a unique number for each project, task, and issue added. The auto-generated ID is a combination of a prefix and a number which is assigned by Zoho Projects. The unique IDs for projects, tasks, and issues will be useful to track, identify, and search easily. You can modify the settings to enable or disable the Project and Task IDs.  Learn more on how to modify Prefix & ID settings for projects and tasks. Issue IDs cannot be disabled, only its prefix can be changed (tasks
      • Task Inline Editing Enhancement

        Hi All, Today, we have made an enhancement in task inline editing. In 4.0, task edit is moved in a single screen in a pop-up. We designed this in-order to make the task edit across the product to be the same. Let it be in Feeds, Tasks & My Tasks tab, Calendar & My Calendar tab, a click on the task title will open the popup and user can edit the values. Customers pointed us the inline editing was very useful to them & how much they miss that in 4.0. Based on the feedback, we have rolled out this enhancement.
      • Blueprint in Zoho Projects

        Often, we stumble upon tasks having the same status workflow. Repetitive task processes are tedious to handle, right? That’s why we have introduced Blueprint for task automation. Blueprint is a tool to organize tasks and automate them based on the workflow you design and the criteria you define.    How do I associate tasks with a blueprint? You can set the criteria while creating the blueprint such that when you publish a blueprint, the tasks that satisfy the criteria will be associated with the