Reference · Tools
Emelia trigger
Starts a workflow when Emelia reports campaign activity like an email sent, opened, or replied.
The Emelia Trigger node starts a BusyBot workflow the moment a campaign event happens in Emelia — a reply, a bounce, a link click, an unsubscribe, and more. It registers a webhook directly with Emelia's API for a specific campaign and delivers the full event payload to your workflow. Use it to, for example, automatically tag a replied contact in your CRM the instant they respond to a cold email sequence.
- Works as
- Webhook trigger
- Tool name
emelia_trigger- Parameters
- 2
- Outputs
- Output
- Credentials
- Emelia API
- Official docs
- Emelia docs docs.emelia.io
What you can build with Emelia
- 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.
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.
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 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— alwaysemelia_trigger_webhook_timestamp— ISO 8601 timestamp of when the request arrived_webhookEvent— the event Emelia reported, taken from the payload’seventfield, falling back totype
The Emelia payload itself carries:
event— the campaign activity, e.g.sentcampaignId— the campaign the event belongs tocontactEmail,contactFirstName,contactLastName— the contact the event is aboutmessageId— the message that produced the eventsentAt— when the message was sent
Reference the payload downstream by expression, e.g. {{ $json.contactEmail }}.
Example Configuration
Fire when a contact replies to or clicks a link in a campaign:
{
"type": "emelia_trigger",
"parameters": {
"campaignId": "5f8a1b2c3d4e5f6a7b8c9d0e",
"events": ["replied", "clicked"]
}
}
Track delivery problems on a campaign:
{
"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
This tool triggers a workflow when an Emelia campaign event occurs, such as an email being sent, opened, replied to, bounced, a link clicked, or a contact unsubscribing. It is the right tool when you need to automate actions based on specific activities within your Emelia cold email outreach campaigns. The tool produces the full event payload from Emelia, containing details about the campaign activity.
Frequently asked questions
Which Emelia campaign events can this node listen for?
The node supports six event types: email sent, email opened, replied, bounced, link clicked, and contact unsubscribed. You choose which events to subscribe to when configuring the node — you are not required to listen for all of them at once.
What credentials do I need to connect this node to Emelia?
You need an Emelia API credential (credential type: emeliaApi) configured in BusyBot. The node uses this credential to register the webhook with Emelia's API on your behalf, so Emelia knows where to send event callbacks. Without it, the webhook cannot be created and the trigger will never fire.
Does the node listen across all my Emelia campaigns, or just one?
The trigger is scoped to a specific campaign — you select which campaign to monitor as part of the node's configuration. If you need to react to events from multiple campaigns, you would set up a separate Emelia Trigger node for each one.
What data does the node pass to the rest of my workflow?
The node outputs the full event payload that Emelia sends in its POST callback. This includes the event type and the associated contact and campaign data. Every downstream node in your workflow has access to this complete payload via the single Output connector.
How does BusyBot register and manage the webhook with Emelia?
When you activate a workflow containing this node, BusyBot automatically calls Emelia's API using your emeliaApi credential to register the webhook URL. You do not need to copy a URL into Emelia manually. If you deactivate or delete the workflow, the webhook registration is managed accordingly through the same API.
Build with Emelia
Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Emelia API credentials first.
Open BusyBotLast reviewed . Spotted something wrong? Tell us.