get_support_settings

Read a project's support inbox settings — enabled, relay mode, agent name, auto-reply and email notifications.

Purpose

Read how a project's member support is configured: whether members can open threads at all, where new threads are relayed besides the dashboard inbox, the name members see on replies, the acknowledgement sent when a thread opens, and whether the creator is emailed about new threads.

The settings are columns on the project, so reading them takes only the project view ability — no support ability is needed to see how support is set up.

The connector relay chat id is never part of the row. It is an identifier the bot handshake writes when the creator links their account, not a setting a client should read or set.

Required ability

project:view

Input schema

{
  "type": "object",
  "required": ["project_id"],
  "properties": {
    "project_id": {
      "type": "string",
      "description": "UUID of the project whose support settings to read."
    }
  }
}

Output shape

{
  "data": {
    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
    "enabled": true,
    "relay_mode": "owner_dm",
    "agent_name": "Team Subscriby",
    "auto_reply": "Thanks — we usually reply within a few hours.",
    "notify_email": false,
    "updated_at": "2026-08-11T15:40:19+00:00"
  }
}

relay_mode is owner_dm (each new thread is forwarded to the creator on their connector) or none (dashboard inbox only). agent_name: null means replies carry the project name; auto_reply: null means no acknowledgement is sent. updated_at is the project's timestamp — it moves whenever anything on the project changes, not only these settings.

Example prompts

"Is member support switched on for project 7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13?"

"What auto-reply do members get when they message the Research Premium bot?"

"Am I getting Telegram DMs or emails for new support threads on this project?"

Failure modes

  • RESOURCE_NOT_FOUNDproject_id names a project the token cannot see: unknown, another team's, or outside the token's scope:project: allow-list.
  • AUTHENTICATION_REQUIRED — no authenticated user on the request.
  • TOKEN_MISSING_ABILITY — token lacks project:view.

How is this guide?

On this page

Subscriby is a product designed by you — for you.

No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request