PachcaInstall

Summary

Updates a Pachca bot’s settings by bot ID, including webhook and token configurations. The operation requires the bot ID and the outgoing webhook URL, and supports numerous optional fields to configure the bot's behavior, permissions, subscriptions, and metadata. These optional fields include roles allowed to edit, verification keys, commands and subscribed events, event history and self-message toggles, bot name, nickname, token scopes (excluding reserved and user-role-only scopes), incoming webhook template and engine, trigger condition, single chat restriction, OAuth client settings, bot catalog promo information, unfurl domains, and who can add the bot to chats. The outgoing webhook URL parameter is required and corresponds to the bot's webhook URL settings. The request sends an update (PUT) to the specified bot with these parameters.

Inputs

• ID (required) — Bot ID to update.
• Webhook URL (required) — URL for the bot’s outgoing webhook.
• Additional Fields — Optional settings to update the bot, including: roles allowed to edit the bot settings (an empty list means only the creator can edit); verification key for incoming webhook verification; bot commands (trigger words) that must collectively be at most 255 characters when joined by commas; subscribed events; toggles for event history saving, ignoring the bot’s own messages, and link preview enabling; incoming webhook kind/source (Gitlab, Grafana, Simple/custom); single chat restriction flag; bot name and nickname (nickname must end with _bot); OAuth client authorization settings; bot's catalog promo information; token scopes (permissions), excluding reserved (bot, all) and user-only scopes; incoming webhook template and template engine (Liquid or Mustache); outgoing webhook URL (alias for the required Webhook URL input); trigger condition for the outgoing webhook (all messages, commands, unfurl); domains that the bot unfurls links for; and who can add the bot to chats (anyone except guests, creator only, creator and admins, or creator/admins/members).

Output shape

A single bot record returned by the update request.

The operation sends an update request for the specified bot. The required Webhook URL is sent as the outgoing webhook URL; the optional outgoing URL field in Additional Fields also maps to that setting. Actual response fields depend on the Pachca API response.

Links

• n8n community nodes installation guide