# Email Link Extractor (`leafed_dryer/email-link-extractor`) Actor

Advanced email link processor that extracts, analyzes and unwraps tracking URLs. Supports SendGrid, Mailchimp, Beehiiv, HubSpot, Constant Contact and other major email service providers. Automatically resolves redirect chains to find real destination URLs hidden behind marketing tracking links.

- **URL**: https://apify.com/leafed_dryer/email-link-extractor.md
- **Developed by:** [Roch News](https://apify.com/leafed_dryer) (community)
- **Categories:** Automation, News, Integrations
- **Stats:** 13 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Email Link Extractor & Tracker Cleaner

Este Actor extrae todos los links de emails y resuelve URLs de tracking para obtener las URLs reales de destino.

### 🎯 ¿Qué hace?

- **Extrae links** del HTML y texto plano de emails
- **Identifica tracking links** de servicios como SendGrid, Mailchimp, Beehiiv
- **Resuelve URLs reales** ocultas detrás de redirects de tracking
- **Organiza resultados** por tipo (directos, tracked, resueltos)
- **Proporciona estadísticas** detalladas

### 📧 Servicios de tracking soportados

- **SendGrid** (`sendgrid.net/ss/c/`)
- **Mailchimp** (`mailchimp.com/track/`)
- **Beehiiv** (`mail.beehiiv.com`)
- **HubSpot** (`hslinks.com`)
- **Constant Contact** (`constantcontact.com/links/`)
- **Mailgun** (`mailgun.org/link/`)
- **Campaign Monitor** (`click.campaigns.`)
- **AWeber** (`aweber.com/ct/`)

### 🚀 Uso básico

#### Input mínimo:

```json
{
  "html": "<html>contenido del email</html>",
  "subject": "Asunto del email"
}
```

#### Input completo:

```json
{
  "html": "HTML del email",
  "text": "Texto plano del email",
  "subject": "Asunto",
  "from": {
    "address": "sender@example.com",
    "name": "Sender Name"
  },
  "date": "2025-08-17T15:06:16.000Z",
  "messageId": "unique-message-id",
  "options": {
    "resolveRedirects": true,
    "includeMailto": false,
    "minTextLength": 3
  }
}
```

### 📊 Output

```json
{
  "success": true,
  "timestamp": "2025-08-17T15:30:00.000Z",
  "email": {
    "subject": "Newsletter Title",
    "from": {...}
  },
  "summary": {
    "totalLinks": 15,
    "trackedLinks": 12,
    "directLinks": 3,
    "resolvedLinks": 8,
    "unresolvedLinks": 4
  },
  "trackingStats": {
    "sendgrid": {
      "total": 8,
      "resolved": 6,
      "unresolved": 2
    }
  },
  "links": {
    "all": [...],
    "resolved": [
      {
        "original": "https://tracking-url...",
        "cleaned": "https://real-destination.com",
        "text": "Click here",
        "service": "sendgrid"
      }
    ],
    "direct": [...],
    "unresolved": [...]
  }
}
```

### 🔧 Integración con Make.com

1. **HTTP Request** al Actor:
   ```
   POST https://api.apify.com/v2/acts/YOUR_USERNAME~email-link-extractor/runs
   ```

2. **Headers**:
   ```
   Authorization: Bearer YOUR_API_TOKEN
   Content-Type: application/json
   ```

3. **Body**: El contenido del email de Make

4. **Obtener resultado**:
   ```
   GET https://api.apify.com/v2/acts/YOUR_USERNAME~email-link-extractor/runs/LAST/dataset/items
   ```

### 💡 Casos de uso

- **Marketing automation**: Limpiar links antes de reenviar
- **Analytics**: Rastrear destinos reales de campaigns
- **Content curation**: Extraer recursos de newsletters
- **Link monitoring**: Verificar destinos de tracking

### ⚡ Performance

- **Tiempo promedio**: 2-5 segundos por email
- **Memoria**: ~100MB por ejecución
- **Costo**: ~$0.0001 por email procesado

### 🆘 Solución de problemas

#### Error: "Se requiere al menos HTML o texto"

- Asegúrate de enviar `html` o `text` en el input

#### Links no resueltos

- Algunos tracking links son muy complejos o están encriptados
- El Actor marca estos como `status: "unresolved"`

#### Timeouts

- Emails muy grandes pueden tomar más tiempo
- Aumenta `timeoutSecs` en las opciones de ejecución

### 📝 Changelog

#### v1.0.0

- Primera versión estable
- Soporte para 8 servicios de tracking principales
- Integración optimizada para Make.com

# Actor input Schema

## `html` (type: `string`):

HTML content of the email to process

## `text` (type: `string`):

Plain text content of the email

## `subject` (type: `string`):

Email subject line

## `from` (type: `object`):

Sender information

## `date` (type: `string`):

Email date in ISO format

## `messageId` (type: `string`):

Unique message identifier

## Actor input object example

```json
{}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("leafed_dryer/email-link-extractor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("leafed_dryer/email-link-extractor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call leafed_dryer/email-link-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leafed_dryer/email-link-extractor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/6sw7viGwKrb6eJ36m/builds/kVLQI3chAxjBHNUXw/openapi.json