<!-- BusyBot node reference — https://busybot.net/tools/emelia-trigger/ -->

> Node: Emelia Trigger (`emelia_trigger`) · Webhook trigger · v1
> Category: Marketing · Credentials: Emelia API (`emeliaApi`)
> Updated: 2026-08-16

# Emelia Trigger

> Trigger workflow on Emelia campaign events

## Overview

Starts a workflow when Emelia sends a webhook callback for campaign activity events such as email sent, opened, replied, bounced, link clicked, or contact unsubscribed. Emelia is a cold email outreach platform. The trigger registers a webhook with Emelia's API for a specific campaign and selected events, and receives POST callbacks with event payload data.

**Category:** Marketing  
**Tool Name:** `emelia_trigger`  
**Version:** 1

**Appearance:** Icon: `lucide-Mail` | Color: `#5a5aef`

## Node Type

**Trigger** — webhook (receives incoming HTTP callbacks)

## Input / Output

| Direction | Port(s) |
|-----------|--------|
| Input | None (trigger node) |
| Output | `Output` |

## Credentials

This tool requires **Emelia API** credentials.
See the [Credentials Guide](https://busybot.net/credentials/emelia-api/) for setup instructions.

### Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| Campaign | `string` | Yes | — | The ID of the Emelia campaign to monitor for events. |
| Events | `multiOptions` | Yes | `[]` | Which campaign activity events to listen for. |
| | | | | Options: `bounced` (Email Bounced), `opened` (Email Opened), `replied` (Email Replied), `sent` (Email Sent), `clicked` (Link Clicked), `unsubscribed` (Unsubscribed Contact) |

## Output Data

Each delivery from Emelia produces one output item. The webhook payload is copied onto the item unchanged, and three fields are added:

- `_trigger` — always `emelia_trigger_webhook`
- `_timestamp` — ISO 8601 timestamp of when the request arrived
- `_webhookEvent` — the event Emelia reported, taken from the payload's `event` field, falling back to `type`

The Emelia payload itself carries:

- `event` — the campaign activity, e.g. `sent`
- `campaignId` — the campaign the event belongs to
- `contactEmail`, `contactFirstName`, `contactLastName` — the contact the event is about
- `messageId` — the message that produced the event
- `sentAt` — when the message was sent

Reference the payload downstream by expression, e.g. `{{ $json.contactEmail }}`.

## Usage Examples

- trigger workflow when an email is opened in an Emelia campaign
- listen for Emelia email bounces
- start workflow when a contact replies to a cold email
- monitor Emelia campaign link clicks
- receive notification when a contact unsubscribes from an Emelia campaign

## Example Configuration

Fire when a contact replies to or clicks a link in a campaign:

```json
{
  "type": "emelia_trigger",
  "parameters": {
    "campaignId": "5f8a1b2c3d4e5f6a7b8c9d0e",
    "events": ["replied", "clicked"]
  }
}
```

Track delivery problems on a campaign:

```json
{
  "type": "emelia_trigger",
  "parameters": {
    "campaignId": "5f8a1b2c3d4e5f6a7b8c9d0e",
    "events": ["bounced", "unsubscribed"]
  }
}
```

### Trigger Behavior

- **Activation:** When the workflow is activated, a webhook endpoint is registered with the service.
- **Deactivation:** The webhook is automatically unregistered when the workflow is deactivated.
- **Payload:** The incoming webhook payload is parsed and output as workflow items.
- **Verification:** Supports signature verification where applicable.

## Tips

Entry point that fires when Emelia sends a webhook callback for campaign events such as email sent, opened, replied, bounced, link clicked, or unsubscribed. Outputs the full event payload for downstream processing.