`POST /v1/notes_destinations`

Sets where a voice channel’s notes go, the same as adding a destination under Notes destinations in the dashboard. Use it when you make channels per client or team, so the new voice channel’s notes go to the right place from its first meeting. Each voice channel has one destination: sending another for the same voice channel replaces it.

Request

POST /v1/notes_destinations
Authorization: Bearer <token>
Content-Type: application/json

Body field	Required	Description
`voice_channel_id`	Yes	The voice or stage channel whose meetings this is for.
`channel_id`	Yes	Where the notes go. A text channel or forum gets a new thread or post for each meeting. A post or thread in one, like a client’s Huddle Notes post, gets every meeting added to it.

Send ids as strings: they’re too long for some tools to keep exact as numbers. To copy one, turn on Developer Mode in Discord (Settings → Advanced), then right-click the channel or post.

Example

POST /v1/notes_destinations
Authorization: Bearer <token>
Content-Type: application/json
 
{
  "voice_channel_id": "1562925672127668374",
  "channel_id": "1563282722724646982"
}

Successful response

Status: 201 Created for a new destination, 200 OK when it replaced one. Content-Type: application/json

{
  "notes_destination": {
    "voice_channel_id": "1562925672127668374",
    "channel_id": "1563282722724646982"
  }
}

Errors

Status: 422 Unprocessable Content when DiscMeet can’t use a channel. message says which one and why:

{
  "error": "invalid_channel",
  "message": "channel_id: that's a private thread, so people outside it couldn't see the notes. Use a public post or thread."
}

Cause	Fix
The channel isn’t in this server, or DiscMeet can’t see it	Check the id, and that DiscMeet’s role can view the channel.
`voice_channel_id` isn’t a voice or stage channel	Use the voice channel’s id.
`channel_id` is a private thread	Use a public post or thread.
`channel_id` is another kind of channel	Use a text channel, a forum, or a post or thread in one.

Status: 400 Bad Request when a field is missing.

From Zapier/n8n

Add a POST step after the step that creates the channels: Webhooks by Zapier → POST in Zapier, an HTTP Request node with method POST in n8n.

URL: https://api.discmeet.com/v1/notes_destinations
Payload type (n8n: Body Content Type): json
Data: voice_channel_id and channel_id, from the step that created them
Headers: Authorization set to Bearer <token>

GET /v1/notes_destinations: list the server’s destinations.
DELETE /v1/notes_destinations/:voice_channel_id: remove one.
Notes destinations: the dashboard setting, and how posting into one post works.

POST /v1/notes_destinations