Workspace tools
Area roles and how an agent hears about its tasks.
set_area_membership
Set area membership. Changes data.
Use this when an owner or an area's admin asks to add someone to an area, make them its admin or a member, or take them out of it. In each area a person is admin or member: members see the area's tasks, projects and knowledge and manage what they created or are assigned; admins run the area (every task in it, who belongs, approving its knowledge). A person or agent can be in several areas; agents are always members. Only owners and the area's admins can do this; agents never can.
| Parameter | Type | Required | Description |
|---|---|---|---|
area | string | yes | Area name or id, from get_workspace (General is the area everyone is in). |
member | string | yes | Who: an email, an agent @handle, a full name, a first name, or "me". If several people match, Gorila returns the candidates instead of guessing. |
action | "add" | "remove" | yes | add: put them in the area (or change their role there) · remove: take them out. |
role | "admin" | "member" | no | With add: admin or member. Omit to add as a member, or keep the role they already have. |
set_my_webhook
Set my webhook. Changes data.
Use this when you are an AI agent with a webhook Gorila can call (a public https URL that wakes you), right after you connect or when that URL or its key changes, or to remove it. Gorila then POSTs the ids of your changed tasks to it when someone assigns, edits, comments on or moves one; keep your scheduled check as a safety net. Only for agents, and only your own webhook; people set agents' webhooks in Settings → Members → Agents, where they can also pause yours.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | "set" | "remove" | no | set: create or change your webhook · remove: stop Gorila calling you. |
url | string | no | With set: your webhook's public https URL. |
format | "standard" | "bearer_json" | "openclaw" | "claude_code_routine" | no | With set: how Gorila calls you. standard: JSON signed with Standard Webhooks headers (Hermes, Svix) · bearer_json: the same JSON with an Authorization bearer (n8n, Cursor, most webhook triggers) · openclaw: OpenClaw Gateway POST /hooks/agent · claude_code_routine: a Claude Code routine's /fire URL. |
key | string | no | With set: the signing secret (standard) or bearer token (the others). Required the first time; omit to keep the stored one. Stored encrypted, never shown again. |
test | boolean | no | With set: send a test delivery now and report whether it arrived. |
set_my_wake
Set my work shift. Changes data.
Use this when the user answers an offer to let their AI work between sessions, asks for it ("let my AI work for me", "adelántame las tareas"), or changes what their scheduled run may do. answer: yes returns the steps and the prompt to create a daily scheduled run in their own client; configured once it exists; not_now, never or unavailable otherwise. A run prepares and never sends. Only for people, about themselves.
| Parameter | Type | Required | Description |
|---|---|---|---|
answer | "yes" | "configured" | "not_now" | "never" | "unavailable" | no | yes: they want it, get the steps · configured: the scheduled run exists · not_now · never: don't offer it again · unavailable: this client can't schedule. Omit to only change shift_scope or max_tasks. |
client | "claude_code" | "claude_ai" | "chatgpt" | "codex" | "cursor" | "agent" | no | The AI client the user is in. Omit to let Gorila detect it. |
shift_scope | "check" | "marked" | "all" | no | What the run may do on its own, the user's choice: check: only close what it can prove and unblock what waits · marked: also prepare the tasks I mark · all: also prepare any of my to-do tasks with a done check (the default). |
max_tasks | integer | no | How many tasks a run should move. Default 3. It is offered up to three times as many and goes on to the next when it cannot move one. |
moment | "waiting" | "due_date" | "stale" | "assigned" | "prepare" | "onboarding" | "floor" | no | Only from the onboarding's wake step: onboarding. |
set_my_block
Keep Gorila always on. Changes data.
Use this when a Gorila reply says this AI client is missing its always-on block, or the user asks to make Gorila work in every chat ("always use Gorila", "úsalo siempre"). Without result it returns the instruction block for this client and where it goes. With result it records what happened: saved (you saved it after their yes), handed (you gave it to the user to paste, without waiting), pasted (they confirmed it), already (it was there) or declined. Only for people, about themselves.
| Parameter | Type | Required | Description |
|---|---|---|---|
result | "saved" | "pasted" | "already" | "declined" | "handed" | no | What happened with the block. Omit to get the block and where it goes. |
client | "claude_code" | "claude_ai" | "chatgpt" | "codex" | "cursor" | "agent" | no | The AI client the user is in. Omit to let Gorila detect it. |
set_my_profile
Set my profile. Changes data.
Use this when the user says what they handle or that their role changed ("I also run support now", "ahora llevo las campañas"), when a Gorila reply says their profile is missing, or to describe what an AI agent handles. The profile is a title, what they handle, concretely (what they own by name, which tasks and approvals go to them), and that in one line; the whole team sees it, and everyone's AI reads it in get_workspace to decide who gets a task. Without fields it returns the current profile and how to draft one. Show the user the text before saving it. A person's profile is only set by that person; an agent's, by itself, an owner or an admin of its areas.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | no | Job title, as they would say it: "Head of sales". Empty clears it. |
responsibilities | string | no | What they handle, concretely, in 2–4 sentences in their own language, so another person's AI can tell whether a given task is theirs: (1) the things they own, by name (products, channels, customers, tools, documents, processes); (2) the kinds of tasks that should go to them; (3) the decisions or approvals that need them, with any threshold ("any discount above 10%"); (4) when it avoids a wrong assignment, what is not theirs and who has it. Never a bare department ("marketing", "the web"). Replaces the current text, so include what still applies. |
summary | string | no | The same in ONE line of at most 140 characters, for the list Gorila shows every teammate's AI when a task is created: the things they own, by name, as a list and not a sentence ("Web: pricing page, plan pages, landings, checkout promo codes (Webflow)"). Keep the names; leave out what is not theirs. Required whenever responsibilities is given. |
agent | string | no | The @handle or name of an AI agent to describe instead of the user. Only owners and the admins of the agent's areas. |