EmailOperator for notifications in Apache Airflow - Step-by-Step Execution

Process Flow - EmailOperator for notifications

Start DAG run

↓

Trigger EmailOperator

↓

Prepare email content

↓

Connect to SMTP server

↓

Send email

↓

Email sent successfully?

No→Log error

Yes↓

End EmailOperator task

This flow shows how Airflow's EmailOperator sends an email notification during a DAG run, connecting to SMTP and handling success or failure.

Execution Sample

Apache Airflow

from airflow.operators.email import EmailOperator
email_task = EmailOperator(
    task_id='send_email',
    to='[e-mail]',
    subject='DAG Notification',
    html_content='<p>Your DAG has completed.</p>'
)
email_task.execute(context={})

This code creates and runs an EmailOperator task that sends an email notification with a subject and HTML content.

Process Table

Step	Action	Evaluation	Result
1	Start EmailOperator execution	N/A	Ready to send email
2	Prepare email content	to='[e-mail]', subject='DAG Notification', html_content='<p>Your DAG has completed.</p>'	Email content ready
3	Connect to SMTP server	SMTP server reachable?	Connection established
4	Send email	Send email via SMTP	Email sent successfully
5	Confirm email sent	Email delivery status	Success confirmed
6	End EmailOperator task	N/A	Task completed

💡 Email sent successfully, task ends normally

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
to	''	'[e-mail]'	'[e-mail]'	'[e-mail]'
subject	''	'DAG Notification'	'DAG Notification'	'DAG Notification'
html_content	''	'<p>Your DAG has completed.</p>'	'<p>Your DAG has completed.</p>'	'<p>Your DAG has completed.</p>'
smtp_connection	None	None	Connected	Closed after send
email_status	None	None	Sent	Confirmed

Key Moments - 3 Insights

Why does the EmailOperator need SMTP server connection?

Because the EmailOperator sends emails by connecting to an SMTP server, as shown in step 3 of the execution_table. Without this connection, the email cannot be sent.

What happens if the SMTP server is not reachable?

If the SMTP server is unreachable, the EmailOperator will fail to send the email and log an error, as indicated by the 'No' branch in the concept_flow after 'Email sent successfully?'.

Why do we provide 'html_content' instead of plain text?

The EmailOperator supports HTML content to allow formatted emails. In the execution_table step 2, 'html_content' is prepared to send a nicely formatted message.

Visual Quiz - 3 Questions

Look at the execution_table, what is the email_status variable after step 4?

A None

B Sent

C Connected

D Confirmed

💡 Hint

Check variable_tracker column 'After Step 4' for 'email_status'

At which step does the EmailOperator confirm the email was sent successfully?

A Step 5

B Step 3

C Step 4

D Step 6

💡 Hint

Look at execution_table row with 'Confirm email sent'

If the SMTP server is unreachable, which part of the concept_flow will be triggered?

A Trigger EmailOperator

B Prepare email content

C Log error

D End EmailOperator task

💡 Hint

Refer to concept_flow decision after 'Email sent successfully?' with 'No' branch

Concept Snapshot

EmailOperator sends emails in Airflow DAGs.
Set 'to', 'subject', and 'html_content' to define the email.
It connects to SMTP server to send the email.
If SMTP fails, it logs an error.
Use execute() to run the task in code.

Full Transcript

The EmailOperator in Airflow sends email notifications during DAG runs. It starts by preparing the email content including recipient, subject, and HTML body. Then it connects to the SMTP server to send the email. If the connection and sending succeed, the task completes successfully. If the SMTP server is unreachable, the operator logs an error and fails. Variables like 'to', 'subject', and 'html_content' hold the email details, while 'smtp_connection' tracks the connection state and 'email_status' tracks sending status. This flow ensures notifications are sent reliably during workflows.

Practice

1. What is the primary purpose of the EmailOperator in Airflow?

easy

A. To store logs of task executions

B. To schedule tasks at specific times

C. To monitor CPU usage of Airflow workers

D. To send emails automatically from Airflow tasks

Solution

1. Step 1: Understand EmailOperator's role

   EmailOperator is designed to send emails triggered by Airflow tasks.

2. Step 2: Compare with other options

   Scheduling tasks, storing logs, and monitoring CPU are handled by other Airflow components, not EmailOperator.

3. Final Answer:

   To send emails automatically from Airflow tasks -> Option D

4. Quick Check:

   EmailOperator = send emails [OK]

Hint: EmailOperator is for sending emails, not scheduling [OK]

Common Mistakes:

