Skip to main content
Question

Post Webhook Response In The Record

  • April 15, 2021
  • 0 replies
  • 90 views
I currently have a POST webhook setup in QuickBase with Endpoint to our 3rd party software.

The way it triggers, is when New Client record is added in Quickbase, it runs the webhook, that creates a user name in our 3rd party software.

When I run that webhook via Postman, if it's successful, it would display a response value (the value would be the user ID that it created in our 3rd party software).

Response:
<?xml version="1.0" encoding="utf-8"?>
<string xmlns="http://www.tempuri.org/">1079</string>

How can I have QuickBase see that response value (1079), because I want that value integrated in a specific field, from New Client record in Quickbase.

------------------------------
Gene Gene
------------------------------
This topic has been closed for replies.

@Gene Strelkov
It doesn't appear as though you can parse the response you get from a webhook. Generally speaking, webhooks are meant to be one way only. Pushing updates as they happen to another system to parse and process. The JSON Handler channel provides more of a back and forth, but it looks like your third party system responds with XML​

------------------------------
Justin Torrence
Quickbase Expert, Jaybird Technologies
jtorrence@jaybirdtechnologies.com
https://www.jaybirdtechnologies.com/#community-post
------------------------------
  • BlakeHarrison
  • Quickbase Alumni
  • April 15, 2021
If you use Pipelines, you can capture the response in a text field and then parse the raw XML with a Formula Text (or Formula Numeric, since your value looks to be a number). You'll need to use a combination of SearchAndReplace and then Part. Probably something like this:
var text a = SearchAndReplace([XML],"\">","*");
var text b = SearchAndReplace($a,"</","*");


Part($b,2,"*")

​


------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quickbase Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------
Terms & ConditionsAccessibility statement