Send Email via Webhook (NHN Cloud)

This guide explains how to build an email send webhook campaign using the NHN Email Send API.

Prerequisites

Preliminary preparation is required for normal bulk email sending.

This step directly affects send success rates and domain reputation.

1. Activate NHN Cloud Email Service

NHN Cloud registration and Email service activation in the console is required.

Check the appKey and X-Secret-Key in the NHN Cloud console.

2. Sender Domain Authentication (Domain Authentication)

Since February 1, 2024, the Gmail sender guidelines have changed.

If domain authentication and SPF, DKIM, DMARC authentication are not completed, sending to gmail.com and yahoo.com domains may be rejected.

This is the most important step for bulk sending.

Domain authentication is essential for spam prevention, delivery rate improvement, and securing bulk sending permissions. When using NHN Cloud, after registering the domain, you must configure the following DNS values.

• SPF (Sender Policy Framework)

• DKIM (DomainKeys Identified Mail)

• Return-Path (Bounce Domain)

SPF (Sender Policy Framework)

SPF is a DNS record that verifies the trustworthiness of the email sending server. It is a setting that authorizes the NHN server to send mail on behalf of your domain.

DNS Type: TXT

Example:

v=spf1 include:mail.nhncloudservice.com ~all

DKIM (DomainKeys Identified Mail)

DKIM is a method that adds a digital signature to emails to prevent sender forgery and tampering during transmission. You can check the DKIM public key in the NHN console.

DNS Type: TXT

Example:

selector._domainkey.example.com  IN TXT  "v=DKIM1; k=rsa; p=public_key..."

Return-Path (Bounce Domain)

Setting up the return mail reception path is also important. NHN Cloud provides a separate Return-Path domain, and this must be configured as a CNAME.

Example:

rp.example.com  CNAME  bounce.nhncloudservice.com

3. Register Sender Email Address (Verified Sender)

The domain and address from which to send email must be registered in the NHN console.

DKIM and SPF must be configured for the sender address to be properly verified.

Example:

[e-mail]

4. Prepare Recipient Data

To send emails via Hackle webhook, the following user properties must be collected.

• email

• name (optional)

If there are many incorrect email addresses, send restrictions may be imposed. We recommend managing email address format validation and collection integrity together.

Configure the Webhook

Follow the steps below to set up the email send webhook.

1

Create a Webhook Campaign

Click the Webhook menu in the Hackle Dashboard, then click the Create button.

Next, enter the desired campaign name to create it.

2

Configure Request Information

URL Settings

Enter the HTTP Method and URL according to the NHN Email Send API.

Header Settings

Click the Add button in the Headers tab and enter the values.

If you need to use different tokens per target user, you can use personalization.

• Key: Authorization

• Value: {{user_properties.authorization_type}} {{user_properties.access_token}}

You can insert personalization values using the {...} button.

You can use stored user properties or event properties to dynamically inject user-specific token values.

3

Body Settings

Set the Body tab to JSON mode and write it according to the NHN General Email Send Request Body specification.

Write Title and Body Directly

You can also insert personalization values inside the title and body.

For example, you can insert values such as name, registration date, and product name individually for each user.

{
  "senderAddress": "[e-mail]",
  "senderName": "YourService",
  "title": "회원가입이 완료되었습니다",
  "body": "안녕하세요  {{user_properties["name"] | default: "회원"}}님,\n회원가입을 환영합니다!",
  "receiverList": [
    {
      "receiveMailAddr": "{{user_properties["email"] | default: ""}}",
      "receiveName": "{{user_properties["name"] | default: "회원"}}",
      "receiveType": "MRT0"
    }
  ],
  "userId": "hackle-webhook",
  "statsId": "hackle-email"
}

• receiveType is typically fixed as MRT0 when sending to the recipient themselves.

• userId and statsId are fields for NHN statistics. They can be managed as fixed strings.

Using NHN Templates

Define replacement keys such as ##user_name## and ##signup_date## in the NHN template body and title, and match them with templateParameter.

Using properties like user_properties["signup_date"] makes it easy to include information such as registration date, purchase amount, and product name.

If you have pre-registered a template in the NHN console, you can manage it more cleanly using templateId and templateParameter.

{
  "templateId": "WELCOME_TEMPLATE",
  "templateParameter": {
    "user_name": "{{ user_properties[\"name\"] | default: \"회원\" }}",
    "signup_date": "{{ user_properties[\"signup_date\"] | default: \"\" }}"
  },
  "receiverList": [
    {
      "receiveMailAddr": "{{ user_properties[\"email\"] | default: \"\" }}",
      "receiveName": "{{ user_properties[\"name\"] | default: \"\" }}",
      "receiveType": "MRT0"
    }
  ],
  "userId": "hackle-webhook",
  "statsId": "hackle-email-template"
}

• receiveType is typically fixed as MRT0 when sending to the recipient themselves.

• userId and statsId are fields for NHN statistics. They can be managed as fixed strings.

4

Target Settings

Configure the cohort to be the webhook send target.

If receiveMailAddr is empty, the NHN API may return an error.

We recommend filtering in the webhook campaign target conditions so that only users with an email property are included.

5

Send Settings

Once you save the campaign settings, you can see the following summary information.

Now configure the desired send conditions.

For example, methods such as Schedule-based and Event-based.

You can also check information about the estimated send target on the send settings screen.

Configure the send type and customer fatigue management, then click Start to activate the campaign.

6

Complete

The email webhook campaign activation is complete.

Track the campaign performance on the statistics screen.