[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-chats\u002Fservice\u002Fflow-form":3,"docs-tabs-chats\u002Fservice\u002Fflow-form":6},{"content":4,"lastmod":5},"## Flow form\n\n`GET \u002Fv1\u002Fchats\u002F:dialogId\u002Fflow-form`\n\nData for the form that creates a task flow from a collab: the ID of the collab's workgroup. The flow is not created — the user fills in the form in Bitrix24.\n\nWorks for collabs only.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|----------|\n| `dialogId` (path) | string | yes | Dialog ID of the collab: `chat123` — the `dialogId` field of a [collab list](\u002Fdocs\u002Fchats\u002Fdiscovery\u002Frecent-collabs) row |\n\nThe operation accepts no query parameters: any query parameter is rejected with `400 INVALID_PARAMS`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat42\u002Fflow-form\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat42\u002Fflow-form\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\"\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat42\u002Fflow-form', {\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { data } = await res.json()\nconsole.log('Collab group:', data.groupId)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat42\u002Fflow-form', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { data } = await res.json()\nconsole.log('Collab group:', data.groupId)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data.groupId` | number | ID of the collab's workgroup — the flow will be created in it |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": { \"groupId\": 57 }\n}\n```\n\n## Error response example\n\n422 — the chat is not a collab:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"BITRIX_ERROR\",\n    \"message\": \"Chat type is not supported\",\n    \"b24Code\": \"CHAT_TYPE_NOT_SUPPORTED\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_PARAMS` | A query parameter was passed — the operation accepts none |\n| 401 | `TOKEN_MISSING` | The API key has no Bitrix24 tokens configured |\n| 403 | `SCOPE_DENIED` | The API key does not have the `im` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is read-only: the call may make the key owner a chat member |\n| 404 | `ENTITY_NOT_FOUND` | Bitrix24 returned \"not found\". The Bitrix24 code is in `error.b24Code` |\n| 422 | `BITRIX_ERROR` | Bitrix24 returned an error. The Bitrix24 code is in `error.b24Code`. `CHAT_TYPE_NOT_SUPPORTED` — the chat is not a collab |\n| 502 | `ME_ALIAS_RESOLUTION_FAILED` | Failed to resolve the current user for `me` |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned a server error |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [Task form](\u002Fdocs\u002Fchats\u002Fservice\u002Ftask-form)\n- [Service methods](\u002Fdocs\u002Fchats\u002Fservice)\n","2026-10-07",{},1794739551834]