Forum Discussion

BobThomas1's avatar
BobThomas1
Qrew Cadet
5 years ago

I can't get my first Webhook to add to Audit Logs Table

Using the University site to learn as much as I can on QuickBase. I have been spending the last three days on Webhooks. I am having trouble. I am getting 404 errors. I have sent my endpoint URL sent to a troubleshooting URL and I do get a response. I am thinking that my message body is wrong, since I can't find any other reason I can't get the change of Tasks from 'not started' to 'in-progress' to write a single record?

<qdbapi>
<usertoken>%user.token.b5ejhe_nsv5_bsjd.Training Token%</usertoken>

<field fid ="6" > [Project - Name]</field>
<field fid ="13" > [Name]</field>
<field fid ="7" > [Old.Status]->[New.Status]</field>
<field fid ="8" > [Date Modified]</field>
<field fid ="9" > [Last Modified By]</field>

</qdbapi>

------------------------------
Bob Thomas
------------------------------
webhook
  • NathanHawe's avatar
    NathanHawe
    Qrew Cadet
    5 years ago
    I haven't done any work with Webhooks specifically, but I do know that if the QUICKBASE-ACTION header is misspelled in a request you can get a 404 HTTP status code (the body of the response will indicate that the operation does not exist).  If you haven't already, check that your Webhook has a message header of "QUICKBASE-ACTION" with the appropriate action (e.g., "API_AddRecord").

    ------------------------------
    Nathan Hawe
    ------------------------------
    • BobThomas1's avatar
      BobThomas1
      Qrew Cadet
      5 years ago
      First I'm replying to the thread by email. I didn't see the three
      responses from Nathan, Austin & Laura, but received your responses via
      email. So maybe I'm not working the forum right?

      Anyway, thanks Laura on automation & Austin on the token. The token is
      right as I clicked on it in between the brackets.

      So Nathan mentioned <<
      "QUICKBASE-ACTION" with the appropriate action (e.g.,
      "API_AddRecord").>>> and I thought, maybe I misspelled or didn't have
      the right capital letters (not sure if case sensitive, so I just mimic
      what I'm told). Then I realized I had seen this QUICKBASE-ACTION: and
      recall yesterday that I wondered that I looked again and sure I saw the
      colon.

      So long story short, the 'colon' is?? a nogo! Worked great with the
      script I posted once I changed QUICKBASE-ACTION: to QUICKBASE-ACTION

      Thanks all & this forum looks great for learning. I was beginning to
      pull hairs out and didn't think that the ':' would cause this to fail
      totally.:-)

      ------Original Message------

      I haven't done any work with Webhooks specifically, but I do know that if the QUICKBASE-ACTION header is misspelled in a request you can get a 404 HTTP status code (the body of the response will indicate that the operation does not exist).  If you haven't already, check that your Webhook has a message header of "QUICKBASE-ACTION" with the appropriate action (e.g., "API_AddRecord").

      ------------------------------
      Nathan Hawe
      ------------------------------
      • BobThomas1's avatar
        BobThomas1
        Qrew Cadet
        5 years ago
        Now I see the responses, thanks all.

        ------------------------------
        Bob Thomas
        ------------------------------
    • BobThomas1's avatar
      BobThomas1
      Qrew Cadet
      5 years ago
      FOR SOME REASON THE REST OF MY RESPONSE IS MISSING SO...So Nathan mentioned <<"QUICKBASE-ACTION" with the appropriate action (e.g.,
      "API_AddRecord").... and I thought, maybe I misspelled or didn't have
      the right capital letters (not sure if case sensitive, so I just mimic
      what I'm told). Then I realized I had seen this QUICKBASE-ACTION: and
      recall yesterday that I wondered that I looked again and sure I saw the
      colon.

      So long story short, the 'colon' is?? a nogo! Worked great with the
      script I posted once I changed QUICKBASE-ACTION: to QUICKBASE-ACTION

      Thanks all & this forum looks great for learning. I was beginning to
      pull hairs out and didn't think that the ':' would cause this to fail
      totally.:-)

      ------------------------------
      Bob Thomas
      ------------------------------
      • BobThomas1's avatar
        BobThomas1
        Qrew Cadet
        5 years ago
        So Nathan mentioned ..."QUICKBASE-ACTION" with the appropriate action (e.g.,
        "API_AddRecord")... and I thought, maybe I misspelled or didn't have
        the right capital letters (not sure if case sensitive, so I just mimic
        what I'm told). Then I realized I had seen this QUICKBASE-ACTION: and
        recall yesterday that I wondered that I looked again and sure I saw the
        colon.

        So long story short, the 'colon' is?? a NoGo! Worked great with the
        script I posted once I changed QUICKBASE-ACTION: to QUICKBASE-ACTION

        Thanks all & this forum looks great for learning. I was beginning to
        pull hairs out and didn't think that the ':' would cause this to fail
        totally.:-)


        ------------------------------
        Bob Thomas
        ------------------------------
  • AustinK's avatar
    AustinK
    Qrew Commander
    5 years ago
    To add on to this some of the Quick Base help documentation actually has the wrong header listed. The one they have listed will give you no real error but the webhook will just fail to fire and leave you scratching your head. I've reported the ones I've found in the past but more still might be out there. The way Nathan suggested is the right way.

    Looking at the webhook above it looks like the user token is malformed. I would not expect to see a token like that. My user tokens are always similar to a random string like this one I just made up "fls45t_gfgf5hgh_hrteh453y5yu546". I also don't wrap mine in percent signs, so that may be another issue. I would verify you are using the right user token. If it is correct then that is a brand new format for them or at least one I have not seen yet.

    Looking at the rest of the webhook you might be running into an issue with "[Old.Status]->[New.Status]" I would expect to just use [Status] here. If for some reason it isn't the newest Status(I don't see why it wouldn't be) you can look into other options. Just go simple for now.
  • LauraThacker's avatar
    LauraThacker
    Qrew Captain
    5 years ago
    I would recommend a QBAction for this or an Automation; rather than a Webhook.  A QBAction allows you to specifically choose "old value" into one field and "new value" into another field.  The Automation will allow you to specify whether the input comes from the "old data value" or the "new data value" into a field; which is a little-bit-less-intuitive when setting it up; but does the same thing as the QBAction.

    ------------------------------
    Laura Thacker (IDS)
    laura@intelligentdbs.com
    (626) 771 0454
    ------------------------------