Velaxe
Channels — Team & Project Messaging with Threads, Files, and Guardrails | Velaxe

Channels

Build a channel bot using Webhooks & the Messages API

Subscribe to events, verify signatures, and post threaded replies programmatically.

22 min Intermediate Developers, Partner Engineers Updated Aug 2, 2025

Overview

Subscribe to events, verify signatures, and post threaded replies programmatically.

Prerequisites

None.

Permissions required

API.tokens:create Channels.read Channels.write

Downloads & Templates

Steps (3)

Estimated: 22 min
  1. 1

    Create an API token & webhook

    Developer 6 min Back to top

    **Admin → API**: create a token with Channels scopes. Register webhook for `channel.message.created`.

    Tips

    Validation

    • Test delivery arrives at your endpoint with a valid signature.

    Success criteria

  2. 2

    Verify signatures

    Developer 6 min Back to top

    Verify HMAC using the shared secret and delivery id for idempotency.

    Tips

    Validation

    Success criteria

  3. 3

    Post a reply via API

    Developer 10 min Back to top

    Call **POST /messages/{id}/reply** to respond in a thread with a formatted block.

    Tips

    Validation

    Success criteria

    • Bot replies in under a second; logs show 2xx responses only.

About this guide

Channels keeps work visible and searchable. Use public or private rooms, keep side conversations contained in threads, and attach files through File-Vault with previews and expiring links. Pin a living Canvas to each channel for runbooks or briefs.

With one click, convert an important thread into an Agent Desk ticket, route tasks into ActionDesk, and log every key moment to Chronicle. Moderation, DLP, retention and legal hold are workspace-level guardrails. Optional AI summaries help teams catch up quickly.