Tool
support_survey_create
Open a new survey.
Open a new survey. It starts as a draft — editable and not yet answerable — whatever questions travel with it. There is no way to create one already published: publishing runs the structure validator, and a create that skipped it would be a second way in
Behavior
- HTTP
POST /support/surveys
Arguments
Name | Type | Required | Description |
|---|---|---|---|
name | string | • | What this survey is called. It becomes the title of an escalated feedback thread |
questions | array | — | The initial question set. Omit it to open an empty draft and fill it in later |
Response
Field | Type | Always | Description |
|---|---|---|---|
id | string | • | Survey id |
name | string | • | What this survey is called |
status | string | • | draft: editable, not answerable. published: answerable, frozen. archived: terminal, neither editable nor answerable, and there is no way back |
createdAt | string | • | ISO-8601 creation timestamp |
questions | array | • | The ordered question set, exactly as stored |
updatedAt | string | • | ISO-8601 last-modification timestamp |
questionIds | array | • | The same questions as a flat list of ids, in the order they are asked |
questionCount | integer | • | How many questions this survey asks — the same field support/survey.published carries, so a workflow built from the trigger and one built from a get-step bind one shape |
Try it
Open a new survey.