AnsweredAssumed Answered

Webhook response mapping not updating lead

Question asked by Caleb Williams on Dec 4, 2019
Latest reply on Dec 5, 2019 by Caleb Williams

Like • Show 1 Like1
Comment • 12

I have a webhook that is working and I see the response come back as a JSON as:

     {
          "results": {
               "id": 2,
               "number": "0001",
               "name": "city, state",
               "ouId": 2,
               "config": {
                    "show1": true,
                    "show2": true
               }
          },
          "success": true,
          "message": "OK"
     }

However my response mapping of result.config.show1 results.config.show1 to a lead field is not updating the lead field. I have tried having the lead field be of type boolean, string, and text area with no change.

Is there an issue with Marketo reading this JSON correctly? Is there another way to get to having those values update a field on the lead? I'm even ok if that means using email scripting to evaluate the JSON.

Thanks,

Caleb

json marketo webhooks

Sanford Whiteman Dec 4, 2019 8:43 PM

Correct Answer

Recreate the entire webhook and retest (no, this isn't a wild guess).

See the reply in context

No one else had this question

Outcomes

Sanford Whiteman Dec 4, 2019 3:20 PM

results has an "s".

Actions

Caleb Williams @ Sanford Whiteman on Dec 4, 2019 6:05 PM

Sanford,

Thanks for the reply and the close eye. I've confirmed this was just at typo in my question. Properly written as `results.config.show` in my field mapping.

I'd prefer that I was just that blind, and it wouldn't be the first time.

Regards,
Caleb

Actions

Sanford Whiteman @ Caleb Williams on Dec 4, 2019 6:35 PM

Actually there's a typo in your last reply, too.

But as long as you have the right dotted JSON path, that's very simple JSON and will be no problem. Ensure the Response Type is set to JSON, and look in Field Management and make sure the field is updateable via webhook.

Actions

Caleb Williams @ Sanford Whiteman on Dec 4, 2019 7:32 PM

I guess that's what i get for trying to protect some of the values / keys by retyping them.

To test your comment about "updatable via web hook", because I am unsure where or how to control that, I have another lead field 'franchiseNumber' which is currently updated via another web hook and has been working for some time. Here is an example of that other web hook's result. This location web hook also returns a JSON object, though it is nested in and array eg [{ data }].

That same field is present in this web hook as the 'number' parameter. On the same web hook, mapping `results.number` to the lead field 'franchiseNumber' also does not update the field.

And yet that field is not updated here. I have also made sure that these values are `null` on my test lead so that its not a case of the value not changing with the web hook result.

Actions

Sanford Whiteman @ Caleb Williams on Dec 4, 2019 7:43 PM

To test your comment about "updatable via web hook", because I am unsure where or how to control that...

I'm talking about Block Updates in Field Management. It's a per-field setting.

Please show the details of the Call Webhook activity.

Actions

Caleb Williams @ Sanford Whiteman on Dec 4, 2019 8:13 PM

Ah I see. Nothing blocked:

Actions

Sanford Whiteman @ Caleb Williams on Dec 4, 2019 8:43 PM

Recreate the entire webhook and retest (no, this isn't a wild guess).

1 person found this helpful

Actions

Sanford Whiteman @ Caleb Williams on Dec 4, 2019 8:46 PM

And don't run anybody through until you've built the whole thing incl. Response Mappings.

Actions

Caleb Williams @ Sanford Whiteman on Dec 5, 2019 6:31 AM

Sanford, thanks for your time in working through this. This worked. I guess i need to remember to "turn it off and on again" when things don't work in Marketo.

Actions

Sanford Whiteman @ Caleb Williams on Dec 5, 2019 6:57 AM

Well, you didn't have to until this bug cropped up recently. The webhook config is supposed to be editable! So you should open a case if you get a chance, need more pressure for a fix.

Actions

Michael Tucker Dec 5, 2019 8:05 AM

Glad this was resolved. Sometimes I run into issues when the response isn't mapped using an index value for the vector... Your JSON response isn't configured this way, but if there were no "response" array title, it's valid to have "[0].id" that would write the value 2 to whatever Marketo field you mapped that to...

Just food for thought for response mapping issues...

Actions

Caleb Williams @ Michael Tucker on Dec 5, 2019 8:08 AM

Yep, we use this on another web hook. Can't remember where i stumbled on the [0].key idea but it works very well.

Actions

12 Replies

Sanford Whiteman Dec 4, 2019 3:20 PM
Mark Correct
Correct Answer
results has an "s".
Like • Show 0 Likes0
Actions
- Caleb Williams @ Sanford Whiteman on Dec 4, 2019 6:05 PM
  Mark Correct
  Correct Answer
  Sanford,
  
  Thanks for the reply and the close eye. I've confirmed this was just at typo in my question. Properly written as `results.config.show` in my field mapping.
  
  I'd prefer that I was just that blind, and it wouldn't be the first time.
  
  Regards,
  Caleb
  Like • Show 0 Likes0
  Actions
  - Sanford Whiteman @ Caleb Williams on Dec 4, 2019 6:35 PM
    Mark Correct
    Correct Answer
    Actually there's a typo in your last reply, too.
    
    But as long as you have the right dotted JSON path, that's very simple JSON and will be no problem. Ensure the Response Type is set to JSON, and look in Field Management and make sure the field is updateable via webhook.
    Like • Show 0 Likes0
    Actions
    - Caleb Williams @ Sanford Whiteman on Dec 4, 2019 7:32 PM
      Mark Correct
      Correct Answer
      I guess that's what i get for trying to protect some of the values / keys by retyping them.
      
      To test your comment about "updatable via web hook", because I am unsure where or how to control that, I have another lead field 'franchiseNumber' which is currently updated via another web hook and has been working for some time. Here is an example of that other web hook's result. This location web hook also returns a JSON object, though it is nested in and array eg [{ data }].
      
      That same field is present in this web hook as the 'number' parameter. On the same web hook, mapping `results.number` to the lead field 'franchiseNumber' also does not update the field.
      
      And yet that field is not updated here. I have also made sure that these values are `null` on my test lead so that its not a case of the value not changing with the web hook result.
      Like • Show 0 Likes0
      Actions
      - Sanford Whiteman @ Caleb Williams on Dec 4, 2019 7:43 PM
        Mark Correct
        Correct Answer
        To test your comment about "updatable via web hook", because I am unsure where or how to control that...
        I'm talking about Block Updates in Field Management. It's a per-field setting.
        
        Please show the details of the Call Webhook activity.
        Like • Show 0 Likes0
        Actions
        Caleb Williams @ Sanford Whiteman on Dec 4, 2019 8:13 PM
        Mark Correct
        Correct Answer
        Ah I see. Nothing blocked:
        
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Caleb Williams on Dec 4, 2019 8:43 PM
        Unmark Correct
        Correct Answer
        Recreate the entire webhook and retest (no, this isn't a wild guess).
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Sanford Whiteman @ Caleb Williams on Dec 4, 2019 8:46 PM
        Mark Correct
        Correct Answer
        And don't run anybody through until you've built the whole thing incl. Response Mappings.
        Like • Show 0 Likes0
        Actions
        Caleb Williams @ Sanford Whiteman on Dec 5, 2019 6:31 AM
        Mark Correct
        Correct Answer
        Sanford, thanks for your time in working through this. This worked. I guess i need to remember to "turn it off and on again" when things don't work in Marketo.
        Like • Show 1 Like1
        Actions
        Sanford Whiteman @ Caleb Williams on Dec 5, 2019 6:57 AM
        Mark Correct
        Correct Answer
        Well, you didn't have to until this bug cropped up recently. The webhook config is supposed to be editable! So you should open a case if you get a chance, need more pressure for a fix.
        Like • Show 2 Likes2
        Actions
Michael Tucker Dec 5, 2019 8:05 AM
Mark Correct
Correct Answer
Glad this was resolved. Sometimes I run into issues when the response isn't mapped using an index value for the vector... Your JSON response isn't configured this way, but if there were no "response" array title, it's valid to have "[0].id" that would write the value 2 to whatever Marketo field you mapped that to...

Just food for thought for response mapping issues...
Like • Show 2 Likes2
Actions
- Caleb Williams @ Michael Tucker on Dec 5, 2019 8:08 AM
  Mark Correct
  Correct Answer
  Yep, we use this on another web hook. Can't remember where i stumbled on the [0].key idea but it works very well.
  Like • Show 0 Likes0
  Actions

Webhook response mapping not updating lead

Outcomes

Related Content

Recommended Content