Courier for Quickbase
Configurations table in the Juiced QB Courier Quickbase Application
QB Courier has been historically managed from our Quickbase portal app that you may have been given access to.
If you have not, that means you have an account in the Extensions Portal, and you manage your configurations there. Learn more about the Extensions Portal.
If you previously used the QB Courier app, you can still configure and manage your QB Courier extension within this Quickbase Extensions-owned Quickbase app.
Important
All new clients must configure from within the Extensions Portal starting in 2025.
The following section shows screenshots from our QB Courier application. The configuration record ID and the processing mode, Triggered, are shown in the email message below.
Application information for the Courier email
The Email Message Info section includes all your typical email fields such as the address you want it delivered to (this can come from a report in Quickbase), who you want copied on the email, and who the email is from.
Lastly, the Activity Log shows you each time the Courier configuration has run and includes important details such as the run date, the processing mode, how many emails were sent, and the processing details that show whether there were any errors.
This highlights a few of the capabilities you have when creating an email configuration in QB Courier. If you are interested in upgrading to the Extensions Portal for more intuitive email creation, learn more about the Extensions Portal.
Configuration table fields
Client Information Section | |
|---|---|
Client Company | Your Company Name, as set up in QB Courier |
Client E-mail | Contact email address for your company. Error messages are sent to this address. |
Client User(s) | The Quickbase user IDs you use to manage your QB Courier configuration records. |
Account URL | All accounts have a unique account URL—xxx.quickbase.com. You must enter it here. |
Processing Details | |
Status | When first setting up your configuration, you should select Test Mode, which is the default and should be changed to Enabled once you have concluded your testing. Enabled—this means the configuration is live and processes based on the processing mode. Test Mode—this means the configuration runs but only one email is sent after the process completes. That email is sent to the Copy email address only, and it summarizes what would be processed if the configuration were set to Enabled. No fields are updated on the records to be processed during test mode. Disabled—the configuration is not executed. |
Run Status | Graphical representation of the Status field's value. Enabled: Green Test Mode: Yellow Disabled: Red |
Processing Mode | Scheduled: Runs based on the Processing Frequency and processes only records that meet the filtered selection criteria in the report query in your app. On Demand: Similar to Scheduled mode, but you can execute it on demand instead of waiting for the daily process to run. Trigger: Emails sent based solely on the Quickbase app event taking place—for example, a record is added, modified, or deleted. |
Processing Frequency | For Scheduled processing only: Daily—Runs every day. Weekly—You can choose the days of the week to process. Monthly—You can choose the day of the month to process. |
Configuration Info | |
Config Name | The name you choose for this configuration should be meaningful, so you can locate it in the future. |
App DBID | The Application ID assigned by Quickbase. |
App Token | This is required only if your Quickbase app has tokens enabled. |
Table DBID | The database ID of the Quickbase table that you are connecting to this configuration. |
Link to table | This is a link to the table in your app that contains the records to be processed by this configuration. Used to verify that you have entered the Table DBID field value correctly. |
Log Activity | To log the execution of the configuration in the Activities table. We recommend always enabling this feature. |
Data Selection | |
Report Query ID | For Scheduled and On Demand configurations, you must create a Quickbase report (query) in your app to filter the specific records you want to include in the email process. Provide the query ID for that report in this field. The record ID# field must be selected as a displayed column in this report. All fields that are to appear in the subject and body of the email message must be included on this report. The query ID (qid) can be found in the URL of the query. |
Link to Report | This is a link to the report in your app that you set up to filter the records to be processed by this configuration. Only displays for Scheduled and On Demand configurations. |
Email Message Info | |
Sending Email Address | When QB Courier sends the email messages, this is the email address the messages come from. The default value is our email address: qbcourier@quickbaseemail.com. You can enter an email address here. You can take actions including:
|
From Field | The Quickbase field ID for the From email address. If you have an email address field on the table being processed and you want that value used as the From address, enter the field ID here. If the email address is not found in the FID provided, the email is sent by QBCourier@quickbaseemail.com. |
From Email | An actual email address that you want the message to look like it was sent from. This appears in the email FROM field. If the recipient of the email message clicks reply, the reply-to address is this email address. |
Email Field | The Quickbase field ID of the field that contains the email addresses the message should be sent to. They appear in the To field of the email. The field can be an email type field or a formula text field with: |
Update Field | If you want to record the date the email was generated or sent in the Quickbase table it was generated from, create a date/time field in that table and provide that field's Quickbase field ID here. |
Copy Email Field | The Quickbase field ID for the CC email address. The field can be an email type field or a formula text field with: |
Copy Email Field from Related Table | If you have a subtable (child table) for your CC email addresses that is related to the master table, you must provide the related table DBID, colon (:), field ID of the relationship to the master table, colon (:), field ID of the CC email address—for example, bg334x62r:6:13. |
BCC Email Field | The Quickbase field ID for the BCC email address. The field can be an email type field or a formula text field with: |
Copy Email | An actual email address that you want CC'd—for example, info@anyemaildomain.com—this is required when in test mode. You can include multiple email addresses, separated by ";". |
BCC Email | An actual email address that you want BCC'd. You can include multiple email addresses, separated by ";". |
Subject | The email subject. You can use the Quickbase field labels to include dynamic values—for example, Please confirm order contents and quantities for order# [Customer Order]. |
Message | The body of the email in HTML text. You can use the Quickbase field labels to include dynamic values. |
Subject/Message CLIST | For Triggered configurations only. You must provide the Quickbase field IDs for all fields used in the subject and body of the email. The field IDs must be separated by a dot—for example, 6.32.107. This is not required for Scheduled and On Demand because the report query is used to identify fields to retrieve from Quickbase. |
File(s) to Attach | None—You do not want to include attachments. Yes, from file attachment field(s)—If you want your email to include file attachments from Quickbase, provide the field ID for the file attachment from the master table. If you want to use more than one file attachment field, enter a list of FIDs separated by a period—for example, 10.15.20. Yes, from Amazon S3—If you want your email to include file attachments stored in Amazon S3, provide the field ID for the s3key field. If you want to use more than one s3key field, enter a list of FIDs separated by a period—for example, 10.15.20. |
Field id(s) to Attach or S3Keyfid | Enter the field IDs for either the file attachment fields or the s3 keyfids here. |
S3KeyFid(s) from Related Table | The format of this field is: dbid: field ID of a related field:field ID of S3 folder key (leave blank if there isn't any):field ID of S3 key field:qry criteria. For example: bbbbbbbbb:25:22:9: dbid—The dbid of the child table. |
S3KeyFid(s) from ANY Table | The format of this field is: dbid:field to match:value to match:field ID of S3 folder key (leave blank if there isn't any):field ID of S3 key field:qry criteria. For example: bbbbbbbbb:13:9::9:qry={'29'.EX.'true'} dbid—The dbid of the child table. Value to match—You can add a value surrounded by single quotes or enter a field ID of the field from the master table. S3 folder fid—If the files are stored in a specific folder in S3, provide the field ID of the S3 folder. |
Use your own mail server | If you want the email messages sent directly from your mail server or account, you need to provide us with the mail server information. |
Mail Server Info (If you choose to use your own email address you need to provide the following) | |
Mail Server Name | Your mail server domain—for example, mail.yourmaildomain.com. |
Mail User Name | The user name or user ID used to authenticate into the mail server. |
Mail Password | The password for that user name or user ID. |
Mail Port | If your mail server requires outgoing mail to use a port other than the default port 25, enter that port number here. |
Additional File Attachments | |
File Attachment | You may have up to 5 static email attachments, such as an image or a blank W-9 form. |
Notes | |
Description | This is a detailed explanation of the email configuration. |
Activities | |
All email activity is recorded in this section, which includes: Run date and time Emails to be sent# Emails sent# Records Bypassed# Records Updated# Status Error Message | |
Triggered configurations
An email notification needs to be created in your Quickbase app to execute a Triggered Courier configuration record. It should be designed based on the action you want to occur in your table that triggers the Courier for QuickBase configuration record to be processed.
Example:
Overview of our Demo Triggered Configuration
Our Triggered Courier configuration record is designed to send an email to the email address in the Email the Proposal to: field within our Proposals table in our DEMO: QB Signature and QB Courier Quickbase app. It also includes the Proposal PDF file as an attachment to the email. We want the email sent when the Proposal record is modified by Exact Forms Plus. We also only want to send an email if the email-to field has a value in it.
Here is a sample of what our email notification looks like in our DEMO: QB Signature and QB Courier app.
Here is what our Courier for QuickBase configuration record looks like:
