Connect Naver Works

When you connect Naver Works, the AI will read and organize your mail, calendar, drive, board, and tasks, and—once you approve—can even send emails, create events, post to boards, and create tasks for you. If you add a bot, you can also receive reports and alerts as messages.

The setup has two steps. ① An admin creates a company app and connects it to the workspace, then ② each member clicks “Connect my account”. The AI only reads the data of the person who clicked the button — it will not open anyone else’s inbox.

Only Naver Works admins can create an app. You must be a super admin, sub-admin, or an admin with Developers permission. If you’re not an admin, copy the text in the connect window under “Copy request text to send to admin” and share this guide with them.

Step 1. Create an app (admin)

Go to Naver Works Developer Console (dev.worksmobile.com), log in with a Naver Works admin account, and add a new app under API 2.0.
In Redirect URL, paste the exact URL shown in Neuro’s connect window (use the “Copy Redirect URL” button). If even one character is different, member login will fail.
In OAuth Scopes, add and save the following: openid, email, profile, mail, calendar, file.read, board, task, bot.message, bot.read. If you won’t use a bot, you can omit bot.message and bot.read.
Copy the Client ID and Client Secret from the app details.

Step 2. Connect in Neuro (admin)

In your Neuro workspace, open Data sources → Naver Works.
Enter the Client ID and Client Secret and click Connect. If you also want to use the bot, first complete “Optional: Bot” below, then fill in the “Send messages via bot” field.

Reconnecting will overwrite the previous setup. Each workspace can have only one Naver Works connection. If you switch to a different app, members who were connected via the old app must reconnect with “Connect my account”.

Step 3. Connect my account (each member)

In the Data sources screen, find Naver Works and click Connect my Naver Works account.
In the pop-up window, log in to Naver Works and approve the permissions—that’s it. If you see a row saying ‘My account: email’, the connection is live.

Your login stays active for about 90 days. If you haven’t used it for a while, or an admin changes your permissions, you’ll see ‘Reconnect’.

Try asking the AI like this:

“Summarize the emails I got yesterday from our ad agency.”
“Organize my schedule for this week and book a campaign review meeting for Thursday at 3 PM.”
“Find the ‘10월 매체 단가’ file in Drive and summarize it.” — For text/CSV files, Neuro can read the contents; for Excel/PDF, it can only read the file name and basic info.
“Show me the latest 3 posts on the notices board.” / “Post this month’s performance summary to the marketing board.”
“Tell me which of my tasks are past due, and add ‘review reports’ as a new task.”

When sending email, creating calendar events, posting to boards, or creating tasks, Neuro will always show a confirmation card before it runs anything. Nothing is executed until you approve it.

Optional: Send messages via bot

In the Step 1 app screen, issue a Service Account and download the Private Key file. Each app can only have one, and when it’s issued, admins get a notification.
In the Naver Works Developer Console under the Bot menu, register a bot. If you also want to send to message rooms, turn on Allow participation in 1:N message rooms. After saving, copy the Bot ID that appears.
In the admin panel, add the bot to your company domain. Until it’s added, the bot status stays ‘Preparing’ and it can’t send messages.
In Neuro’s connect window, open Send messages via bot (optional), then enter the Service Account, Private Key (upload key file), and Bot ID to connect. Neuro only saves after actually receiving a token and successfully looking up the bot.

You can set recipients by member email or message-room channel ID. For message rooms, invite the bot first, then copy the ‘Channel ID’ from the room menu and share it with Neuro (the bot can’t find rooms by name).

Treat your Private Key like a password. Don’t paste it into chat or email—share it as a file and keep it secure. If you reissue a key, the old one is immediately invalidated.

Permissions and data handling

When a member logs in, Neuro only acts with that person’s own permissions. Drive is read-only (file.read), while Mail/Calendar/Boards/Tasks allow reading plus write actions that always require approval.
Because a bot token has admin-level privileges, when Neuro receives a token it Only bot.message and bot.read are requested. Even if the app has other permissions enabled, the bot will not read mail or calendar data.
Client Secret, Private Key, and member login tokens are encrypted at rest and never shown again in the UI.
Content from emails or posts that the AI reads is stored in that AI conversation history like any other channel data. If you delete the conversation, any sensitive emails referenced there are removed with it.
For detailed data collection items and retention periods, please see our Privacy Policy.

Disconnect

Member — When you click “Disconnect” on the Data sources row, your login token is revoked and deleted from Naver Works.
Admin — When you disconnect Naver Works, all members’ login tokens are revoked and stored keys are deleted. The app and bot belong to your company, so Neuro does not delete them — if you’re no longer using them, remove them in the Naver Works Developer Console.

Troubleshooting

You see an error in the “Connect my account” window

Check whether the app’s Redirect URL exactly matches the URL of this connection window, and that all of the scopes above are added under OAuth Scopes. After you add scopes, members must reconnect for the changes to take effect.

AI keeps telling me to “connect my account”

The person in that conversation either hasn’t connected “My account” or the connection has expired. Go to the Data sources page to connect or reconnect.

It says bot authentication failed

Check that the Client ID, Secret, Service Account, and Private Key all come from the same app and that bot.message and bot.read are included in the scopes.

Bot messages are failing to send

Check that the bot is added to your domain in the admin console, that the recipient is a member of the same company, and, for chat rooms, that the bot has been invited to that room.

If you have any issues while connecting or using the integration, contact pango_plat@pango-gy.com. We’ll respond within 1–2 business days.