Add documentation floe:// and manageiq:// methods

Author: agrare

managing_providers/_topics/embedded_workflows.md

@@ -159,7 +159,7 @@ You can create and use embedded workflows as needed to not only change parts of
 
 Workflows must be authored in Amazon State Languages (ASL) format. As part of authoring a workflow, you (or your users) can build container images that are able to perform any tasks that are required in any language that you like. You can use these images during Task states in your workflows.
 
-1. Define the code for the workflow. If your workflow requires the use of any credentials or parameters to be specified, ensure that they are passed in the code.
+* Define the code for the workflow. If your workflow requires the use of any credentials or parameters to be specified, ensure that they are passed in the code.
 
    Within the workflow code, you need to specify the states that your workflow requires, including any next steps. For `Task` type steps in the workflow, a docker container is called. The container defines what happens for that Task state. For example, a docker container can run to clone a template. If your states require parameters or credentials, you can specify them in your state definitions.
 
@@ -174,12 +174,40 @@ Workflows must be authored in Amazon State Languages (ASL) format. As part of au
       - ItemReader
       - ResultWriter
 
-2. Build the docker containers that are required for the workflow.
+* Build the docker containers that are required for the workflow.
 
    When you have the code for your task resource written, you need to bundle it into a docker image. You can bundle the code by creating a standard [Dockerfile](https://docs.docker.com/engine/reference/builder/) and building the image (https://docs.docker.com/engine/reference/commandline/build/). Then, you can push the image to a [registry](https://docs.docker.com/engine/reference/commandline/push/), which makes the image available to be used by {{ site.data.product.title_short }}. When you have pushed your images to an image registry, you can add the registry to {{ site.data.product.title_short }}.
 
   Pull secrets for containers are used differently between appliances and the OpenShift Container Platform (OCP). These differences are outlined in the following sections.
 
+* Use "builtin" runner methods from floe or manageiq
+
+  In addition to the `docker://` runner which can run any container you want, there are also builtin runner methods for some common tasks like executing an http call or sending an email.
+
+  * floe://http - Execute any HTTP action
+
+    Parameters:
+    * Method
+    * Url
+    * Headers
+    * QueryParameters
+    * Body
+    * Ssl
+    * Options
+    * Proxy
+  * manageiq://email - Send an email using the configured SMTP server
+
+    Parameters:
+    * To
+    * From
+    * Subject
+    * Cc
+    * Bcc
+    * Body
+    * Attachment
+  * manageiq://embedded_ansible - Execute an ansible playbook with EmbeddedAnsible
+  * manageiq://provision_execute - Execute an MiqProvision task
+
 #### Running an Embedded Workflow on Appliances
 
    * On appliances, `podman` is used to execute the container so use [podman login](https://docs.podman.io/en/stable/markdown/podman-login.1.html) as the `manageiq` user.