Use SMTP Email Sender for Workflow Notifications with Python

Send a plain text or HTML email through your own SMTP account from an Apify run. Supports multiple recipients, CC/BCC, Reply-To, and file attachments.

1. Choose the data you need

Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.

2. Prepare a source-based input

This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.

The published schema does not supply an example for these required fields: smtpPassword, smtpUser. Supply them using the reference documentation before execution.

{
  "smtpHost": "smtp.gmail.com",
  "smtpPort": 587,
  "subject": "Test Email from Apify",
  "to": "recipient@example.com",
  "useTls": true
}

Download input.example.json and save your reviewed copy as input.json.

Field	Type	Required	Description
`to`	string	required	Recipient email address(es). Separate multiple addresses with commas. Example: 'user@example.com' or 'alice@example.com, bob@example.com'
`cc`	string	optional	Carbon copy recipient(s). Separate multiple addresses with commas.
`bcc`	string	optional	Blind carbon copy recipient(s). Separate multiple addresses with commas. BCC addresses are hidden from other recipients.
`subject`	string	required	Email subject line.
`text`	string	optional	Plain text email body. At least one of 'Plain Text Body' or 'HTML Body' must be provided. If both are set, email clients choose which to display.
`html`	string	optional	HTML email body. Takes priority over plain text in most email clients. Example: '<h1>Hello</h1><p>This is a test.</p>'
`replyTo`	string	optional	Reply-to email address. When recipients reply, their response goes to this address instead of the sender.
`attachments`	array	optional	File attachments as base64-encoded objects. Each item needs 'filename' (string) and 'data' (base64 string). Example: [{"filename": "report.pdf", "data": "base64data..."}]
`smtpHost`	string	required	SMTP server hostname. Examples: smtp.gmail.com, smtp.office365.com, smtp.mail.yahoo.com, smtp.mailgun.org, smtp.sendgrid.net
`smtpPort`	integer	optional	SMTP server port. Use 587 for STARTTLS (recommended), 465 for SSL/TLS, or 25 for unencrypted.
`smtpUser`	string	required	SMTP login username. Usually your full email address. For SendGrid, use 'apikey' as the username.
`smtpPassword`	string	required	SMTP login password. For Gmail, use an App Password (Google Account > Security > App Passwords). For SendGrid/Mailgun, use your API key.
`useTls`	boolean	optional	Enable TLS encryption. Port 587 uses STARTTLS, port 465 uses direct SSL. Recommended: always keep enabled.

3. Start an Actor run

Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.

Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.

import json
import os
import urllib.request

# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
    actor_input = json.load(stream)

token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
    "https://api.apify.com/v2/acts/LZLFcGSFyk5X30jn1/runs?timeout=120&maxTotalChargeUsd=0.50",
    data=json.dumps(actor_input).encode("utf-8"),
    headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
    method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
    run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.

4. Inspect the actual results

Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.

Delivery confirmation record for each email sent, including recipients, subject, and the SMTP server used.

Questions before you run

Which inputs are required?

The published required fields are to, subject, smtpHost, smtpUser, smtpPassword

What does this guide verify?

The fields, prefills, and schema links are rendered from the published build. This is a usage recipe, not a paid live extraction test. Source availability and collection results can vary.

What if the run request times out?

Check Apify Console before retrying. The first request may already have created a run. Do not automatically repeat a run-creation POST.

Open on Apify Full Actor reference

Generated from source build mX5wE5AOnSOfsXi8M and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.