QuickBase Community Home

Can I send an e-mail to a QuickBase app to add a new record?

Can I send an e-mail to a QuickBase app to add a new record using data in the e-mail for certain fields in the record?

I've searched through the forum and the knowledgebase, but only find info on having Quickbase send e-mails out.  This would be the reverse.  Don't know if it is possible or not.


Thanks in advance.


    If I were you I would require the users to submit a HTML form and not support email. An email message describing  the support request would not have any individual fields and would probably consist of just one large narrative blob of text. The email request would have to be parsed into fields by the help desk person to work its way into your QuickBase application. Just require the user to directly submit an HTML form and you won't have to worry about developing a PHP script or insuring that the email to QuickBase gateway is up and running 24/7 for occasional submissions.


      Sure you can! If you send email to the following address:


      with a message body indicating the URL you wish to to view by email you can cause the record to be added as a "side effect" of retreiving the document:

      GET https://www.quickbase.com/db/DBID?act=API_AddRecord&_fnm_text=foo&_fnm_number=3

      In a few seconds you will get back an email with text such as the following and sooner than that you record will have been added to your application:

      API_AddRecord 0 No error 7 1260298912512

      This is basically the XML response of the API_AddRecord call converted to plain text.

      You can read all about www4mail here http://www.www4mail.org/ however, the technology is long dead and represents a historical oddity in the development of the web when modems were bleeding edge  technology and users found they had email access without web access.

      If you really want to use email to create QuickBase records the solution for this problem today is to write a short PHP program that will serve as an email to web gateway. However, I would suggest you rethink your process as there are better ways to accomplish this if you want to use a mobile device to add records to a QuickBase application.


        Thanks for the info Dan.  Very helpful as a start. 

        Allow me to explain why I'm asking.  I'm part of an IT team for a medium sized company.  We use QuickBase for various things, including using it as our IT help desk tracking system.  We have a form we created on our corporate intranet that allows our employees to submit an IT request for support, which adds a new record into our QuickBase IT help desk app. 

        However, we also let people send in requests for help to a particular e-mail address.  We try to steer people to the form so that it get's into QuickBase as efficiently as possible, but occasionally people do send an e-mail to the support address, and then we have to go create the new record in QuickBase for them.

        We thought we might be able to save a little time if we could figure out a way to auto-forward those e-mail requests to QuickBase and have it create the new record, even though it probalby wouldn't have much info in it at first. 

        So, given that, would you still say that creating our own program (say in PHP, or we would probably prefer, Ruby) to take said e-mail and use the API AddRecord call to create the new record is the best way to go?


          If you need to retain the email functionality, rather than Dan's suggestion of an HTML form, you can see if SendToQuickBase will meet your needs.  It's a tool which we use to capture data from email notifications and then populate quickbase tables with data from the emails.  www.sendtoquickbase.com


            Another option, if you use Outlook and have the patience to follow the steps -



              Contribute an answer

              People come to QuickBase Community for help and answers—we want to let them know that we're here to listen and share our knowledge. We do that with the style and format of our responses. Here are five guidelines:

              1. Keep it conversational. When answering questions, write like you speak. Imagine you're explaining something to a trusted friend, using simple, everyday language. Avoid jargon and technical terms when possible. When no other word will do, explain technical terms in plain English.
              2. Be clear and state the answer right up front. Ask yourself what specific information the person really needs and then provide it. Stick to the topic and avoid unnecessary details. Break information down into a numbered or bulleted list and highlight the most important details in bold.
              3. Be concise. Aim for no more than two short sentences in a paragraph, and try to keep paragraphs to two lines. A wall of text can look intimidating and many won't read it, so break it up. It's okay to link to other resources for more details, but avoid giving answers that contain little more than a link.
              4. Be a good listener. When people post very general questions, take a second to try to understand what they're really looking for. Then, provide a response that guides them to the best possible outcome.
              5. Be encouraging and positive. Look for ways to eliminate uncertainty by anticipating people's concerns. Make it apparent that we really like helping them achieve positive outcomes.

              Similar questions other people found helpful: