Easyhook

Communication Developer Tools

v0.2.39

Last updated Aug 28, 2026

n8n nodes for the Easyhook messaging and reviews API.

146 Weekly Downloads

2,661 Monthly Downloads

View on NPM GitHub Repository

Included Nodes

Easyhook

Easyhook Trigger

Description

n8n-nodes-easyhook

Easyhook integration for n8n.

Easyhook is a lightweight multichannel messaging and reviews API for WhatsApp, Telegram, TikTok Business Messaging,
Gmail, Outlook, generic IMAP/SMTP email, Mercado Libre, and Google Business Profile. This node focuses on the workflows
developers normally automate:

Message Action groups cross-channel text and media actions. Use Send Buttons for standardized reply buttons on WhatsApp, Messenger, Instagram, Telegram, and TikTok Business Messaging. Use Send Quick Replies when Messenger or Instagram needs more than three text choices.
Message Control groups read, typing, reply, and reaction actions and only

lists channels that support the selected operation.

Email Only works consistently with Gmail, Outlook, and IMAP/SMTP: send,

reply, forward, read/unread, archive, and create/edit/send drafts.

Comment lists public Facebook Page and Instagram professional-account

comments and publishes public replies without treating them as private messages.

Onboarding creates or sends hosted connection links for any supported channel.
WhatsApp Only groups WhatsApp sends, templates, Flows, and consent.
Review lists Google reviews, returns the aggregate location rating, and publishes business replies.
Template lists, synchronizes, checks categories, creates, and deletes templates.
Use standard or humanized delivery on WhatsApp, Messenger, Instagram, Telegram, and TikTok Business Messaging.
Schedule supported WhatsApp, Messenger, Instagram, Telegram, Mercado Libre, and TikTok Business Messaging messages.
Upload organization-wide reusable media and send it later by media_name.
Download protected incoming media into an n8n binary field.
For TikTok webhooks, keep contact.id as the stable recipient and

message.thread_id as the provider conversation. Easyhook accepts either
value as to and resolves the TikTok thread internally.

List/sync templates and media
Cancel scheduled messages before processing begins
Receive Easyhook webhook events in n8n with the Easyhook Trigger node

For Mercado Libre, use the same Send Text operation. Select the connected
seller as From and map To from an incoming trigger item:
question: answers a product question and pack: replies in a
post-sale conversation. Mercado Libre does not permit arbitrary new
conversations, so the destination must come from a previous event.

Install

In n8n, open Settings > Community Nodes and install:

n8n-nodes-easyhook

For self-hosted n8n, you can also install it manually in your n8n custom nodes folder.

Credentials

Create an Easyhook API credential:

API Key: your ehlive... key from Easyhook

n8n validates the credential with GET /v1/me, so no WhatsApp number is needed just to test the API key.

Common Examples

Receive Webhooks

Use Easyhook Trigger as the first node in a workflow.

1. Add the Easyhook Trigger node.
2. Select your Easyhook API credential.
3. Choose a provider. Easyhook filters the available events and scope types automatically.
4. Choose a scope. For WABAs, WhatsApp numbers, Messenger Pages, or Instagram accounts, select a connected account from the list loaded with your API credential.
5. Activate the workflow.

Public comments require their own connection and provider. Choose **Facebook
Comments or Instagram Comments*, then subscribe to comment.. Messenger
and Instagram providers remain limited to private messages. Comment events
include comment.post.id and may include publication context under
interaction.object.

n8n registers its Production URL in Easyhook automatically and stores the HMAC signing secret in the workflow’s private static data. Deactivating or deleting the workflow removes the Easyhook subscription. No portal setup or secret copy/paste is required.

WhatsApp uses the same three levels as the Easyhook portal: Entire Organization → WABA → WhatsApp Number. Selecting a WABA receives matching events from all numbers connected to it. Meta Business Portfolios stay internal and never appear as n8n scopes.

The trigger outputs the normalized Easyhook webhook JSON directly.

For Google Business Profile, choose provider Google Business Profile and
subscribe to review.created and/or review.updated. Map review.id when a
later node needs to reply to that review.

Manage Google Reviews

Resource: Review
Operation: List Reviews, Get Rating, or Reply to Review
Location: select a connected Google Business Profile location

List Reviews returns normalized reviews and nextpagetoken. Get Rating
returns the aggregate rating and total review count. To respond publicly,
choose Reply to Review, map review.id from the trigger or list result, and
enter the reply. Google may update an existing reply when the same review is
answered again.

Send Text

Resource: Message Action
Operation: Send Text
Channel: select a connected channel
To: 5215660069997
Body: Hello from n8n

The channel selector stores the same provider-native value delivered as
account.id by the Easyhook Trigger. WhatsApp uses the Meta Phone Number ID;
Messenger uses the Page ID; Instagram uses the Instagram account ID; and
Telegram uses its connected account ID. Legacy page and ig aliases remain
accepted by the API, but new workflows do not need prefixes.

Choose Delivery: Humanized to apply the supported read, pause, and typing
behavior before sending through WhatsApp, Messenger, Instagram, or Telegram.

Send Messenger Or Instagram Quick Replies

Resource: Message Action
Operation: Send Quick Replies
Channel: select a connected Messenger Page or Instagram account
To: map the provider contact ID from contact.id
Body: prompt shown above the buttons
Quick Replies: add 1–13 title/payload pairs

The title is visible and accepts up to 20 characters. The payload is returned
unchanged in message.quick_reply.payload; use it to route the workflow.

For scheduled text, media, or templates, add:

Schedule At: ISO 8601 execution time
Options > Client Reference: optional identifier from your application
Options > Idempotency Key: optional stable key used only when retrying the same scheduled send

Use resource Cancel Scheduled Message to cancel a pending delivery before processing begins.

Send Email

Resource: Email Only
Operation: Send Email
Email: select a connected Gmail, Outlook, or IMAP/SMTP address
To Email: recipient email address
Subject: email subject
Message: plain-text message
HTML Message: optional rich body

To answer an existing email, choose Reply to Email instead. Map the inbound
Easyhook Trigger value message.id into Original Email ID. Easyhook resolves
the Gmail thread, Outlook reply, or IMAP headers automatically. You do not need
to configure Thread ID, In-Reply-To, or References in n8n.

All email providers use POST /v1/messages/email and return the same normalized
response. Treat inbound message.html as untrusted content.

Add files under Attachments by selecting an input binary field. Easyhook
uses its file name and MIME type automatically. Use Forward Email with the
trigger’s message.id; use Update Email to mark that ID read, unread, or
archived. Draft operations return a Draft ID that can later be edited or sent.

Send Read, Typing, Or Reaction

Resource: Message Control
Operation: Mark as Read, Show Typing, React, or Reply
Channel: select the channel from the incoming event
Inbound Message ID: map message.id from Easyhook Trigger

The channel list is filtered by capability. WhatsApp supports all four
operations. Messenger and Instagram support read, typing, and reply. Telegram
supports typing, reply, and reaction. Unsupported combinations are rejected
explicitly without charging the wallet.

For a reaction, also set To and Reaction. Leave the reaction empty to remove
it. For a contextual reply, map the original message.id, recipient, and reply
text.

Send Reusable Media

First upload media:

Resource: Media
Operation: Upload
Name: promo_image
Type: Image
Source: Binary Property
Binary Property: data

Reusable media belongs to the Easyhook organization, not to one WABA or channel.
The same media_name can be used by supported WhatsApp, Messenger, Instagram,
and Telegram senders in that organization.

Then send it:

Resource: Message Action
Operation: Send Media
Channel: select a supported connected channel
To: customer WhatsApp ID
Type: Image
Media Reference Type: Reusable Media Name
Media Name: promo_image

To read protected incoming media, map message.media.url from Easyhook Trigger
into Media → Download → Media URL. The node authenticates with the Easyhook
credential and returns the file in the selected binary field. Do not use a
generic HTTP Request node without the API key: protected URLs intentionally
return an authorization error.

Send Template

Resource: WhatsApp Only
Operation: Send Template
Template Source: Enter Manually
Template Name: the approved template name in Easyhook/Meta
Language: select the Meta language code from the list, for example esMX or enUS
Template Data: choose Map Automatically to load the template definition by name and language, or Custom Components (JSON) to provide raw components.

