So I would have thought this would be a common question, but I can't find an answer anywhere on these forums, so here it is.
We use QBase as our CRM. I'd like to integrate a "Contact Us" form on our website that would then create the customer's record in QBase automatically. From there, I would create an automation that would create a task to call the customer for an appointment. Here's ideally how it would work:
1. Customer enters their info into the website
2. A record is created in Qbase containing their info
3. A task is created to contact them for an appointment
4. An email thanking the customer is automatically generated and sent.
I can't get past step 2 so far. I used this form creation wizard I found:
https://login.quickbase.com/db/6mztyxu8?act=DBPage&pagename=formWizard.html&_ga=2.154279416.1119470619.1565032774-2045215432.1565032774
and input the app token, etc., but I get an error when I test it out on my website:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<qdbapi>
<action>API_AddRecord</action>
<errcode>22</errcode>
<errtext>Sign-in required</errtext>
<errdetail>The page you have requested can be viewed only by users who have signed in. Please sign in to proceed.</errdetail>
</qdbapi>
I could find no real helpful information about this error. Obviously my customers can't be logged in to Qbase to use the form. I found some rough info about API login, but I'm not certain that is the correct path for this use-case. Any help out there?
Question
Create a ""Contact Us"" form on website, create Record in QBase, Auto-email response
+10Your best route to go is to open your application to the internet with the Everyone on the internet use with an extremely limited role that can only add records in your source table. They can't view/modify anything - just add to that table. That way you can get around the authentication issue.
You don't want to go to api_authenticate or deal with tokens since this is client side and you don't want to expose that information publicly on your site.
Everyone on the internet would be an easy solution though.
Chayce Duncan | Director of Strategic Solutions
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
You don't want to go to api_authenticate or deal with tokens since this is client side and you don't want to expose that information publicly on your site.
Everyone on the internet would be an easy solution though.
Chayce Duncan | Director of Strategic Solutions
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
Technically yes - but I'm not clear if that counts against the license
When you add a user start typing 'Everyone' and if your realm is already set up for it it will populate everyone on the internet as an option
Chayce Duncan | Director of Strategic Solutions
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
When you add a user start typing 'Everyone' and if your realm is already set up for it it will populate everyone on the internet as an option
Chayce Duncan | Director of Strategic Solutions
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
The standard for a role / user like this is to set up a new role with basic permissions - and set their default access to view/modify to none for all tables - hide all the UI elements and toggle everything off in your app with one exception that the role should be able to 'add' in the target table you want records added to. That should do it
Chayce Duncan | Director of Strategic Solutions
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
Chayce Duncan | Director of Strategic Solutions
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
+10OK this worked! I modified all the permissions so the new user can only create a new entry. Any ideas on getting an auto-email generated? I can make an automation for the task function, but the email is the one I can't quite figure out in my head.
You set up a notification in the table where the web form just created a record, trigger would be when a record is created. You format from there.
+10I'm not sure I'm following what you're saying... I set up an automation to create the "call the customer" task, but how would I go about automatically sending a "thank you for your interest" email from Qbase? I don't know of any email triggers now.
You go to the QB table's settings... that the form just added a record to. In those table settings, you'll see Notifications. Add a Notification there, set it to run whenever a Record is created in that table.
The automation will essentially trigger that notification.
The automation will essentially trigger that notification.
To condense this - Ryan is saying that when your customer is submitting a new record from the website - that you just set up a basic Quick Base notification to send them back a response. This would be an 'open' email notification that would go to someone who is not a user.
The catch to this is that you will need to actually capture/log the persons email from the site. So when they're submitting via your website - one of your fields should be an email, and you log that to Quick Base. When the record is successfully added to your system - you fire off a notification to the email listed in that field, and you've got your 'thank you'
Chayce Duncan | Director of Strategic Solutions
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
The catch to this is that you will need to actually capture/log the persons email from the site. So when they're submitting via your website - one of your fields should be an email, and you log that to Quick Base. When the record is successfully added to your system - you fire off a notification to the email listed in that field, and you've got your 'thank you'
Chayce Duncan | Director of Strategic Solutions
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base
Let me look into that one... I think there's a setting that makes it open to all, but then it may require hard coding the email, which wouldn't work in this case obviously.
+10OK i found a small issue with this... it's not passing the address through from the web form to the record. I originally had "street address", "City", "St" fields (based on what the wizard generated), but I changed that to just a blanket "address" field because only the city and state were coming through... and now nothing comes in. Any ideas where to look? My address field is just 1 field, it generates a map with all the info.
+10i think i figured it out... the wizard pulled the generic field ID, instead of the specific street field ID.
Sign up
Already have an account? Login
Login to the community
Login with Quickbase US – quickbase.com Login with Quickbase EU – quickbase.eu
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.