First Webhook, First Error. API_AddRecord

If that is the actual user token, it looks incorrect.

Hi Jack,

As a best practice for User Token you would want to keep them secure and be careful of sharing them. They function as a form of authentication within our API calls and can allow access to your data. To be on the safe side the end of this User Token has been cut out. If that was an actual User Token I would suggest deactivating it and instead replacing it with a new one if possible just to be on the safe side. 

As for error code 11 that error often comes up when the body of a Webhook contains XML characters that the API has trouble differentiating from your actual Webhook code. They can cause the message to become garbled. Do any of these fields you are passing over contain text elements and possible unique characters or XML character? Common culprits can be ", ', <, >, and &. 

Thank you, I'll delete the user token but this is my test db but I'll be more careful, thankyou for answer, I'll check the data and see what pop's up.

I've checked the data and can't see any offending characters, if this is working as I'd expect it to I just added one order to the source table I'd expect to see this appear in the destination table but the information is very simple and no strange characters.  The tables are about a year old so this web hook would be a new thing and cuts out a bit of manual work.  Would the script just be looking at the new row or the entire table? 

Whenever the webhook was triggered it would only be looking at any records that triggered the webhook, not the full table. If you are seeing that error still and your body doesn't have any of the possible trouble characters in it then there might just be a syntax error. In your live one did you have % signs around the usertoken as your example did? Also it looks like some of the markup may have gotten chewed up by the forum, could you repost the webhook again and I would suggest using the pre setting in the format bar when you submit it to help keep it from being chewed up by the forum input. I would be happy to give it another look over and see if anything jumps out at me. 

Well that is a step forward, I would suggest making sure that your new User Token is assigned to the right app or apps if this is passing data between two apps just to be sure it is assigned. For a standard webhook you wouldn't want those %s around the User Token in my experience

Between the > < on the usertoken line; are you using the name of the Usertoken from the drop-down list in the fields or are you pasting it in.  Try the former.  Sometimes I have had a hard time with the Usertokens; and I've had to copy the full Usertoken value to test that the webhook is working.  Once it is; I then try to revert it back to the selected token Name from the list.

Sometimes; I have had to rebuild a Webhook from scratch.  Also; I never use the <udata> line - it's unecessary.

Thanks everyone, now have this working and found out it's not very good at filling in dropdown fields.  Darn! 

I am glad to hear that was helpful, and sometimes it is the littlest detail that drives you crazy after you build out something bigger. I've done the exact same thing before. 

... I'm late to chime on on this thread, but out of curiosity, are you using a Webhook to learn the syntax for tacking something more complicated in the future?  ie why not just use a no code Automation?  Or is this perhaps a Cross Realm Webhook (which can probably be done with an Action).

Trying stuff out, I'm not familiar with all the components of Quickbase and do have a table from Big Commerce which needs loading. 

But, I would like to know if you can put two fields from the source into one field in the destination, I've not seen any syntax for this so just going one for one at the moment.