Below is a list of Delivery Actions that can be applied to create Conditional Workflow Alerts and integrate report and data delivery after forms have been submitted. A conditional workflow alert or action is when a delivery event (email, forward, etc) is to happen as a result of content within the form. For example, the equipment being inspected requires maintenance. A conditional alert is created to deliver an email to the maintenance team only when maintenance is required.
Email Submitter – Send an email in the requested format/s to the user currently filling out the form in the app. This Action does not work when using web forms.
Email Users – Send an email to the indicated user/s in the designated format/s. You will also want to specify the email’s Subject and Body that gets sent to your users. You will want to separate recipients’’ email addresses with a comma.
Note - You can only use this action for users that are on your FastField account.
Email External – Send an email to the indicated email recipient/s in the designated format/s. You will also want to specify the email’s Subject and Body that gets sent to these recipients. You will want to separate recipients’’ email addresses with a comma. Please note that you can only use this action for users that are not on your FastField account.
Note - This will only work with external recipients only not with current users.
Email From Field – Send an email to an address contained within a field on your form. You can specify which field and (like other actions) which format you would like to receive the data from.
FTP – Send your form submissions in your desired format/s to your FTP server. You will need to add your server’s settings correctly.
SFTP – Send your form submissions in your desired format/s to your SFTP server. You will need to add your server’s settings correctly.
HTTP/HTTPS – Post your form submissions in your desired format/s through an HTTP request. You will need to add your server’s settings correctly.
Send To Dropbox – Connect to your Dropbox account and send your submissions to a folder.
Send To Google Drive – Connect to your Google Drive and send your submissions to a folder.
Send To SQL Server – Send your data to an SQL Server. Make sure that your form is finalized before mapping to your SQL Server database tables. If you make changes to your form after you have mapped to your tables, you will have to add/edit database columns manually. This can also result in data not being inserted into your tables if your form changes and your mappings have not been updated.
Send To Power BI – Send your data to Power BI. Make sure your form is finalized before mapping to Power BI Datasets. In most cases, if you later decide to update your form, it would be better to create a new Dataset.
Send To AWS S3 – Send data directly to your Amazon S3 buckets. You will need to enter your keys and region and specify which bucket you wish to send to.
Send Files To SharePoint – This Integration will allow you to send Form result PDFs, CSV, JSON, and other files directly to SharePoint Folders and Subfolders. Your form should be finalized before mapping to your SharePoint Document Library (folder).
Send Form To SharePoint – This Integration will allow you to map Form result fields to SharePoint lists. Your form should be finalized before mapping to your SharePoint Document Library and Lists.
Dispatch New Form (Beta) – This will allow you to populate and dispatch a new form once your form has been submitted.
Push Notification (Beta) – This will allow you to send a Push Notification to a user once the form has been submitted.
Forward – Send an editable version of your submitted form to other users on your account to edit and submit.
Forward Cycle – This action will allow users to specify who they want to forward the form to and will repeat until the form is marked "complete." Forward Cycle actions help open-ended Review and Approval processes, or if you don’t know how many times you will need to pass a form back and forth.