Actions

Type key: actions. Renders the button row at the bottom of a page: the primary button that moves respondents to the next page, or submits the form when the next page is an ending, and an optional Back button. In the editor, see Page navigation.

A structural node: it sits at the page root and cannot be placed in a layout row.

Meta fields

The meta fields of this node type are listed in the request body of Replace the draft document, under pages › nodes, in the actions tab.

Example

A minimal Actions node

{
  "public_id": "nSub",
  "sort_order": 3,
  "type": "actions",
  "meta": {
    "label": "Register"
  }
}

Defaults and rules

• Every intro and normal page holds exactly one page-level actions node, always last. A page you send without one gets a default from the server: Start on the intro, Submit on the last question page, and Next elsewhere. An actions node sent elsewhere on the page moves to the end, and a hidden one is shown. Endings never hold one.
• A default the server adds receives a new public ID, and a later write that omits the page’s actions node keeps that ID.
• The defaults are label: "Submit", back_button_label: "Back", and is_page_actions_override: false, which means the Back button, the button arrows, and the alignment follow the theme.
• show_back_button, show_button_arrows, and action_button_alignment apply only when is_page_actions_override is true. Sending any of them without is_page_actions_override turns the override on; with the override false, the server drops them.
• The Back button appears only once respondents have moved past the first page, whatever the settings say.
• Both labels are plain text of up to 100 characters and support answer piping.
• Keep is_hidden at false: a hidden Actions node is stripped at publish, and the page loses its button.