Buttons
Some tasks come up again and again: filing a bug with the same properties, adding a meeting agenda in the same format, or moving a task along and telling someone about it. A button bundles that sequence into a single click, so it happens the same way every time and nobody has to remember the steps.
A button is a block you place on a page. Every button follows the same shape: when it's clicked, do a list of actions.
Create a Button
- Type
/buttonon any page and select Button from the block menu - Give it a name — the default is
New button, and you can pick an icon alongside it - Under Do, click Add action and choose what it should do
- Add further actions if the task takes more than one step
- Click Done
The name is what people see, so write it as an instruction — File a bug, Approve request, Start weekly review — rather than a label like Button 1.
The When condition is fixed at Button is clicked — a button always runs in response to someone clicking it.
Actions
An action is a single step the button performs. A button can chain several, and they run top to bottom in the order you list them.
| Action | What it does |
|---|---|
| Insert blocks | Adds content to the page — text, lists, headings, or any other block |
| Show confirmation | Asks the person to confirm before the remaining actions run |
| Open page or URL | Opens a Closot page |
| Add page to… | Creates a new item in a database you choose |
| Edit pages in… | Updates existing items in a database and the values of their properties |
| Send notification | Notifies people in your workspace |
Ordering Actions
Order matters. A button that files a bug might add a page to the Bugs database, then send a notification to the on-call engineer.
Put Show confirmation first when the button does something people would rather not trigger by accident — creating records in bulk, or notifying a large group. Everything after it only runs once the person confirms.
Edit or Remove a Button
Every button has a gear icon beside it. Click it to reopen the configuration panel and change the name, icon, or actions.
To delete a button, select the block and press Backspace, or use the ⋮⋮ handle and choose Delete. See Keyboard Shortcuts.
Permissions
Creating, editing, and clicking a button all follow the permissions on the page it sits on — you need edit access. Someone with view or comment access can see a button but not run it.
When a button writes to a different database from the page it's on, the person clicking needs access to that database too, or the action can't complete. See Sharing & Permissions.
Examples
File a bug. Adds an item to the Bugs database with Status set to Not started, then notifies the on-call engineer.
Start a meeting note. Inserts a heading, an attendees line, and an empty action-items list on the page.
Close out a sprint. Shows a confirmation, then edits the remaining items in the sprint database to move them to the backlog.
Open the team hub. Jumps straight to the page everyone needs during an incident, so nobody has to search for it.