Actions168
- Bot Actions
- Call & Meeting Actions
- Channel Actions
- Add Bot to Channel
- Add Channel Members
- Approve Channel
- Archive Channel
- Change Channel Member Role
- Change Channel Permission
- Create Channel
- Delete Channel
- Get Channel
- Get Channel Members
- Join Channel
- Leave Channel
- List Channels
- Reject Channel
- Remove Bot From Channel
- Remove Channel Members
- Remove Single Channel Member
- Unarchive Channel
- Update Channel
- Chat Actions
- Cliq Database Actions
- Custom Domain Actions
- Custom Email Actions
- Department Actions
- Designation Actions
- Event Actions
- File Actions
- Maintenance (Bulk Export) Actions
- Message Actions
- Message Component Builder Actions
- OAuth Helper Actions
- Reaction Actions
- Reminder Actions
- Remote Work Actions
- Role Actions
- Team Actions
- Thread Actions
- User Actions
- User Field Actions
- User Status Actions
- Widget Map Ticker Actions
Message Component Builder → Build Buttons
AI-generatedSummary
Build one or more reusable Zoho Cliq button objects in JSON format without sending a message. Use structured fields or provide raw JSON for each button's configuration, including action type and action data, and optionally include a 'buttons' wrapper array in the output for advanced JSON message construction.
Inputs
- Buttons (required) — Define multiple button objects either using detailed fields (label, action type, etc.) or raw JSON. Each button can be enabled or disabled, include optional confirmation dialogs, and specify action details such as URL, function names, or system API calls.
- Include Buttons Wrapper in Output — Optionally wrap the resulting buttons array inside a 'buttons' property, suitable for use in advanced JSON editors for message posting.
Output shape
a single JSON object per input item containing two output properties: 'buttonsJsonPretty' (a formatted array of button objects without wrapping) and 'buttonsPayload' (the same array optionally wrapped in a 'buttons' property if chosen).
If 'Include Buttons Wrapper in Output' is enabled, the output includes a 'buttons' wrapper property for raw JSON editor use downstream. This operation does not send any message; it only prepares button configuration data to be reused elsewhere in message components or payload assembly.
Examples
Example 1: Creating two buttons with structured properties
Define each button with label, action type (e.g., 'open.url'), and relevant action data like URLs. Configure optional confirmation dialogs or icons as needed. The output JSON can then be referenced in later message composing nodes.