Trigger types (HTTP, Timer, Blob, Queue) in Azure - Step-by-Step Execution

Process Flow - Trigger types (HTTP, Timer, Blob, Queue)

Event Occurs

↓

Trigger Type?

↓

Run Function with Event Data

↓

Function Executes

↓

Output or Side Effect

When an event happens, Azure Functions check the trigger type (HTTP, Timer, Blob, or Queue) and run the function with the event data.

Execution Sample

Azure

Trigger: HTTP
Request: GET /api/hello
Function: Returns 'Hello World!'

This function runs when an HTTP GET request is received and returns a greeting.

Process Table

Step	Trigger Type	Event	Function Action	Output
1	HTTP	GET /api/hello	Function runs with HTTP request data	Returns 'Hello World!'
2	Timer	Timer fires at 12:00	Function runs on schedule	Logs 'Timer triggered'
3	Blob	New blob uploaded 'image.png'	Function runs with blob data	Processes and stores metadata
4	Queue	Message added to queue	Function runs with queue message	Processes message and deletes it
5	-	-	-	No event, no function run

💡 Execution stops when no trigger event occurs.

Status Tracker

Variable	Start	After HTTP	After Timer	After Blob	After Queue	Final
Trigger Event	None	HTTP Request	Timer Event	Blob Upload	Queue Message	None
Function State	Idle	Running	Running	Running	Running	Idle
Output	None	'Hello World!'	'Timer triggered'	Metadata stored	Message processed	None

Key Moments - 3 Insights

Why does the function run only when a trigger event happens?

Because Azure Functions are event-driven, they stay idle until a trigger event occurs, as shown in execution_table rows 1-4. Row 5 shows no event means no run.

How does the function know what data to use for each trigger?

Each trigger type passes specific event data to the function, like HTTP request info, timer schedule, blob content, or queue message, as seen in the 'Event' and 'Function Action' columns in the execution_table.

Can multiple trigger types run the same function?

Yes, but each trigger event runs the function separately with its own data, shown by different rows in the execution_table where the function runs for HTTP, Timer, Blob, and Queue triggers.

Visual Quiz - 3 Questions

Look at the execution_table, what output does the function produce when a new blob is uploaded?

A 'Hello World!'

B 'Timer triggered'

C Processes and stores metadata

D Processes message and deletes it

💡 Hint

Check the row where Trigger Type is 'Blob' in the execution_table.

At which step does the function run because of a timer event?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look for 'Timer' in the Trigger Type column of the execution_table.

If no event occurs, what is the function state according to variable_tracker?

A Idle

B Error

C Running

D Paused

💡 Hint

Check the 'Function State' row under 'Final' column in variable_tracker.

Concept Snapshot

Azure Functions run when triggered by events.
Common triggers: HTTP request, Timer schedule, Blob storage change, Queue message.
Each trigger passes event data to the function.
Function runs only when triggered, otherwise idle.
Outputs depend on trigger and function logic.

Full Transcript

Azure Functions use triggers to start running. When an event happens, like an HTTP request, a timer firing, a new blob uploaded, or a message added to a queue, the function runs with data from that event. The function stays idle if no event occurs. Each trigger type provides different data to the function, and the function's output depends on the trigger and its code. This event-driven model helps functions run only when needed.