Both template sources support the same data modes. Choose From Easyhook selects an approved template from a list; Enter Manually resolves the approved template using the typed name and selected language. Map Automatically then creates only the fields required at send time:

Header text variables
Header image, video, or document URL and optional document filename
Header location fields
Body variables, including named variables
Dynamic URL button values
Quick reply payloads
Copy-code coupon values

Use Custom Components (JSON) when you need to provide raw Meta components. The value can be a components array or { "components": [...] }. Template text itself remains fixed by the approved Meta template.

Text header, body variables, and dynamic URL button:

[
  {
    "type": "header",
    "parameters": [{ "type": "text", "text": "PED-1048" }]
  },
  {
    "type": "body",
    "parameters": [
      { "type": "text", "text": "Benjamin" },
      { "type": "text", "text": "15 July" }
    ]
  },
  {
    "type": "button",
    "sub_type": "url",
    "index": "0",
    "parameters": [{ "type": "text", "text": "PED-1048" }]
  }
]

Media header and named body variable:

{
  "components": [
    {
      "type": "header",
      "parameters": [
        {
          "type": "document",
          "document": {
            "link": "https://cdn.example.com/invoice.pdf",
            "filename": "invoice.pdf"
          }
        }
      ]
    },
    {
      "type": "body",
      "parameters": [
        {
          "type": "text",
          "parametername": "customername",
          "text": "Benjamin"
        }
      ]
    }
  ]
}

Media links must use HTTPS and be downloadable by Meta without authentication. A dynamic URL button value is the variable suffix, not the complete URL. Use [] when the template has no runtime components.

Send WhatsApp Flow

Resource: WhatsApp Only
Operation: Send Flow
From: your WhatsApp sender number
To: customer WhatsApp number
Flow Name: the Easyhook flow name
Message Body: the text above the flow button
Button Text: the flow button label
Flow Data: optional key/value fields sent as the flow payload

Send Consent

Resource: WhatsApp Only
Operation: Send Opt-In or Opt-Out
From: your WhatsApp sender number
To: customer WhatsApp number
Consent Flow: Opt-In or Opt-Out

To store consent collected on a website, CRM, or external form, use
Record Opt-In or Opt-Out instead. Select the marketing or service scope and
provide auditable Evidence JSON, for example:

{
  "form_id": "lead-form-v3",
  "accepted_at": "2026-07-29T18:00:00.000Z",
  "source_url": "https://example.com/contact"
}

Easyhook records this evidence but does not manufacture consent. The Easyhook
customer remains responsible for collecting valid permission and honoring
opt-outs.

Use Get Consent Status with the same sender and contact to read the current
service and marketing states. Each scope returns optin, optout,
pendingoptout, or unknown; unknown is not permission.

Voice AI Calls

Use Voice Call > Record Consent before any automated outreach. Select the
Easyhook number, destination, opt-in or opt-out state, capture time, source,
and auditable Evidence JSON. Easyhook stores the customer’s evidence but does
not manufacture consent.

Use Voice Call > Start AI Call with the same number and destination after a
distinct outbound ElevenLabs agent has been assigned in the Easyhook portal.
Set a maximum duration, optional scalar Context JSON, and a stable Idempotency
Key. Easyhook enforces consent, frequency limits, number ownership, provider
capabilities, wallet reservation, and settlement. Get Call and Hang Up
operate on the returned Easyhook call ID.

Hosted Onboarding

Resource: Onboarding
Operation: Get Onboarding URL or Send Onboarding Link
Provider: WhatsApp, Messenger, Instagram, Telegram, TikTok Business Messaging, Gmail,

Outlook, IMAP/SMTP, or Mercado Libre

Connection: WhatsApp Coexistence or WhatsApp Business API when the

provider is WhatsApp

Language: Spanish or English
Return URL: optional HTTPS destination after completion

Get Onboarding URL returns the hosted URL without sending a message. Send Onboarding Link creates the same session and sends its URL from the selected Easyhook WhatsApp number to To. Subscribe with Easyhook Trigger to onboarding events when the workflow must continue after the customer connects a number.

