Problem mapping Owner ID and select fields on Make.com (only for leads)

Sean Chua
Sean Chua Member Posts: 2 NEW MEMBER
edited October 21 in Apps and Integrations #1

I'm mapping a website form to create a lead on make.com.

I'm able to map integers to owner_id and text to select fields for both persons and organisations. But I'm getting errors when I try to map the exact same fields for leads and I don't know why.

For example, when I try to map the exact same owner_id for leads, I get this error: "error 400: provided dataset is not valid ("owner_id" must be a number)". I'm stumped on this one. Mapping the variable = "12345" does not work. But typing down "12345" works.

When I map the same select field, I get this error "error. 400: provided dataset is not valid (Custom field validation failed. Error: Expected 'number' as value of singleOption field.". (I get that this is asking for the ID of the select field item, but mapping text worked for persons and orgs, why not leads as well?

image.png

Tagged:

Answers

  • Manuel Oliveira
    Manuel Oliveira Admin Posts: 1,292 COMMUNITY MANAGER
    1000 Comments 250 Likes 25 Answers Third Anniversary
    #2

    @David Gurr (Make.com) do you have any advice that might be helpful here?

  • Tony Xavier
    Tony Xavier Pipedrive Team Posts: 144 PIPEDRIVE TEAM
    100 Comments 25 Likes 5 Answers Second Anniversary
    #3

    Hello @Sean Chua,

    Even though Make is a third-party tool and we have limited visibility, as they use Pipedrive's open API, we can try to provide some insights based on that.

    The error you are seeing with owner_id seems related to an issue with Make. As long as the value you map to the owner_id parameter is an integer, the request will be processed correctly, and you shouldn't see the error. It would be best if you could confirm with Make that the value you are mapping is, in fact, formatted as an integer to resolve this issue.

    When it comes to Single/Multiple custom fields error, this is currently expected as the API call for Leads only supports the ID of the Option instead of the value itself. This is something that only affects the Leads, and it is expected that passing along the value of options for Person and Organisation works.

    Since you will be hardcoding the value for custom fields, you can either use the API call to get details of all Deal/Lead field or you can contact our support team with the name of the custom field and they will be able to share the ID correpsonding to each value.

Categories