Azure Functions Trigger Outputs and Integrations

George Alpizar
George Alpizar
  • Updated

Overview

This output type streams notifications and alerts to an Azure endpoint.


Review Parameters

Review the following parameters that you can configure in the Edge Delta App:

Visual Editor YAML Description
Name name

Enter a descriptive name for the output or integration.

For outputs, this name will be used to map this destination to a workflow.

The following parameter is required. 

Review the following example: 

name: azure-functions-output
Integration integration_name

This parameter only appears when you create an individual output.

This parameter refers to the organization-level integration created in the Integrations page. If you enter this name, then the rest of the fields will be automatically populated.

If you need to add multiple instances of the same integration into the config, then you can add a custom name to each instance via the name field. In this situation, the name should be used to refer to the specific instance of the destination in the workflows.

The following parameter is optional. 

Review the following example: 

integration_name: ed-alert-azurefunctions
Not applicable type

Enter azurefunctions.

The following parameter is required. 

Review the following example: 

type: azurefunctions
Endpoint endpoint

Enter the Azure Functions FaaS endpoint.

The following parameter is required. 

Review the following example: 

endpoint: "https://XX.azurewebsites.net/XX/XX"
Custom Headers and Custom Fields custom_headers and custom_fields

This parameter is used to customize the notification content.

If you do not want to use default fields in a notification, then you can create custom headers and fields.

To learn more, see Review Notify Content Parameters.

This parameter is optional. 

Payload

notify_content:

 advanced_content

A payload is JSON object that is used to define metadata about the message.

In the app, when you click Advanced Mode, you can update a pre-populated JSON file. 

You are responsible for ensuring the validity of the JSON object. 

Additionally, configurations you make in Advanced Mode will override all other configurations, including custom_fields, title, and disable_default_fields.

To learn more, see Review Template Values for Trigger Payloads.

This parameter is optional. 

Review the following example: 

notify_content: 
advanced_content: |
{
"foo": "bar",
}

Review Sample Configuration

The following sample configuration displays an output without the name of the organization-level integration:

    - name: azure-functions-integration
      type: azurefunctions
      endpoint: "https://XXXXXXXXXX.azurewebsites.net/XXXX/XXXXXX"
      notify_content:
        advanced_content: |
          {
            "foo": "bar",
          }

 

Share this document