Skip to main content

HTTP POST to a Durable Azure Function

POST to a Durable Azure Function.

Category: Ingest to Lakehouse | Tags: Ingestion

How it works

Run CUSTOMER Azure Function '<<AzureFunctionName>>'

To use this activity within the API, use an ActivityCode of POST-AZFUNC-DURABLE.

Available Connections​

TargetConnection:

Example JSON​

An example of what the Task Config would look like for a task using this activity. Some of these variables would be set at the group level to avoid duplication between tasks.

{
  "AzureFunctionName": "",
  "TargetConnection": "MY-TARGET-CONN"
}

Variable Reference​

The following variables are supported:

  • AzureFunctionBody (Optional) - The JSON Body to pass to the Azure Function. Optional. If not specified, the entire Config JSON will be sent to the Azure Function.

  • AzureFunctionName (Required) - Name of the Azure Function

  • ExtractControlVariableName (Optional) - For incremental loads only, the name to assign the Extract Control variable in State Config for the ExtractControl value derived from the Extract Control Query above.

  • ExtractControlVariableSeedValue (Optional) - The initial value to set for the Extract Control variable in State Config - this will have no impact beyond the original seeding of the Extract Control variable in State Config.

  • IsFederated (Optional) - Makes task available to other Insight Factories within this organisation.

  • Links (Optional) - NULL

  • MaximumNumberOfAttemptsAllowed (Optional) - The total number of times the running of this Task can be attempted.

  • MinutesToWaitBeforeNextAttempt (Optional) - If a Task run fails, the number of minutes to wait before re-attempting the Task.

  • TargetConnection (Optional) - Target connection to use.