...
Automatically forward emails with a summary to the responsible internal team
Scan any email sent to a given inbox such as info@mycompany.tld for example, find out the intention of the sender, then forward the email to the internal team such as support, sales, … which can handle the request. The AI can find out the type of request, whether it is a support request, an order request, a question regarding an invoice or any other type just by writing an advice to the AI and without any programming. It can also detect and extract all required data such ascustomerId
,invoiceNumber
and more from the sender’s email. Furthermore, it can also create a short summary about what the core intent of the sender is to make it easier for the internal team to process the request.Automatically validate and start an internal workflow by email
Scan any email sent to a given inbox such as invoice@mycompany.tld for example and if this email matches to an existing workflow, extract all variables required for this workflow from the email, start the workflow and pass these variables along with it. For example to start an accounts payable workflow based on an given payable invoice. The AI can validate whether all required data exist and is valid in order to start the workflow.Automatically call endpoints of other systems by email
Scan any email sent to a given inbox such as info@mycompany.tld for example and if this email is related to a service, offered by a third party system which provides an remote API, call this remote API (for example REST) and pass along parameters extracted from the email. For example create a new ticket on an external ticket system.
Using command ai.
...
command.detect
In order to integrate Text-to-Command functionality into your automation pipelines, you can use the command ai.intentcommand.detect
. It will
take a text, for example like an email as input,
will apply the given AI instructions on this text and
finally will select a command to be executed and optionally executes it.
Here is a first example how this could look like in an automation pipeline:
Code Block | ||
---|---|---|
| ||
body: | From: customer@somedomain.tld Subject: I have a problem with your product Hello, I have a big problem with your product and need support. My customer id is 123456. Cheers, Valued Customer pipeline: - ai.command.detect: runDetectedCommand: truefalse advice: intentCandidates: - intentId: "forwardToSupport" instruction: "Use this intent in case the sender needs product support." targetCommand: "mail.send" params: to: value: "support@internal.tld" from: instruction: "The email address of the sender." subject: instruction: "Use the subject of the sender's email." message: instruction: "Use the message of the sender's email." - intentId: "forwardToInfo" instruction: > Use this intent in case the sender's intent could not be detected. targetCommand: "mail.send" params: to: value: "info@internal.tld" from: instruction: "The email address of the sender." subject: instruction: "Use the subject of the sender's email." message: instruction: "Use the message of the sender's email." |
...
Each intent has an instruction
in order to instruct the AI about the criteria to select this intent. In case such an intent is selected by AI, there is the targetCommand
field defining the name of the command which must be called. In this example this is the mail.send
command.
The parameter runDetectedCommand
defines whether the command should directly be executed (true
) or the intent JSON should be simply returned for further processing (false
).
Intent Parameters
The params
section on each intent lists the parameters required to call the command. For the mail.send
command these are for example the parameters to
, from
, subject
and message
. The values of these parameters can be fixed, templated or can be detected by the AI.
...