Forum Discussion

JackFretwell's avatar
JackFretwell
Qrew Assistant Captain
6 years ago

New fields added to record without human action.

This company has a customer facing website on Big Commerce which customers fill in, there is a webhook between this data and a storage table in Quickbase.   

The storage table now has a webhook to an Opportunities table (where we keep customer requests and process them).

The only reliable field here is the email address.  We are wanting to use email address as a key field to take information out of the contacts table.

Is there a way I can add additional information (name, company) to the record at any stage which doesn't involve human intervention?

Any relationships I have set up all require human action to select a record and draw the additional fields in.

We expect volumes to increase and don't want to have someone keying company names in all day if there is an automatic way of adding additional fields.

Can any automatic actions complete this for me?  Form rules?  

If this can't be done I'll need some advice to give to my manager.
  • An API can edit any record or Webhook.  Typically the API or webhook will refer to the Record ID and will contain a phrase like

    &rid=123456

    but you can also edit a record be specifying the key field its its not the Record ID# field.

    In that case the syntax is 

    &key=fred.flintstone@bedrock.com

    if the Key field of the table is an email field.



  • JackFretwell's avatar
    JackFretwell
    Qrew Assistant Captain
    Thank you, feel my old friend API_DoQuery is going to pop back soon... : ) 
  • JackFretwell's avatar
    JackFretwell
    Qrew Assistant Captain
    Is there any information on using API_DoQuery in a Webhook?  I can't find anything useful from Google or the QB Community.
  • Hi Jack,

    Typically API_DoQuery and an Webhook are not compatible for the use you are looking to put them to of getting data from somewhere else and then including it in a change. This is because Webhooks are only a one way communication, they send out a request but they aren't set up to take the response back and do anything with it. That is usually an example of where a developer needs an intermediate in the service to send out the API_DoQuery, get back the request, and then send the now finished and formatted data into Quick Base. Webhooks don't have the capacity to handle multiple steps like that. 

    For your Contact table do you have the key field set to email address? If you did then you could set up the relationship between Contacts and Opportunities to use the related contacts email to identify them automatically. Then you would just push the email address that comes in with the Webhook to write into the related contact field so long as they key on Contacts is email address. That just requires you to change the key field if you don't currently have it set to email address which can break any other relationships you have and would make them need to be rebuilt. I hope that information is helpful Jack and thank you for reaching out.