400 error in Webflow Create Live Item via Make HTTP

[Reely]

Thank you for your help, we are building a reel video script generation application called Reely with Make (formerly Integromat) + Webflow.

Currently, we are trying to publish a new Live item immediately with the following configuration, but every time we try to do so, we get “400 Bad Request (ValidationError: Invalid request body)” and the submission fails.

Scenario Configuration

Webhook (Custom webhook)

JSON Parse

OpenAI (ChatGPT module)

HTTP module (Webflow API)

HTTP module configuration

Method: POST

URL: https://api.webflow.com/v2/sites/[site ID]/collections/[collection ID]/items/live

Headers: Content-Type: application/json + authentication Headers

Body type: Raw (JSON)

Request content:

{

“fields”: {

“name”: “ReelScript_” + formatDate(now; “yyyyMMdd_HHmmss”) + “_” + randomText(4),

“slug”: " reelscript-" + formatDate(now; “yyyyMMdd_HHmmss”),

“script-content”: 6.Choices[:Message.Content],

“user”: 1.field,

“date”: now,

“script- plain-text”: 6.Choices[:Message.Content]

}

}

---

お世話になります。Make（旧Integromat）＋WebflowでReelyというリール動画台本生成アプリを構築中です。

現状、以下の構成で新規Liveアイテムを即時公開しようと試みていますが、毎回「400 Bad Request（ValidationError: Invalid request body）」が発生し、送信に失敗しています。

---

シナリオ構成

1. Webhook（Custom webhook）
2. JSON Parse
3. OpenAI（ChatGPT モジュール）
4. HTTP モジュール（Webflow API）

---

HTTP モジュール設定

• Method： POST
• URL： https://api.webflow.com/v2/sites/[サイトID]/collections/[コレクションID]/items/live
• Headers： Content-Type: application/json + 認証ヘッダ
• Body type： Raw（JSON）
• Request content：

{
  "fields": {
    "name": "ReelScript_" + formatDate(now; "yyyyMMdd_HHmmss") + "_" + randomText(4),
    "slug": "reelscript-" + formatDate(now; "yyyyMMdd_HHmmss"),
    "script-content": 6.Choices[:Message.Content],
    "user": 1.field,
    "date": now,
    "script-plain-text": 6.Choices[:Message.Content]
  }
}

[samliew]

Welcome to the Make community!

We’d love to help, however, you have not provided sufficient information to demonstrate the problem that would allow us to reproduce the scenario and any issue/s and/or error/s.

To allow others to assist you with your scenario, please provide the following:

1. All Relevant Screenshots

We need to see what you’re working with to give you the best advice. Screenshots are extremely important because Make is a visual editor — a picture provides us with more context.

It would help us identify the issue by having screenshots of:

• the full scenario,
• any error messages,
• individual module fields,
• relevant filter settings (conditions), and
• each module’s output bundles
• any external services (spreadsheet headers, sample data, regex101.com, etc.)

2. Scenario Blueprint

Please export the scenario blueprint. Providing your scenario blueprint file will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return - this would greatly benefit you in implementing our suggestions as you can simply paste module exports back into your scenario editor!

To export your scenario blueprint, click the three dots at the bottom of the editor then choose ‘Export Blueprint’.

3. Module Output Bundles

Please provide the output bundles of each of the relevant modules by running the scenario (you can also get this without re-running your scenario from the History tab).

Click on the white speech bubbles on the top-right of each module and select “Download input/output bundles”.

A. Upload as a Text File

Save each bundle contents in a plain text editor (without formatting) as a bundle.txt file.

You can upload the file here by clicking on this button:

B. Insert as Formatted Code Block

If you are unable to upload files on this forum, alternatively you can paste the formatted bundles.

To provide code/text using Markdown format, you can type a code fence.
Add three backticks ``` in a separate line before and after the content, like this,

```
text goes here
```

Alternatively, you can upload your file and share the public link** —
(this method is only recommended for large files exceeding the forum upload limit)

Providing the input/output bundles will allow others to replicate what is going on in the scenario, especially if there are complex data structures (nested arrays and collections) or if external services are involved, and help you with mapping the raw property names from collections.

Sharing these details will make it easier for others to assist you.

[Reely]

Thank you very much for your kind reply and helpful guidance.

As requested, I have attached the following:

• A screenshot showing the error message from the HTTP module’s output bundle
• The exported scenario Blueprint in JSON format

Below is the full content currently entered in the Request content field that is causing the error:

{
“isArchived”: false,
“isDraft”: false,
“fields”: {
“name”: “ReelScript_{{formatDate(now; "yyyyMMdd_HHmmss")}}_{{randomText(4)}}”,
“slug”: “reelscript-{{formatDate(now; "yyyyMMdd_HHmmss")}}”,
“script-content”: “{{6.Choices[1].Message.Content}}”,
“script-plain-text”: “{{6.Choices[1].Message.Content}}”,
“user”: “testuser”,
“date”: “{{formatDate(now; "yyyy-MM-dd’T’HH:mm:ss.SSS’Z’")}}”
}
}

Integration Webhooks.blueprint.json (53.1 KB)