LINE Notifications

Using the LINE Messaging API, you can send monitor incident notifications to LINE.

1. Prepare a LINE Official Account and Messaging API channel

   Follow the official LINE guide to enable the Messaging API for a LINE Official Account. Manako needs credentials for that Messaging API channel.

2. Issue a Channel Access Token

   Issue a valid Channel Access Token for the Messaging API channel and store it securely. This is the value for Manako’s Channel Access Token field.

3. Obtain the target ID

   Read source.userId, source.groupId, or source.roomId from a Webhook event sent by the user, group, or room. This is the value for Manako’s Target ID field.

4. Confirm the Bot can reach the target

   For a user target, have the user add the LINE Official Account as a friend. For a group or room, add the Bot to that conversation.

Destination	ID Format	How to Obtain
User	U + 32-digit hex	source.userId from a Webhook event
Group	C + 32-digit hex	source.groupId from webhook events
Room	R + 32-digit hex	source.roomId from webhook events

1. In the dashboard, open Settings > Integrations, then select Configure for LINE
2. Enter a recognizable Name
3. Enter the Channel Access Token and Target ID
4. Select Add

After setup, LINE messages will be sent when a monitor detects an incident or recovers.

Normal notifications are LINE Flex Messages with a status-colored header. Only the Test action sends a text message.

Section	Content
Header	🔴 ダウン検知 (⚠️ 警告 for a warning)
Body	Monitor name, monitored URL when available, and ID: {Incident ID}
Footer	Manako

Section	Content
Header	🟢 復旧 (🟢 解決済み for a manual incident)
Body	Monitor name and ID: {Incident ID}
Footer	Manako

• The Target ID is rejected: Manako accepts U, C, or R followed by 32 hexadecimal characters. A display name or LINE ID cannot be used.
• The API fails or the message is not received: Check whether the Token expired or was revoked, whether the user is a friend, and whether the Bot belongs to the target group or room. LINE may return success even when a blocked user does not receive the message.
• A test arrives but normal notifications do not: When a monitor has channel links, only active linked channels are used. If links exist but all are disabled, Manako does not fall back to team-wide channels.
• Notifications stop during rapid state changes: After more than three state changes for the same monitor within 10 minutes, the flap guard suppresses subsequent notifications.
• Notifications appear duplicated: A sent record for the same incident, channel, and event type skips retries. Creation and recovery are separate events, while failed or pending sends are retried.

Test sends an actual LINE text message and has a 60-second cooldown after success. A failure on one channel does not stop delivery to other channels.

The flap guard and incident-level sent check apply to incident notifications. Maintenance notifications bypass both controls and go to active, verified team channels.