• Confusing EmailOperator with scheduling operators
• Thinking EmailOperator manages logs or monitoring
• Assuming EmailOperator runs tasks instead of notifying

2. Which of the following is the correct way to import EmailOperator in an Airflow DAG file?

easy

A. from airflow.operators.email_operator import Email

B. from airflow.operators.email import EmailOperator

C. from airflow.operators.email_operator import EmailOperator

D. import EmailOperator from airflow.operators.email_operator

Solution

1. Step 1: Recall correct import path

   The correct import path for EmailOperator in Airflow is from airflow.operators.email_operator import EmailOperator.

2. Step 2: Check other options for syntax or naming errors

   from airflow.operators.email import EmailOperator uses wrong module name (missing '_operator'); from airflow.operators.email_operator import Email imports wrong class name; import EmailOperator from airflow.operators.email_operator uses invalid Python import syntax.

3. Final Answer:

   from airflow.operators.email_operator import EmailOperator -> Option C

4. Quick Check:

   Correct import = airflow.operators.email_operator [OK]

Hint: Use 'from airflow.operators.email_operator import EmailOperator' [OK]

Common Mistakes:

• Using wrong module path like email
• Incorrect import syntax like 'import X from Y'
• Confusing class name with module name

3. Given this Airflow task using EmailOperator:

email_task = EmailOperator(
    task_id='send_email',
    to='[e-mail]',
    subject='Test Email',
    html_content='Hello from Airflow!',
    dag=dag
)

What will happen when this task runs successfully?

medium

A. The task will send an email but with empty content

B. An email with subject 'Test Email' is sent to [e-mail]

C. No email is sent because 'to' is not a list

D. The task will fail because html_content is missing

Solution

1. Step 1: Analyze EmailOperator parameters

   The task specifies 'to' as a string email address, 'subject', and 'html_content' correctly.

2. Step 2: Understand EmailOperator behavior

   EmailOperator accepts a string or list for 'to' and sends the email with given subject and content.

3. Final Answer:

   An email with subject 'Test Email' is sent to [e-mail] -> Option B

4. Quick Check:

   Valid params = email sent [OK]

Hint: Single string 'to' is valid for EmailOperator [OK]

Common Mistakes:

• Thinking 'to' must be a list
• Assuming html_content is required to be a file
• Believing task fails without attachments

4. You wrote this EmailOperator task but it fails with an error:

email_task = EmailOperator(
    task_id='notify',
    to=['[e-mail]'],
    subject='Alert',
    html_content='Check this alert',
    dag=dag
)

What is the most likely cause of the failure?

medium

A. SMTP server is not configured in Airflow settings

B. The 'to' parameter must be a string, not a list

C. Missing 'from_email' parameter in EmailOperator

D. The 'subject' parameter cannot contain spaces

Solution

1. Step 1: Check EmailOperator parameters

   The 'to' parameter accepts a list, and 'subject' with spaces is valid.

2. Step 2: Identify common failure cause

   EmailOperator requires SMTP server setup in Airflow config; missing this causes failure.

3. Final Answer:

   SMTP server is not configured in Airflow settings -> Option A

4. Quick Check:

   SMTP setup missing = failure [OK]

Hint: Check SMTP config if EmailOperator fails [OK]

Common Mistakes:

• Assuming 'to' cannot be a list
• Thinking the 'subject' parameter cannot contain spaces
• Thinking 'from_email' is mandatory parameter

5. You want to send an email notification only when a task fails using EmailOperator. Which Airflow feature should you use to trigger the email task only on failure?

hard

A. Set trigger_rule="one_failed" on the EmailOperator task

B. Set trigger_rule="all_success" on the EmailOperator task

C. Use depends_on_past=True on the EmailOperator task

D. Set email_on_failure=False in the DAG definition

Solution

1. Step 1: Understand trigger_rule usage

   Setting trigger_rule="one_failed" makes the task run only if any upstream task fails.

2. Step 2: Evaluate other options

   all_success runs only if all succeed; depends_on_past controls task dependency on previous runs; email_on_failure is a DAG-level flag, not for task trigger.

3. Final Answer:

   Set trigger_rule="one_failed" on the EmailOperator task -> Option A

4. Quick Check:

   Trigger on failure = trigger_rule one_failed [OK]

Hint: Use trigger_rule='one_failed' to run on failure only [OK]

Common Mistakes:

• Using trigger_rule='all_success' for failure notification
• Confusing depends_on_past with failure triggers
• Misusing email_on_failure flag for task triggers