Hosted links expire after one hour and are consumed after a successful connection. The sent message is
localized by Easyhook and always includes the hosted URL.

Webhook Automation

Easyhook webhooks are handled with Easyhook Trigger. It is not a polling node: activation creates a /v1/webhooks subscription for the n8n Production URL and deactivation removes it. Deliveries are authenticated automatically with X-Easyhook-Signature: sha256=.

The trigger starts with no provider or event selected. Choose one provider and
at least one compatible event. The option names and values match the Easyhook
portal; All events must be selected alone.

Useful event scopes:

message.*: incoming messages from the selected provider, including

WhatsApp, Messenger, Instagram, Telegram, TikTok Business Messaging, Gmail, Outlook, and IMAP/SMTP

status.*: message delivery/read/failure status
template.*: template status changes
flow.submission.*: WhatsApp Flow responses
smbmessageecho.*: WhatsApp Business App coexistence message echoes
smbappstate_sync.*: WhatsApp Business App coexistence contact/app state sync
history.*: coexistence history sync events
account_update.*: WhatsApp account updates
media.*: media lifecycle events, when enabled in Easyhook
message.text, message.image, status.failed: narrower event filters matching the Easyhook portal

Messenger and Instagram hooks use the same event values with a separate
provider filter. Do not add provider prefixes to event names.

Receive Coexistence History

Configure the Easyhook Trigger before connecting the WhatsApp Business App number or requesting coexistence sync:

1. Select Provider: WhatsApp.
2. Select Event: Coexistence history (history.*).
3. Choose the organization, WABA, or WhatsApp number scope.
4. Activate the workflow.
5. Allow history sharing in the WhatsApp Business App and keep the app open while synchronization starts.

Easyhook creates the webhook subscription and stores its HMAC secret in n8n automatically. Do not create a second portal webhook. message.* only covers live messages; it does not include history imports.

Easyhook delivers History and App State in signed batches of at most 100 events. One batch starts one workflow execution, and the trigger expands every normalized event into a separate n8n item. This keeps large imports fast without creating one execution per historical message. Historical inbound messages use type: message.received; historical outbound messages use type: message.echo. Both include message.source: history, and every item includes _sync with its batch and progress metadata:

{
  "id": "event_uuid",
  "type": "message.echo",
  "channel": "whatsapp",
  "account": { "id": "980912725115744", "phone": "5218661479075" },
  "contact": { "id": "5214445087305" },
  "message": {
    "id": "wamid...",
    "direction": "out",
    "source": "history",
    "type": "text",
    "text": "Previous reply",
    "history": {
      "thread_id": "5214445087305",
      "status": "READ",
      "phase": 1,
      "chunk_order": 2,
      "progress": 80
    }
  },
  "_sync": {
    "batchid": "deliveryuuid",
    "source": "history",
    "progress": 80,
    "count": 100
  }
}

Use message.id for idempotency because deliveries are at-least-once. Keep live auto-replies disabled when message.source is history. Media does not block the import: a historical message can first include message.media.storagestatus: pending, followed later by type: message.mediaavailable with the same message.id and a protected download URL.

The same history. trigger receives sync.started, sync.progress, sync.completed, and sync.failed lifecycle items. Wait for sync.completed instead of inferring completion from Meta’s progress value. App State contact records are delivered under smbappstate_sync.; they can arrive before or after History, so use contact.id and message.id rather than array position to join and deduplicate records.

History covers up to approximately 180 days and excludes group conversations. Historical media availability is normally limited to recent messages (approximately 14 days). Easyhook offers three import policies in the portal: messages only, recent media without video, and recent media including video. Missing or expired media never fails the message import.

Only one synchronization runs per WhatsApp number. An organization may have any number of connected numbers, with up to two numbers importing concurrently for fair capacity sharing. Failed webhook deliveries retry five times and can be replayed without changing the original message IDs or idempotency keys.

If the business disables history sharing, Meta can return error 2593109; the trigger receives it as type: sync.failed under the same history.* selection.

Development

npm ci
npm run lint
npm run typecheck
npm run build
npm pack --dry-run

Releases are published from GitHub Actions with npm provenance. See CONTRIBUTING.md for the validation and release workflow.