Custom channels

An organization admin connects the channel in the Pager dashboard.

1. 1

   Open Settings → Channels and click Підключити власний канал (Connect your own channel).

2. 2

   Enter a channel name — managers see it in the inbox — and a URL for sending messages: your server's address where Pager will send managers' replies.

3. 3

   Once connected, the channel card shows an API Key like chan_sk_live_… — that's the channel key. Add it to your server's settings.

Both directions are signed with the channel key in the x-channel-key header.

• Your server → Pager. Send the key in x-channel-key with every webhook request. Pager uses it to identify the channel and organization.
• Pager → your server. Pager sends the same key in x-channel-key. Compare it with yours and reject requests with any other key — otherwise anyone who knows your URL could message your clients as a manager.

Successful processing always returns 200 with ok: true. The action field says what was done:

Errors come with an error field:

{
  "error": "Invalid payload",
  "details": {
    "formErrors": [],
    "fieldErrors": {
      "client": [
        "Invalid input: expected string, received undefined"
      ]
    }
  }
}

Respond with a 2xx as soon as you've accepted the message, and return the message's ID on your platform as JSON.

{
  "externalMessageId": "msg_90415"
}

• Pager stores externalMessageId (or externalId) as the message's ID. Without it you won't be able to edit or delete this message later.
• The message counts towards your organization's message allowance only if you responded with a 2xx and returned externalMessageId.
• The manager only sees the message as sent after your response, so respond quickly and do any heavy processing afterwards.

Delivery and retries

• If your server responds with a non-2xx or doesn't respond at all, Pager retries twice more — after 0.2 and 0.6 seconds.
• If all three attempts fail, the message is saved in Pager marked as undelivered, and the manager sees that. Pager doesn't resend it automatically later.

A minimal handler: verifies the key, drops repeats, passes the message to your platform and returns its ID.

import express from "express"

const app = express()
app.use(express.json())

// pagerMessageId -> externalMessageId. In production, use a database or Redis
const processed = new Map()

app.post("/pager/outbound", async (req, res) => {
  // 1. The request really comes from Pager
  if (req.get("x-channel-key") !== process.env.PAGER_CHANNEL_KEY) {
    return res.status(401).end()
  }

  const { client, message } = req.body

  // 2. A repeat of an already processed message
  if (processed.has(message.pagerMessageId)) {
    return res.json({ externalMessageId: processed.get(message.pagerMessageId) })
  }

  // 3. Send to the client on your platform
  const sent = await platform.sendMessage({
    to: client.externalId,
    text: message.text,
    attachments: message.attachments,
  })

  processed.set(message.pagerMessageId, sent.id)
  res.json({ externalMessageId: sent.id })
})

Attachments are an array of { type, payload: { url } } objects — the same in inbound events and in requests from Pager.

[
  {
    "type": "image",
    "payload": {
      "url": "https://cdn.example.com/uploads/photo.jpg"
    }
  },
  {
    "type": "document",
    "payload": {
      "url": "https://cdn.example.com/uploads/invoice.pdf"
    }
  }
]

• Pager stores the link, not a copy of the file, so it must stay available for as long as managers need the conversation history.
• Links to localhost and internal networks (127.*, 10.*, 192.168.*) are silently dropped; the rest of the message is saved.
• Up to 20 attachments per message.
• In requests from Pager, links are temporary and expire after 24 hours — download files right away.