Actions74
- šÆ Campaign Management Actions
- š„ Lead Management Actions
- š§ Email Accounts Actions
- š Analytics & Stats Actions
- š Smart Delivery Actions
- Get Region Provider IDs
- Create Manual Placement Test
- Create Automated Placement Test
- Get Spam Test Details
- Delete Tests in Bulk
- Stop Automated Test
- List All Tests
- Get Provider Report
- Get Geo Report
- Get Sender Account Report
- Get Spam Filter Report
- Get DKIM Details
- Get SPF Details
- Get rDNS Report
- Get Sender Account List
- Get Blacklists
- Get Domain Blacklist
- Get Spam Test Email Content
- Get Email Reply Headers
- Get Schedule History
- Get IP Details
- Get Mailbox Summary
- Get Mailbox Count
- Get All Folders
- Create Folder
- Get Folder by ID
- Delete Folder
- š Webhooks Actions
- šØ Smart Senders Actions
Overview
This node integrates with the SmartLead API to manage email marketing automation, specifically handling various resources such as campaigns, leads, email accounts, analytics, smart delivery tests, webhooks, and smart senders.
For the Email Accounts - Get by ID operation, the node retrieves detailed information about a specific email account using its unique identifier. This is useful when you want to fetch configuration, status, or metadata of an email account that is part of your email marketing setup.
Common scenarios:
- Fetching details of an email account before updating or reconnecting it.
- Retrieving email account info for reporting or auditing purposes.
- Integrating email account data into workflows that require validation or synchronization.
Practical example:
You have multiple email accounts linked to different campaigns. Before sending emails, you want to verify the status and settings of a particular email account by its ID to ensure it is active and properly configured.
Properties
| Name | Meaning |
|---|---|
| Email Account ID | The unique identifier of the email account to retrieve. |
| Additional Fields | A collection of optional fields (not applicable for this operation but present in schema). |
Note: For this operation, only the Email Account ID property is required and used.
Output
The node outputs the JSON response from the SmartLead API containing the details of the requested email account. The structure typically includes fields such as:
- Email account metadata (ID, email address, provider info)
- Status and configuration details
- Warmup settings if applicable
- Associated campaign IDs or usage statistics
If the API returns binary data (not typical for this operation), it would be summarized accordingly, but here the output is purely JSON.
The output is wrapped in n8n's standard execution metadata format, associating each item with the input index.
Dependencies
- Requires an API key credential for authenticating with the SmartLead API.
- The base URL for requests is
https://server.smartlead.ai/api/v1. - Proper configuration of the SmartLead API credentials in n8n is necessary.
- Network access to the SmartLead API endpoint must be available.
Troubleshooting
- Invalid Email Account ID: If the provided ID does not exist or is malformed, the API will likely return an error. Verify the ID correctness.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Network Issues: Check connectivity to the SmartLead API server.
- JSON Parsing Errors: Not applicable for this operation since no JSON input is parsed, but other operations may throw errors if JSON inputs are invalid.
- Rate Limits: Be aware of any API rate limits imposed by SmartLead to avoid request failures.
Links and References
- SmartLead API Documentation (Assumed based on base URL)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for authentication and error handling.
Summary of execute() logic for Resource "emailAccount" and Operation "get"
- Reads the
emailAccountIdparameter. - Constructs a GET request to
https://server.smartlead.ai/api/v1/email-accounts/{emailAccountId}. - Sends the request authenticated via the configured API key.
- Returns the JSON response data as output.
This operation is straightforward and involves a single GET request to fetch email account details by ID.