Edge Delta Azure Functions Triggers
2 minute read
Overview
This output type sends notifications and alerts to an Azure endpoint.
Example
- name: azure-functions-integration
type: azurefunctions
endpoint: "https://XXXXXXXXXX.azurewebsites.net/XXXX/XXXXXX"
notify_content:
advanced_content: |
{
"foo": "bar",
}
Parameters
name
Required
Enter a descriptive name for the output or integration.
For outputs, this name will be used to map this destination to a workflow.
name: azure-functions-output
integration_name
Optional
This parameter refers to the organization-level integration created in the Integrations page.
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 parameter. In this situation, the name should be used to refer to the specific instance of the destination in the workflows.
integration_name: ed-alert-azurefunctions
type: azurefunctions
Required
Enter azurefunctions.
type: azurefunctions
endpoint
Required
Enter the Azure Functions FaaS endpoint.
endpoint: "https://XX.azurewebsites.net/XX/XX"
custom_headers and custom_fields
Optional
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.
notify_content: advanced_content
Optional
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.
notify_content:
advanced_content: |
{
"foo": "bar",
}