Overview of the default workflow types

There are are several built-in workflow types that can be used to extend the functionality of your form. Here is an overview:

Change Record State

This workflow is used to automatically approve or delete a record once it is submitted.

Configure some words that you want to check for, and select whether these words should trigger a deletion or an approval.

Post as XML

This workflow is used to post the form as XML to a specified URL.

Besides a name, the following configuration can be set:

• URL (required)
• Method
• XsltFile - used to transform the XML
• Headers - map the needed files
• User and password

Save as an XML file

This workflow will save the result of the form as an XML file by using XSLT. In the configuration you can configure the following settings:

• Path - where to save the XML file (required)
• File extension (required)
• XsltFile - used to transform the XML

Save as Umbraco Content Node

This workflow gives you the option to save a forms submission as a new content node.

First of all, you need to choose a Document type and match the fields in the form with the properties on the selected Document Type. You can also choose to set a static value to fill in the properties.

In the example above, a Document Type called 'Blogpost' is selected to be used for creating the new content node. Furthermore, the value from the 'Name' field will be added as the 'Node Name' property in the new content node, and the value from the 'Email' field will be used for the 'Content' property.

Other configuration:

• Publish - choose whether to publish the node on submission
• Where to save - choose a section in the content tree where this new node should be added

Send email

Send the result of the form to a specified email address.

The following settings can be configured:

• Email (required)
• SenderEmail - also configurable in Config/umbracosettings.config
• Subject of the email
• Message (required)
• Attachment - specify whether file uploads should be attached to the email

Send email with template (Razor)

This workflow will use a template to send the results of the form to a specified email address.

You can create your own custom Razor templates to be used to send out emails upon forms submission. Read more about how to create these templates in the Email Templates article.

The following settings can be configured:

• Email (required)
• SenderEmail - also configurable in Config/umbracosettings.config
• Subject (required)
• Email Template - specify which template you want to use (required)
• Attachment - specify whether file uploads should be attached to the email

Send form to URL

This workflow sends the form to a url, either as a HTTP POST or GET.

The following settings can be configured:

• URL (required)
• Method - POST, GET, PUT or DELETE (required)
• Standard Fields - optionally include and map standard form information such as name and page URL
• Fields - map the needed fields
• User and password

When mapping fields, if any are selected, only those chosen will be sent in the request to the configured URL. If no fields are mapped, all will be sent.

The receiving endpoint will be able to extract the form fields and values from the querystring or form collection when the method used is set to GET or POST respectively.

Send XSLT transformed email

Send the result of the form to an email address and have full control over the email contents by supplying an xslt file.

The following settings can be configured:

• Email (required)
• SenderEmail - also configurable in Config/umbracosettings.config
• Subject (required)
• XSLT File - specify which file should be used to transform the content

Slack

This workflow lets you post the form data to a specific channel on Slack.

The following settings can be configured:

• API Token (required)
• Channel (required)
• Username (required)
• Avatar URL (required)