SmartLead icon

SmartLead

Comprehensive SmartLead API integration for email marketing automation

Overview

The "Get Provider Report" operation of the Smart Delivery resource in this node fetches email deliverability test reports aggregated by email providers. This allows users to analyze how their emails perform across different email service providers, helping identify deliverability issues or provider-specific trends.

Typical use cases include:

  • Monitoring email placement and spam filtering rates per provider.
  • Optimizing campaigns based on provider-specific performance.
  • Diagnosing deliverability problems with certain providers.

For example, a marketing team can use this report to see if their emails are consistently landing in inboxes for Gmail but getting flagged as spam by Yahoo, enabling targeted improvements.

Properties

Name Meaning
Test Filter Data JSON-formatted filter and pagination options to specify which tests to include in the report. Common fields include: limit (number of results), offset (results to skip), and optional date filters like date_from and date_to.

Example value for Test Filter Data:

{
  "limit": 10,
  "offset": 0,
  "date_from": "2024-01-01",
  "date_to": "2024-01-31"
}

Output

The node outputs a JSON array under the json field containing the provider-wise report data returned from the API. Each item in the array represents metrics related to a specific email provider's deliverability performance within the filtered test scope.

The exact structure depends on the external API response but typically includes fields such as provider ID, name, delivery statistics, spam rates, and other relevant analytics.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the SmartLead API.
  • The node makes HTTP POST requests to the endpoint:
    https://smartdelivery.smartlead.ai/api/v1/reports/provider
  • The user must provide valid JSON filter parameters for the test data to control pagination and filtering.

Troubleshooting

  • Invalid JSON in Test Filter Data: If the JSON provided in the "Test Filter Data" property is malformed, the node will throw an error indicating invalid JSON. To fix, ensure the JSON syntax is correct and properly formatted.
  • API Authentication Errors: If the API key credential is missing or invalid, requests will fail. Verify that the API key is correctly configured in n8n credentials.
  • Empty or Unexpected Response: If the filter parameters exclude all data or are incorrect, the output may be empty or not as expected. Adjust the filter dates, limit, and offset accordingly.
  • Network or Endpoint Issues: Connectivity problems or changes in the API endpoint URL could cause failures. Confirm network access and that the base URL remains valid.

Links and References


This summary focuses exclusively on the "Get Provider Report" operation of the "Smart Delivery" resource as requested.

Discussion