update_support_settings
Change a project's support inbox settings. Anything omitted keeps its stored value.
Switch member support on or off, choose where new threads are relayed, set the name members see on replies, set or clear the automatic acknowledgement, and toggle email notifications. Partial by design: only the settings present in the call change, and the rest is assembled from the stored row before the write.
Emits support.settings.updated with the settings as they now stand and what changed — and only when something did. Idempotent: sending the stored values again writes nothing and emits nothing.
Turning support off
With enabled: false, member messages stop reaching the inbox and go back to
the bot's "I can't understand" fallback. Existing threads are kept, nothing is
deleted, and switching it back on resumes intake — but messages sent in
between are not recovered.
relay_mode accepts owner_dm, forum_group and none. forum_group
starts relaying once the creator has added the project bot to a group with
Topics enabled as an administrator; the bot links the group itself and
confirms by DM, so switching the mode alone does not connect anything.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it. Sending the same arguments twice changes nothing the second time. It reaches beyond Subscriby: a connector, a provider or a member.
Arguments
project_id*stringUUID of the project whose support settings to change.
enabledbooleanoptionalWhether members can open support threads with the bot.
relay_modestringoptionalWhere new threads go besides the dashboard inbox: "owner_dm" forwards them to the creator on their connector, "forum_group" opens each thread as a topic in the group the project bot administers, "none" keeps them in the inbox only.
agent_namestringoptionalThe name members see on replies, up to 60 characters. Pass null to use the project name.
auto_replystringoptionalThe message sent automatically when a member opens a thread, up to 1000 characters. Pass null for none.
notify_emailbooleanoptionalWhether the creator is emailed about new threads.
What it returns
{ "data": { "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "enabled": true, "relay_mode": "owner_dm", "agent_name": "Team Subscriby", "auto_reply": "Thanks, we will reply within a day.", "notify_email": true, "updated_at": "2026-09-06T10:05:00+00:00" }}The same row get_support_settings returns, after the change. agent_name and auto_reply come back trimmed; a blank string is stored as null, the same as passing null.
How it fails
VALIDATION_FAILEDrelay_mode is anything but owner_dm or none, agent_name longer than 60 characters, auto_reply longer than 1000, or enabled / notify_email not a boolean. The envelope names the offending field. Also returned when the token's owner is on the project's team but their role may not update the project.
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_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks project:update.
How is this guide?
Last updated on