Output Connectors & Actions

Output Connectors define what is done with the results of the device types. There are several options to choose from:

• Akenza DB

  • Storing the data in the akenza database

• Mailgun

  • Sending parts of the data in an e-mail to a recipient

• Webhooks

  • Forwarding the data to a 3rd party system for further processing or storing

Additional connectors can simply be added by clicking on "Add connector". Once an output connector is chosen, a specific topic (eg. Occupancy, Temperature) can be further selected. The output connector will then only trigger the action if a sample with this topic is emitted by the device type. Only available topics values will be shown in the dropdown. If no Topic is selected all data samples will trigger the output connector.

Akenza DB

The output connector to the akenza database ensures, that all data passing through this data flow is saved in the database of akenza and thereby becomes available via the API.

Mailgun

The mailgun output connector can be used to forward parts of the received sample to a specified recipient.

With the use of the templating syntax parts of the sample can be accessed and sent in the subject or message of the email. Formatting options for the message are limited.

Webhooks

The webhook output connector can be used to invoke any third-party REST API to the sample in the request body.

Note: The whole sample will be forwarded to the invoked endpoint. Make sure the target API is trusted. Avoid sensitive data in the sample.

The HTTP method, multiple custom headers, content type and authentication method can easily be specified. Authentication flows (e.g. Oauth2) are not yet supported.

The action section is used to define the action which is taken after the condition in the logic section evaluated to true.

Once the rule is saved, the actions can be re-used in other rules.