Skip to content
MarcommAI

Connect NAVER WORKS to Marcomm

Get instant alerts, approval requests and the digest from a NAVER WORKS bot, in a 1:1 chat or in a chat room.

  1. 1
    In the NAVER WORKS Developer Console, open API → ClientApp and add an app with the bot and user.read scopes.
  2. 2
    Copy the Client ID and Client Secret. Under Service Account, issue an account, then select Issue / Reissue next to Private Key and download the .key file.
  3. 3
    Open Bot, register a bot for the app and note its Bot ID, a number. Make the bot available to the people who should receive messages.
  4. 4
    In the NAVER WORKS Admin console, add the bot you registered so that members can use it. A bot registered only in the Developer Console is not available to members.
    NAVER WORKS page in Marcomm with the bot, recipient and credential fields
    Settings → Integrations → NAVER WORKS.
  5. 5
    In Marcomm, go to Settings → Integrations → NAVER WORKS, enter a name, the Bot ID and the recipient, then the Client ID, Client Secret, service account and the contents of the .key file, and select Add. The recipient is a member ID (id@company) for a 1:1 chat, or the channel ID of a chat room the bot has joined.
  6. 6
    Select Send a test message. It arrives from the bot in that chat.
  7. 7
    To receive in a 1:1 chat and in a room, add each as its own destination with the same credentials.

The member ID is the one shown in the NAVER WORKS admin console (id@company), not the sign-in email.

LINE WORKS and NAVER WORKS run on the same service behind the scenes, so a workspace can connect only one of them. Connect the one your company uses.

Marcomm stores the Client Secret and the private key encrypted and never shows them again. They are deleted when you remove the destination or delete the workspace.

NAVER WORKS receives only what a message shows, such as an article headline, a press release title or the details of an approval request. Approval requests link back to Marcomm, where the decision is made.

The bot connected to the workspace also sends a direct message to each recipient's Marcomm sign-in email. Marcomm finds your account by the Marcomm sign-in email. If that does not match a NAVER WORKS ID, it also tries the personal email on your NAVER WORKS profile (needs the user.read scope). If no account is found, no direct message is sent and the chat you set as the destination still receives the notification. Each person turns on the Messenger column in the table under Account → Notifications. On this integration's page in Marcomm, the Direct messages section shows your sign-in email so you can compare it.

To add your workspace schedule to your NAVER WORKS calendar, turn on the WORKS calendar switch under Account → Notifications. Scheduled press releases, blog posts and press events then appear in your default NAVER WORKS calendar within seconds of saving. The app also needs the calendar and user.read scopes in the Developer Console. Marcomm does not delete events when a schedule is removed.

FAQs

Marcomm sends instant alerts, approval requests, approval results and digests to the NAVER WORKS conversation you connect. The workspace bot can also send one-to-one messages, and for those your Marcomm sign-in email has to match your NAVER WORKS account email. Approving and rejecting happen on the Marcomm screen that the link in the message opens.

Yes. Add one destination with a member ID for the 1:1 chat and another with the channel ID for the room.

In the NAVER WORKS admin console, in the member's details. It looks like id@company and is not the sign-in email.

Yes. When this bot is connected to the workspace, people who turn on the Messenger column in the table under Account → Notifications receive a direct message at their Marcomm sign-in email. The Marcomm sign-in email and the NAVER WORKS account email must be identical. The app needs the user.read scope.

Integrations